OPLA provides dashboards and reports using analysis areas created on Agile Product Lifecycle Management (Agile PLM) data.These dashboards are classified into the following groups:
Product changes
Product engineering
Product quality
Product portfolio
The table below lists the acronyms used in this chapter.
Acronym | Expansion |
---|---|
AML | Approved Manufacturers List |
BI | Business Intelligence |
CAPA | Corrective and Preventive Action |
DM | Data Mart |
ECO | Engineering Change Order |
ECR | Engineering Change Request |
ETL | Extract-Transform-Load |
MCO | Manufacturing Change Order |
MDS | Multi-Dimensional Schema |
MTBC | Mean Time Between Cycles |
MTBF | Mean Time Between Failures |
NCR | Non-Conformance Report |
OBIEE | Oracle Business Intelligence Enterprise Edition |
ODI | Oracle Data Integrator |
PLM | Product Lifecycle Management |
PLM BI | Product Lifecycle Management Business Intelligence |
PLM DM | Product Lifecycle Management Data Mart |
PPM | Product Portfolio Management |
PQM | Product Quality Management |
PR | Problem Report |
SS | Stop Ship |
WBS | Work Breakdown Structure |
There are two types of dashboards available for Agile Product Lifecycle Management (Agile PLM) in OPLA:
Functional dashboards
Role-based dashboards
Functional | Role Based (Samples) |
---|---|
Customer Complaints | Quality Executive |
Non-Conformances | Quality Manager |
CAPA | Quality Analyst |
Audits | Change Analyst |
Change Orders | Component Engineer |
Manufacturer Orders | Component Manager |
Product Portfolio | Commodity Manager |
Configuration Manager | |
VP Engineering |
The table below describes all the standard dashboard pages.
Dashboard | Description | Prompt | Example Pages | Example Reports |
---|---|---|---|---|
Customer Complaints | Provides comprehensive and actionable insight into various aspects of Customer Complaints - trends, Open/Overdue volumes, and Cycle time and Failure modes. | Complaints Type, Calendar Year | Complaint Trends, Overdue Complaints | Top 10 product lines based on closed complaints, Overdue complaints by Aging |
Non-Conformance Reports | Provides comprehensive and actionable insight into various aspects of NCR's - trends, open/overdue volumes, cycle time and failure modes. | NCR Type, Calendar Year | Overview - NCR, Item NCR | Failure Mode Pareto Analysis, NCR Affected Items by Trend |
Corrective and Preventive Actions | Provides comprehensive and actionable insight into various aspects of CAPA - trends, open CAPA and cycle time. | CAPA Type, Calendar Year | CAPA Trends, Cycle Time | Closed CAPA by Dimensions, Open CAPA Status Cycle Time by Dimensions |
Audits | Provides comprehensive and actionable insight into Audits- trends, open audits and cycle time. | Audit Type, Calendar Year | Audit Trends, Open Audits | Audit Cumulative Trends, Top 5 Suppliers based on Open Audits |
Change Analyst | Enables you to track submitted changes and pending approvals | Change Analyst, Quarter | Submitted Issues, Change Documents | Open Change Orders by Status, Documents on Pending Change Orders |
Change Orders | Provides the ability to analyze volume, cycle time and trends of Change Orders. It also provides the ability to analyze the trends and reasons for Change Requests and Stop Ships. | Year, Quarter, Change Order Type | Open Change Orders, Item Changes | Open Change Orders Aging by Dimensions, Parts undergoing change by Part Type |
Configuration Manager | Enables you to manage the Change Order process with the ability to measure Cycle time and Volume. The analysis help you to identify issues related to process. | Quarter, Preliminary, Year, Quarter, Product Lines | Team Effectiveness, Process Effectiveness | Change Orders Aging by Change Analyst, Number of Closed Change Orders by Workflow Type |
Manufacturer Orders | Manufacturer Order functional dashboard provides the ability to analyze volume, cycle time and trends of Manufacturer Orders. | Year, Quarter, Month, Mfr Change Type | Mfr Order Trends, Open Mfr Orders, Cycle Time, Item Mfr Order | Open Manufacturer Change Orders by Dimensions, Changes Cumulative Trends |
Quality Executive | Provides Quality Executive with comprehensive and high-level view of complaint trends, failure modes and product line performance. | Year and Item Product Line, Calendar Year | Failure Mode, Product Line Performance | NCR Affected Items by Failure Mode, Closed CAPA Volume and Cycle Time |
Quality Manager | Provides comprehensive visibility into all aspects of quality in one or more product lines. | Year and Product line, Year Quarter Month | Product Line Performance, Supplier Performance | Complaints Trend and Cycle Time, NCR Trend by Supplier |
Quality Analyst | Enables analysts to track and manage open complaints, NCR and CAPA. | Not Applicable | Submitted Issues, Open Issues | Open Complaints by Status, Open NCRs by Days Open |
Component Engineer | Enables you to track progress of newly created parts and sign-off progress on Manufacturer Change Orders. | Mfr Part Creator, Item Creator, Manufacturer (AML), Manufacturer, Year, Quarter | NPI Manufacturer | Manufacturer part without Item, Top 10 Manufacturers based on AML count by Mfr part preference status |
Component Manager | Helps track key Part risks such as AML (Approved Manufacturer List) risk, Manufacturer Part Risk, and Part risk. It also helps Component Manager track newly created parts and their associated risks. | Year, Quarter, Product Lines, and Part family | NPI, Team Effectiveness | New Mfr Parts and Risk coverage by Part Family, Mfr Part Risk Effectiveness |
Commodity Manager | Enables you to track Manufacturer and Manufacturer Parts being considered for New Product development. It helps in early visibility of risks associated with new products. | Year, Quarter, Commodity, Product Lines | NPI, Commodity Analysis | Top Ten Commodities by Part Count, Top N Manufacturers based on AML Split |
VP Engineering | Provides ability to monitor Product design, quality and risk information. It also helps evaluate effectiveness of Product lines along key parameters such as mean time between changes and design KPI. | Year, Product Lines | NPI, Product Line Performance | Products with Pending Change,
Design Effectiveness and Product Risk |
Product Portfolio | This dashboard provides the ability to track progress and measure performance of a product portfolio. It has reports that assist in Strategic and Tactical portfolio management. It also provides details about Deliverables in the Project | Portfolio Name, Project State, Project Name, Product Line, Project Region, Project Type, Project Division, Program Name, Portfolio Name, Project Launch Year, Project Customer, Phase Type, Phase Name, Gate Type, Gate Name, Tasks, Task Owner Resource Pool | Projects, Portfolio, Phases and Gates, Deliverables | Top 5 projects with most schedule changes, Task Completion Rate, Current Phase Performance based on Cost Variance, Upcoming Gate reviews, Project Portfolio by Time and Deliverable Drill Down Report |
Product Management | This dashboard provides ability to use external data templates (.csv files) to populate and modify reports related to product management process. | Product Lines | Product Management | Late Projects by Product line & Scheduled launch date, Product Revenue - Plan vs. Actual |
The table below lists the standard Key Performance Indicators (KPI) in the OPLA application.
KPI | Description | Page |
Percentage Open Variance | Indicates the variance between the expected and actual number of 'Open' items in Complaints, Audits, NCRs, CAPA, Change Orders, Change Analyst, Configuration Manager, and Manufacturing Orders dashboards. | Overview page in all functional dashboards |
Percentage New Variance | Indicates the variance between the expected and actual number of 'New' items in Complaints, Audits, NCRs, CAPA, Change Orders, Change Analyst, Configuration Manager, and Manufacturing Orders dashboards. | Overview page in all functional dashboards |
Cycle Time Variance | Indicates the variance between the expected and actual Cycle Time for items in Complaints, Audits, NCRs, CAPA, Change Orders, Change Analyst, Configuration Manager, and Manufacturing Orders dashboards. | Overview page in all functional dashboards |
KPI - Projects | Indicates the number of projects as on date for the current year and the past year | Portfolio Page |
KPI - Average Project Duration | Indicates the average project duration for the current year and the past year | Portfolio Page |
KPI - Projects Under Execution | Indicates the number of projects that are work in progress for the current year | Portfolio Page |
KPI - Number of Projects Estimated late | Indicates the number of projects that have been estimated late | Portfolio Page |
KPI - Number of Projects completed to date | Indicates the number of projects completed as on date | Portfolio Page |
KPI - Number of Projects completed late | Indicates the number of projects that were completed late. | Portfolio Page |
Number of Projects estimated | Number of Projects that have exceeded the budget, effort and schedule | Project Page |
Guided Navigation directs you through the results obtained from Oracle BI Answers and helps provide insight into business issues, so that you can take appropriate actions. When based on common scenarios and best practices for your industry or organization, Guided Navigation allows you to see and analyze related issues by navigating to a related set of results, another dashboard, or a URL. Guided Navigation is specified using the Dashboard Editor.
The functional dashboards contain a Guided Navigation section that appears conditionally based on certain Key Performance Indicators (KPIs). When the system detects that one of these KPIs has reached its predefined threshold, a link appears in the Guided Navigation section to guide you to a Summary report for further investigation.
The table below lists sample guided navigations, threshold descriptions, and navigation target pages for the navigations that are delivered with the OPLA application.
Guided Navigation Link Name | Dashboard | Page | Condition | Navigation |
Overdue Complaints | Customer Complaints | Overview | ("- Volume Measures"."# of Overdue Complaints - Not Released"/"- Volume Measures"."# of Open Complaints - Not Released")*100 >75 | Customer Complaints --> Overdue Complaints Page |
Open Complaints without Expected Resolution Date | Customer Complaints | Open Complaints | # of Open Complaints - without expected resolution date returns data | Open Complaints without Expected Resolution Date |
Guided Nav Link 1 | Quality Executive | Overview | Open Complaints are 10 % above last 12 month average | Open Complaints by Product Lines |
Guided Nav Link 1 | Quality Executive | Overview | New NCR last month are 10 % higher than the 12 month average | Open NCRs by Product Lines |
Guided Nav Link 1 | Quality Executive | Overview | CAPA cycle time is 10 % higher than the 12 month average | Closed CAPA Cycle Time by Product Lines |
Guided Nav Link 1 | Quality Executive | Overview | No Audits were conducted in last 6 months. | New Audits by Product Lines |
Change Requests & Stop ships | Change Orders | Overview | Number of Open Change Requests and Stop Ships is greater than 90 days | Change Requests & Stop ships |
Elapsed Duration exceeds 75% of Scheduled Duration | Product Portfolio | Phases and Gates | Days elapsed exceeds 75%. Scheduled duration is greater than 1, and Phase Status Type is not equal to or is not in 'Complete' state. | Elapsed duration exceeds 75% of Sch duration |
The OPLA application supports a number of subject areas. Based on analysis focus the subject areas are grouped into the following analysis areas:
Product Risk
Product Change
Product Quality
Product Portfolio
The dimension Project is found in the following subject areas:
Product Change
Product Quality
Product Risk
By using the Project dimension the process owner can focus on processes impacting projects. For example, if you are a change analyst, you can identify the change orders that impact projects, and the name of the impacted project, enabling you to get them completed on time. The Project dimension helps you to answer such questions as:
What is the cycle time of change orders associated with my project?
How many items associated with the project have quality issues?
Product Risk analysis allows you to minimize risk on new products by helping to identify parts with risks.
For example:
Identify parts that have fewer manufacturer parts associated to them
Identify inactive manufacturer parts
Identify parts with no published prices
Identify parts with quality issues
Identify parts with compliance issues
Product Risk analysis has four subject areas. Each subject area contains specific measures and dimensions that are important to risk analysis. The four subject areas associated to Product Risk analysis are as follows:
Item
Item and AML
Manufacturer Part
Product Performance
Note The subject areas reports can drive the organization's tactical decisions, as it provides analysis pertaining to a specific measure and dimension. Management can use trend reports to understand the change from past trends to current trends, and analyze the impact of this trend change on the business over specific time period.
For more information on the measures available in every subject area, see subject area matrices.
The Item subject area measures the volume and risk associated with preliminary items and released items. In addition, by taking the item revisions into consideration, it also calculates the age of items on the basis of effectivity dates or released dates. You can analyze the item part risk by important Item dimensions such as lifecycle, product line, and part family.
This subject area contains items that are associated with manufacturer parts and those that are not associated with manufacturer parts.
Examples of some of the most common questions answered in this subject area are:
What percent of items belonging to a specific product line have price data attached to them?
How many released items have pending changes associated with them?
What is the yearly item lifecycle age with respect to part category?
When to use this subject area | To analyze part risks |
Key Measures | Counts - for example, number of preliminary items
Risk measures - for example, % items with manufacturer part and item age |
Key Dimensions | Part Family
Lifecycle Product Lines Supplier Creator Project Name Project |
The Item and AML subject area helps to identify the manufacturer or manufacturer part risk on a part or a product line.For example:
To avoid downstream supply chain issues, you can determine the minimum number of manufacturer parts per item.
You can analyze the impact of a manufacturer on a product line.
You can monitor parts impacted by obsolescence
This subject area considers only those items associated with manufacturer parts.
Examples of some of the most common questions answered in this subject area are:
What are the average numbers of parts per item by part family?
What parts are sole-sourced?
How many items are at risk due to obsolete parts?
When to use this subject area | To determine the manufacturer or manufacturer part risk on a part or a product line. |
Common Measures | #Mfr
#Released Items #Mfr Parts Avg Mfr parts per Item Items with one Mfr only |
Common Dimensions | Part Family
Product Line Item Number Mfr Part Lifecycle Mfr Location Mfr Part Family Mfr Part Lifecycle Phase Mfr Preferred Status Mfr Part Creator |
The Manufacturer Parts subject area helps you understand the risks associated with manufacturer parts.For example:
Lack of price and compliance.
You can identify obsolete parts.
This subject area considers only manufacturer parts.
Examples of some of the most common questions answered in this subject area are:
How many manufacturer parts are obsolete by product family?
By product family, how many manufacturers are we dealing with?
What are the part families that have the highest number of parts to be qualified?
When to use this subject area | When the subject of analysis is manufacturer or manufacturer parts. |
Common Measures | Number of manufacturer parts
Number of manufacturers |
Common Dimensions | Mfr Part Number
Mfr Part family Mfr Lifecycle Phase Project |
The Product Performance subject area contains similar measures & dimensions as described in the Item subject area. In addition, the Product Performance subject area consolidates the affected item measures belonging to Product Change (such as # Change order Affected Items, # Change request Affected Items etc.) and Product Quality (such as # Problem Report Affected Items, Non Conformance Affected Items etc.). These measures can be analyzed by limited Product dimensions such as Item, Product line, and Item Type enabling 360 degree views of Product and/or Item.
Examples of some of the most common questions answered in this subject area are
What Item Product lines have most Quality and Changes?
What Items have most Quality & Change?
Examples of some of the most common questions answered based on external data are:
What product lines have high parts per million defects based on unit-sales?
What part types have high parts per million defects based on units-received?
What Product Changes need to be delayed to reduce impact on inventory?
What 'End of life' decisions need to be delayed based on demand?
When to use this subject area | To gain a 360 degree visibility into Products and/or Items. |
Common Measures | Counts - Affected Item counts, such as:
# PR Affected Item # NCR Affected Item # CAPA Affected Item # Audit Affected Item # Change Order Affected Item # Change Requests Affected Item # Mfr Order Affected Item # Stop Ship Affected Item External Template measures: Product Planned Revenue Product Actual Revenue Product Planned Demand Product Actual Demand Product Planned Units shipped Product Actual Units shipped Product Planned Units received Product Actual Units received Product Planned Inventory Product Actual Inventory Product Planned Inventory value Product Actual Inventory value |
Common Dimensions | Part Type
Product Lines |
The Product Quality analysis area provides information on trends and cycle times across key quality areas. This area also handles non-conformances issues. Product Quality analysis has four subject areas. Each subject area contains specific measures and dimensions that is important to product quality. The four subject areas associated to Product Quality analysis are as follows:
Customer Complaints
NCR
CAPA
Audits
For more information on the measures available in every subject area, see subject area matrices.
The Customer Complaints subject area allows you to obtain reports on volume, cycle time, severity, status, and aging of customer complaints across product lines. Customer complaints are sourced from Problem Reports created in Agile PLM. Examples of some of the most common questions answered in this subject area are:
How many complaints were recorded in the last quarter per product line? What is the trend?
How quickly are complaints getting resolved?
What is the workflow cycle time between the originate state and released state for customer complaints this week?
What are the cycle times for each status step? Where are the bottlenecks?
When to use this subject area | When a business has queries about complaints on a given product. |
Key Measures | Count of New
Open and Closed Complaints Cycle Time of Complaints Aging Analysis in Buckets of Time, such as, 11-20, 21-30 days |
Common Dimensions | Customer
Supplier Product Lines Severity Status Resolution Project |
Non-Conformance Reports (NCR) subject area allows you to analyze the following:
Volume
Cycle Time
Aging of NCR
Examples of some of the most common questions answered in this subject area are:
What are common Non-Conformances?
What is the trend in closing NCR?
What is the aging of open NCR?
How many NCRs are in the various aging buckets?
What 20% of failure modes cause 80% of NCR?
When to use this subject area | To answer business questions about NCRs recorded on the product. |
Key Measures | Count of new, open and closed NCRs
Cycle time of NCRs Aging analysis in buckets of time such as 11-20,21-30 days |
Common Dimensions | Customer
Supplier Product Lines Severity Status Resolution |
The Audits subject area allows you to analyze the following items that have taken place in the organization:
Count
Turnaround Time
Aging Of Audits
Examples of some of the most common questions answered in this subject area are:
How many audits have been conducted this year?
How many audits did not show any change over the past year?
What is the average cycle time of an audit?
What are the major areas of concern based on the audit results?
When to use this subject area | To answer business question about audits conducted on the product or process. |
Key Measures | Count of new, open and closed audits
Cycle time of complaints Aging analysis in buckets of time such as 11-20,21-30 days |
Key Dimensions | Customer
Supplier Product Lines Status Audit Result Project |
Corrective and Preventive Actions (CAPA) subject area allows you to analyze the following:
Volume
Cycle Time
Aging of CAPA
Examples of some of the most common questions answered in this subject area are:
Which status changes take the longest time?
How many CAPAs are overdue?
How many CAPAs have resulted in changes?
When to use this subject area | To answer business question is about CAPA. |
Common Measures | Count of new, open and closed CAPAs
Cycle time of CAPAs Analysis in buckets of time, such as, 11-20, 21-30 days |
Common Dimensions | Customer
Supplier Product Lines Category Status Project |
Item Quality subject area allows you to analyze the following:
Items affected by complaints (supports failure mode and affected item analysis and the quantity affected analysis)
Items affected by NCR (supports failure mode and affected item analysis and the quantity affected analysis)
Items affected by CAPA (supports affected items analysis)
Items affected by audits (supports affected items analysis)
Examples of some of the most common questions answered in this subject area are:
How many items in this product line are reported in quality incidents?
What are the failure modes?
When to use this subject area | Business question is on the items affected by CAPA, Customer Complaints, NCR and Audits. |
Common Measures | Number of affected items with changes
Number of failure modes |
Common Dimensions | Failure Mode
Item Type Item Product Line Item Commodity Item Part Family Project |
The Product Changes analysis area provides information on trends and cycle times related to the following:
Change Orders
Manufacturer Orders
Engineering Change Requests
Stop Ships
Deviations
The Product Changes analysis area has five subject areas. The five subject areas associated to Product Changes analysis are as follows:
Change Orders
Change Requests
Item Changes
Mfr. Change Orders
Stop Ships
Deviations
For more information on the measures available in every subject area, see subject area matrices.
The Change Orders subject area allows you to analyze the following:
Volume of processed Change Orders
Time taken by Change Orders to move from one stage to the next stage (within a workflow)
Aging of Change Orders
Sign-off cycle time by users and user groups assigned for the sign-off responsibility
The Change Orders subject area also allows you to measure the count of first time right change orders.
Examples of some of the most common questions answered in this subject area are:
Who are the analysts with most open change orders?
What are the new change orders by product lines?
How many change orders have been rejected in the last quarter?
When to use this subject area | To answer business questions on age, cycle time, volume and sign-off of change orders. |
Key Measures | Count of New Change Orders
Open Change Orders Cumulative Closed Change Orders Change orders open between 11-20 days First Time Right Closed and Released Change Orders Approvers Modified Bill of Materials |
Key Dimensions | Product Line
Category Reason for Change Project |
The Manufacturer Change Orders subject area allows you to analyze the following:
Volume
Cycle Time
Aging of Manufacturer Change Orders
Sign-off Cycle Time by the Sign-off Users
Examples of some of the most common questions answered in this subject area are:
What are the open manufacturer change orders per originator?
What are the reasons of change that are showing spike this year in comparison with the last year's record?
Which categories have the highest cycle time?
What was the cycle time for the manufacturer change orders that were closed last quarter?
When to use this subject area | To answer business questions (with regards to manufacturer change orders) on age, cycle time, volume, and sign-off. |
Common Measures | Volume
Sign-off Cycle time Aging Redline First Time Right |
Common Dimensions | Product Line
Category Reason for Change Project |
The Change Requests subject area allows you to analyze the following:
Volume
Cycle Time
Aging of Change Requests
Sign-off Cycle Time by the Sign-off Users
Examples of some of the most common questions answered in this subject area are:
What is the current status for open change requests?
What was the cycle time for change requests that were closed last quarter?
Which change requests have the highest cycle time?
When to use this subject area | To answer business questions (with regards to change requests) on age, cycle time, volume, and sign-off. |
Common Measures | Count of New Change Requests
Open Change Requests Cumulative Closed Change Requests Change Requests open between 11-20 Days First Time Right Closed Released Change Requests and Approvers Sign-off Cycle Time |
Common Dimensions | Product Line
Category Reason for Change Project |
The Stop Ships subject area allows you to analyze the following:
Volume
Cycle Time
Aging of Stop Ships
Sign-off Cycle Time by the Sign-off Users
Examples of some of the most common questions answered in this subject area are:
What is the current status on open stop ships?
What is the current trend on stop ships per product line?
How many new stop ships occurred this year?
When to use this subject area | To answer business questions (with regards to the stop ship subject area) on Age, Cycle Time, Volume, and Sign-off. |
Common Measures | Count of New Stop Ships
Open Stop Ships Cumulative Closed Stop Ships Stop Ships open between 11-20 days First Time Right Closed Released Stop Ships and Approvers Sign-off Cycle Time |
Common Dimensions | Product Line
Category Reason for Change Project |
The Deviations subject area allows you to analyze the following:
Volume (specifically changes in volume by time)
Cycle Time (notably you can measure cycle times between statuses, and measure cycle times within a status)
Aging of Deviations across category and reason for change
Analyze the sign-off cycle time by the sign-off users
Examples of some of the most common questions answered in this subject area are:
What are the new deviations by product lines?
What is the current status for open deviations?
Which deviations have the highest cycle time?
What was the cycle time for deviations that were closed last quarter?
When to use this subject area | To answer business questions (with regards to the deviations subject area) on Product, Cycle Time, New Volume, Open Volume and Closed Volume. |
Common Measures | Number of new Deviations by month, quarter, or year
Percent change of open deviations from this month to last month Number of open deviations that are between 31 to 40 days old Number of deviations that closed within the last 90 days |
Common Dimensions | Time
Changes Product People Workflow Flags Project |
The Product Portfolio analysis area helps you to manage the following:
Product pipeline
Project schedules
Phase Gate processes
Prioritize and monitor Project progress and costs
Identify schedule risks
Monitor project Cycle Time
The Product Portfolio analysis area has five subject areas.
The five subject areas associated to Product Portfolio analysis are as follows:
Project Summary
Phase Gate
Project Detail
Portfolio Summary
Program Summary
For more information on the measures available in every subject area, see subject area matrices.
The Project Summary subject area provides you with key metrics to measure project health, phase health, and helps in understanding the impact of baseline over schedule duration.
You can analyze project executions at a macro level by aggregating projects by portfolio and key business dimensions.
For example:
Product Line
Region
Division
Project Type
The aggregated task measures (such as number of tasks below project) aggregates all tasks. That is, parent tasks and child tasks.
For the definitions of Tasks, see the PPM Analytics - Best Practices section.
Examples of some of the most common questions answered in this subject area are:
Which projects in my product line are over schedule, over budget, or require more effort?
Which projects/phases are on track to finish this month?
Which projects have been baselined the most?
How many active projects are there in my portfolio?
Which completed projects were the best executed projects?
Which projects are scheduled for launch in the next year?
External data templates bring additional information into Project Summary subject area.
External data templates help answer the following questions:
What are the launch risks to Top-5 product projects by revenue potential?
What Projects are consistently over budget?
These measures qualify only with limited dimensions and the same is described in the Appendix.
When to use this subject area | When you need to understand project execution at a macro level. |
Key Measures | Count of projects begun or finished this year
Count of projects that are over budget, over schedule, or requires too much effort Count of off-track tasks in a project Average project schedule or actual project durations Average duration variances Cost and effort variances External data template: Project Forecast Revenue Project Actual Revenue Project Planned Total Cost Project Actual Total Cost |
Common Dimensions | Product Line
Region Division Project Type Customer Portfolio Program Project Phase and Gate |
The Phase Gate subject area allows you to analyze projects in terms of their performance at the decision gates. In addition, you can determine the following:
Which decision gate the project is at
The number of deliverables holding up the project before it can reach the next phase
Trends of business assumption projections that were made at the project approval stage (may require additional configuration or customization)
Examples of some of the most common questions answered in this subject area are:
What is the distribution of active projects by decision gate?
What projects are in the launch gate? How many tasks are still pending?
The number of decision gates that are behind schedule.
Which decision gates are the ones that are delayed the most?
When to use this subject area | When you need to analyze project performance with decision gate performance |
Common Measures | Count of gates
Count of delayed gates Gate schedule variance days Project cost remaining Number of tasks remaining on a particular phase Scheduled duration days to Decision Gate Actual duration days to Decision Gate Gate Cycle Time (pending exit date to complete entry date) |
Common Dimensions | Project-product Line
Region Division Project Type Customer Portfolio Program Project Phase and Gate |
The Project Detail subject area helps you gain detailed visibility into tasks associated with your projects.
Use this subject area to identify the following:
Completed tasks
Tasks that did not start on time
Tasks estimated for late completion
Delayed Gates (not just Decision Gates)
Examples of some of the most common questions answered in this subject area are:
Which tasks are running behind schedule?
Who are the task owners with the most number of delayed tasks?
Which tasks are scheduled to begin and which tasks are scheduled to finish in the next two weeks?
When to use this subject area | To analyze the project at a task level. |
Key Measures | Activity Duration
Gate Duration Activities Cost Gate Cost Number of Deliverables Gates # Deliverables on Activities Scheduled Date Variance Days Over First Snapshot Estimated Date Variance Days Over First Snapshot |
Key Dimensions | Product Line
Region Division Project Type Customer Portfolio Program Project Phase Gates Activities |
The Portfolio Summary subject area allows you to compare the budget that was set at the portfolio level with the actual total costs from all the projects in the portfolio.
For information on how to set up the domain values to enable portfolio, see Oracle Product Lifecycle Analytics Data Mapping and Configurator Guide.
When to use this subject area | To analyze portfolio |
Key Measures | Number of portfolios
Portfolio cost variance |
Key Dimensions | Portfolio
Scheduled start date and end date Item name Program health |
Program Summary subject area can be used to analyze Programs.
The metrics available in this subject area help to compare the Budget set at a Program level with summation of Actual costs from Projects that belong to this Program.
For information on setting up domain values to enable portfolio, see Oracle Product Lifecycle Analytics Data Mapping and Configurator Guide.
When to use this subject area | To analyze programs. |
Key Measures | Number of programs
Program End Date Variance Program Total and Actual Cost |
Key Dimensions | Program
Scheduled Start Date and End Date Item Name Program Health Note Cannot analyze the Program Summary subject area using the portfolio dimension |
It is important to understand the following common scenarios that form the basis of most of the Item, Mfr, and Item and AML reports.
When using Item and AML subject area, we recommend that you create Reports for the Global Items with latest effective revision that are not obsolete. Lifecycle can be used as a dimension, but when there is more than one lifecycle per revision, some aggregation of data may not be valid. Average of data may provide correct results in these use cases.
Use the out of the box filter, 'filter-latest item revisions' to create reports that filter only the latest revision of the Item.
The query used in the filter is as given below:
Site is equal to / is in Global
AND Change Class Type is equal to / is in Change Orders, Manufacturer Orders
AND Is Latest Rev is equal to / is in YES
AND Lifecycle is not equal to / is not in Obsolete
AND REV is not null
OR REV is not equal to / is not in Introductory
For simplified interpretation, we recommend you to use dimension and measure combinations from same dimension/measure group. For example, Item dimensions with Item measures.
For other combinations, interpretations may be necessary. The contexts within each measure provide explanation as required.
Use Item Number, Rev, Site to get a detailed report by Item and revision. Use Item Number, Lifecycle to get a detailed report of Items by lifecycle.
Some measures are appropriate for creating reports and analyzing the trend over time. For example, AML split distribution in the past vs. present. In such situations, all versions of the Item need to be included with the Time dimension. Even obsolete items need to be included to get the correct analysis.
Use the out of the box filter, 'filter-all item revisions' to create reports for all revisions of the Item.
The query used in the filter is as given below:
Site is equal to / is in Global
AND Change Class Type is equal to / is in Change Orders, Manufacturer Orders
AND REV is not null
OR REV is not equal to / is not in Introductory
Inclusion of this filter does not automatically consider count of every revision of the item. For example, if there are two items with three released revisions each, the result for # Items released displays 2. When you combine the # Items released with Item number and revision, all revisions of every item are counted.
Time dimension is not valid with measures, such as Item Age within Item Subject Area, and measures where aggregation is by averaging data.
Lifecycle can be used as a dimension, but when there is more than one lifecycle per revision, some aggregation of data may not be valid. Summation of data gives correct result.
Site = Global;
Class Type = Change Orders, Manufacturer Orders;
Rev not equal to' Introductory' or not equal to NULL;
Time
Use Item Number, Rev, Site to get a detailed report by Item and revision
Use Item Number, Lifecycle to get a detailed report of Items by lifecycle.
You can also filter the detailed report by a specific item number, to view the trend of items over revision or lifecycle.
Caution: Do not use the recommended filters and dimensions with the following measures: # Item with Pending Changes # Items (Prelim) # Items (All) |
OPLA provides revision specific information for few measures and dimensions.
Example: Description and AML. Calculations specific to the remaining Measures and Dimensions use the data specific to the latest revisions for all revisions.
We recommend using certain best practice templates to organize your projects so that the OPLA analytical reports on these projects give accurate results.
You need to identify and configure the Phase sub class to a Phase domain value in the OPLA Configurator.
On the basis of this configuration, OPLA makes the following assumptions:
Project is identified to be one level above Phase
Tasks are activities that are one or more levels below Phase
In addition, you need to identify and configure the Decision Gates using the OPLA Configurator. These configurations along with usage of best practice templates shown below are required for OPLA to provide the right information in the analysis areas.
Template 1:
Gate is at the same level as the Phase |
Template 2:
Gate is within a Phase |
Project 1
Task 1.1 Task 1.1.1 Task 1.1.2 Task 1.2
Task 2.1 Task 2.2
Task n.1 Task n.2 Task n.n
|
Project 1
Task 1.1 Task 1.1.1 Task 1.1.2 Task 1.2 Gate 1
Task 2.1 Task 2.2 Gate 2
Task n.1 Task n.2 Gate n |
For more detailed metrics on Phases, you can split Phase subclasses into Phase 0, 1, 2, and so on.
While it is possible to look at a flat list of all Tasks below the Phase, OPLA does not maintain or display a tree of tasks. For example, in the above template, it is possible to get Tasks under Phase 1 such as Task 1.1, 1.1.1 & 1.1.2 but it is not possible to get a list of Tasks under Task 1.1.
OPLA does not support a Phase subclass under another Phase subclass.
OPLA supports Portfolio and Program analysis. The information that is provided in these areas is dependent on the following:
Domain value configuration of Portfolio and Program in the OPLA Configurator
Usage of PLM Reference number in Agile Product Lifecycle Management (Agile PLM) Product Portfolio Management
PLM Reference number is available from Agile 9.3 version onwards. If you are a 9.2.2.x customer, use a Defined field instead of PLM Reference number.
Use PLM Reference Number on:
Portfolio to refer to one or more projects or programs or both. You cannot use PLM Reference Number on Portfolio to refer to other Portfolios.
Program to refer to one or more Projects. You cannot use PLM Reference Number on Programs to refer to other Programs.
Project to refer to Items. Reference to any other object will be ignored by OPLA.
Portfolio and Program referred to above are the subclasses configured as Domain Values in OPLA Configurator.
User Defined fields (P2/P3) on:
Portfolio to associate with one or more programs, projects or both. You cannot use the Defined field on Portfolio to refer to other Portfolio.
Program to associate with one or more projects. You cannot use the Defined field on Program to refer to other programs.
Project to refer to Items. Agile OPLA does not consider references to any other object.
PPM has category fields. In OPLA, these fields are assumed to be associated with the project and exposed as Project dimensional attributes.
Use these fields to capture information regarding the projects. If these fields are associated with Phases or Tasks, they can be analyzed using the Project Detail Subject Area.