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

BW EHS Waste Management and CADRI

The goal of Entries Control Report is to provide a report that facilitates the control of waste generation by period and its posterior management at Paulinia site.

In order to control the generation of each waste by several generating areas of Paulinia and the subsequent steps to final disposition from the supplier, it is necessary to list all Entry Documents created in the period that were not deleted, and them to have the trace of each relevant document created during the process.

Waste Management processes are transversal processes that involves EHS (DG and Product Safety), RtR, PtP and OTC.

There are 2 main transactions in Waste process:

-       Edit Entry Documents - WAE0X – that creates Entry Documents, wastes, stock entries and purchase Orders,  

-       Edit Disposal Documents – WAM0X – that manages the details of waste expedition and posterior disposal

Both types of documents – entry and disposal – have different types of status that are linked to their current process step.

 There is a governmental license –CADRI- that controls the amount of waste that can be  disposed by type of waste and by disposer in a defined period. Also for each waste there are 2 codes that must be informed CETESB and IBAMA CODES.

Also, there are 2 types of classification, one related to waste and its transport, that is the normal DG country classification. And the other is a country Waste Code related to its waste nature.

Summarizing the process at Brazil:

 1-    The generator representative creates an amount of waste in the system. The number of units is exact but the weight is estimated. The waste will be weighed only at the time that it is being issued, therefore the quantity in Kg is estimated until the expedition time.

2-    The Waste Administrator release the Entry Document and define where the waste will be stored, transferring the quantity to the defined warehouse.

3-    Waste Administrator defined the disposer and the transporter and creates the Disposal Document and the purchase request that is based in a preexistent contract. There is an automatic check regarding governmental license- CADRI-  if there is no allowed volume, the process is blocked.

4-     In the purchase request the Waste Adm informs the date expected to issue the waste.  Back office team will create the purchase order. The purchase process is a subcontracting process. Therefore there is a mirror virtual material (ZDIE) linked to each waste material (ZUNB). The waste material appears in the purchase order as a component.  

5-    The logistic team creates the delivery by transaction ME2O, based in the purchase order. After the delivery creation, logistics team creates the shipment order and the expedition programing. If it is the case, all the usual process regarding DG goods expedition is followed.

6-    In right date, the picking is done, the truck is loaded, the waste is weighed, NFe is created and the expedition is done. The waste delivered appears as in the supplier storage control.

7-    NFe copy is sent to Waste Adm that input the data updating the Disposal Document. Also, the right weight value in KG is fixed by MIGO transaction in the stock.

8-    After the effective disposal, the supplier (disposer) sends a destruction certificate and the related invoice to Waste Adm. The weight informed by the supplier can be different of the registered in the expedition.  

9-    The Waste Adm updates data in Disposal document and changes its status. People of invoice centralized reception receives automatically information to perform MIRO and MIGO, and also closes the purchase requisition.

10- The process is finished.       

3.0 Application Feature Overview

Information about the existent Workbooks and the respective BW queries.

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.

Reporting

BW_QRY_MVEHSW01_0001 - EHS Waste Movement (core query)

Filters

Rows

Columns

Navigational Attributes

Lay-Out

BW_QRY_MVEHSW02_0001 - EHS Waste CADRI (core query)

Filters

Rows

Columns

Navigational Attributes

Lay-Out

Data Loading

Info Providers and objects loaded 

Process Chain name: PC_EHS_WASTE_FLOW

Daily, start at 4:30 am.

Remark: PC_EHS_WASTE was the original metachain, but has been replaced by chain PC_EHS_WASTE_FLOW, in order to be aligned with all BW systems

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

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.