Access Management
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
ZR_RCS_CA_M09 | PS - Project Costs | Role menu for all project costs queries |
ZBI_RCS_PS_A02 | Project Costs and Structures Analysis - End User role | Application Role:
|
ZBI_RCS_CO_A21 | CBS Project costs Reporting Analysis - End User role | Application Role:
|
- Authorization role : ZR_RCS_PM_A02: Maintenance Orders Applications - End User role
- Role menu : ZR_RCS_CA_M08: PM - Plant Maintenance
List of authorization objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| 0COMP_CODE;C_COMPCDE;C_PMORDER__0COMP_CODE | Company, role: ZR_*_CA_P01 |
DataFlow
Overview
Technical Rules on Workbench
Data is extracted from standard extractors from system WP1 400: 2LIS_17, 0PM_OM_OPA_1 & 2, 0CA_TS_IS_1
Dependencies:
- It shares some extractors (2LIS_17_I3OPER, 0PM_OM_OPA_2) with MECANO.
- Data is consumed by ORACLE by the broadcast of a workbook (BCAST_ORACLE_PM) with PM costs, which is integrated manually by IS PM team.
- Data is loaded in cube CUB_PM for QV dashboard RCS KPI
- Costs data from all three systems (WP1/PF1/RHO) is used in FI cubes
Functional Rules:
- Alternative Labeling is used on Functional Location in the source system. The alternative label is loaded in the master data attributes.
Reporting
- CATALOG - Industrial & Planning Reporting (in the tab Maintenance)
Several topics are covered by BEx reports :
- Work Orders with Maintenance Plan
- Work Orders with Equipment
- Notifications by Status and Causes
- Planned and Actual duration on Operations
- Work Orders and Operations by Status and Priority
- Monthly Costs
- Functional Location and Equipment Attributes
- Consumption of Materials on Work Orders
- Work Orders Costs by Vendor
- MTBF (Mean Time Between Failure)
- Backlog on Operations
Broadcast
- BCAST_ORACLE_PM (Weekly) : Extraction of actual costs year to date for current year send to PM IS Team for Chalampé plant, and the data is loaded manually in ORACLE Hyperion by PM Team.
- RCS_KPI_PM_ALL (Monthly) : Extraction of KPI PM. It has been unscheduled on SEP 2015 after a usage survey from IS Reporting Team and is not running anymore.
Dependencies with other applications
We should have the information where the application is sending or receiving information (e.g. APD open hub)
Data Loading
Info Providers and objects loaded
Detail of process chain, list + link between or special event done for the loading
| Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
Data loadings
Info providers and objects loaded
Infoproviers and Master data are grouped in the Application Area AREA_PM.
Process Chains included in the Global RSP_DAILY Process Chain:
- ZPC_MD_ATTR_RCS (For shared master data attributes and texts)
- RCS_PM_KPI (Load Cubes for RCS KPI application used by QV dashboard)
- RSP_PM
- RSP_PM_ACETOW (Load PM Costs data from RHO system for FI cubes)
- RSP_PM_SOLVAY (Load PM Costs data & Commitments and orders distribution rules from PF1 system for FI cubes)
- PC_PM_01
Others Process Chains:
- PC_PM_ORDER_WEEKLY
- PM_BACKLOG
Loading frequency
- Daily loadings Monday to Friday
- Weekly loadings for PC_PM_ORDER_WEEKLY & PM_BACKLOG
Average performance
The main process chain RSP_PM run in about one and a half hours.
PM Extractors (2LIS_17) are set up in delta with a delta queue. Costs on PM orders are loaded in full mode.
Historization
We keep all the data in the DSO and Cubes. Archiving is done on Source System.
Data Quality Control
Operational Documentation
Procedures
<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>
Scheduling
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
Monitoring
<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>
Error Handling
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
Known Bugs
<List the existing bugs, its criticity, workarounds and resolution plan.>
Roadmap
<List past & future evolutions for the application (including links to MED/FSD/TSD)>