EHS 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
Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator
Around 90 users, worldwide. Each country can only report on its data.
2014 - SVT Roll Out Asia/Turkey => KT document "SVT RO // Knowledge Transfer" => https://drive.google.com/open?id=1yWblSq3wGJGdm-T7D97nWF3I7Ufeawe-HYb91RmZ26Q
2015 - SVT Roll Out Europe/USA/Canada => KT document "EHS-SVT-Documentation" => https://drive.google.com/open?id=1W-NDge82ePPYy4fBiMhr57DVYeBxzRsuyPxjK1ZWQuM
| 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 |
| ZBI_CA_EHS_P06 | EHS – Substance Volume Tracking Canada | Role perimeter / Based on authorization object ZCAEHSP06 / Country CA |
Usefull 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.
Usefull 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 (Application 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
The BUTA data will have to be loaded in cube REACH (SVT Analysis - EU (Rhodia) / CREHS06).
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| Country of Origin (C_CNTRY_O) | |
| Plant (C_PLANT) | See above explanation for role ZR_RCS_EHS_A07 |
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
Detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
Detail of frequency : monthly; weekly or else
if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016