Go to primary content

Oracle Product Lifecycle Analytics Security Guide Release 3.5 E70278-01 |
| Contents

Previous | Next |

# 2 OPLA Architecture Overview

You can deploy OPLA various database and application components with different hardware and machine configurations. Depending on the performance criteria set and based on the source (Agile PLM or Agile PLM for Process) database size, volume of data changes in the source database, IT network, infrastructure constraints, and business requirements.

## 2.1 OPLA Architecture

OPLA is designed and developed using a layered Data Warehouse and OLAP architecture on Oracle enterprise technologies. At the bottom of the stack is the Agile PLM OLTP Agile PLM for Process OLTP database which is optimized for core transactions. The database is the source data system for OPLA, but it can be extended to load data from other data sources.

Layer 2 includes the ODI and PL/SQL ETL tasks for extracting data, including metadata, from the Agile PLM source system and loads it into the Staging Schema (Layer 3). Layer 4 provides ETL tasks using ODI and PL/SQL for extracting data from the operational data store, then transforms, aggregates, and loads data to the pre-defined multi-dimensional schema in Layer 5. MDS as a set of star schemas that were designed based on top-down business analytical requirements. Layer 6 provides the pre-built analytical repository for OBIEE and its metadata repository. Layer 7 has the pre-built roles-based and functional dashboards with a pre-defined set of reports and KPIs along with alerts and guided navigation for providing actionable insights into PLM data.

The following figures show the basic product architecture for OPLA with Agile PLM and for OPLA with Agile PLM for Process, respectively.

Figure 2-1 OPLA with Agile PLM

Figure 2-2 OPLA with Agile PLM for Process