You are here: Primavera Unifier Administration Mode > About Configurable Managers

About Configurable Managers

A configurable manager does not replace existing managers but provides additional functionality. Configurable managers have flexible coding structures that allow you to analyze your data. To Primavera Unifier users, a configurable manager behaves like any other module in the application. You design configurable managers in Primavera uDesigner. You can create configurable managers at the shell, project, or company level. You can have up to 25 managers.

There are two types of configurable managers.

•

Code and records-based: This type of configurable manager allows users to define codes and capture data using records. You can create multiple classes of records and sheets, each with it own coding structure. For example, a Parts Manager could provide the following functionality:

•

Categorize parts by type or class

•

Track inventory at various locations

•

Maintain basic cost information

•

Track parts transactions (bought, sold, received, or shipped)

•

Monitor costs generated by transactions

•

Code-based: This type of configurable manager allows users to define codes and work with sheets to analyze information generated manually or from BPs. This manager consolidates all the data in one sheet. For example, a Condition Assessment Manager could provide the following functionality:

•

Define a building systems code structure at the company, project, or shell level

•

Design multiple BPs to track and calculate:

•

Maintenance requirements

•

Inspections

•

Work orders

•

Repairs

•

Costs of maintenance

•

Deficiency costs

•

Renewal costs

•

Provide various indices, such as a Facility Condition Index, to monitor the condition and usability of facilities

Summary of Differences

The following table itemizes the differences between a code-based manager and a code-and-record-based manager.

Code-Based Manager

Code-and-Record-Based Manager

Uses an attribute form to create the codes that will appear on the sheet.

Uses an attribute (detail) form to define code “classes” for categorizing the items on the sheet and for collecting item details. Provides users a way to drill down to specific information from the sheet.

Uses a single sheet for analyzing information about the items being managed. These items are added to the sheet manually by the user. Records do not exist for code-based managers; the values collected for a code-based manager exist only on the sheet. Values on this sheet can be gathered from business processes or manually entered.

Uses multiple sheets (one for each class) for analyzing information. New items are automatically added to the sheet from item records created by users filling out an attribute (detail) form.

This type of manager gathers values from Cost and Line Item types of BPs for the manager sheet.

The code structure for this type of manager is created in Primavera Unifier by the administrator.

The code structure for this type of manager is created in Primavera uDesigner.

Cannot operate across shell hierarchy.

•

Can operate across the shell hierarchy. To facilitate this capability, one or more data pickers are usually designed to help users navigate to records within the hierarchy.

•

Sheets for these managers will display rollup data from across shells, and users will be able to drill down from the sheet to the business process transaction

The manager sheet:

•

Is created manually by the user in Primavera Unifier

•

Shows codes as rows in a flat or tree format

•

Can show rollup values from company and shell BPs at any status; values appear as columns on the sheet

•

Does not support time-based filtering using queries.

The manager sheet:

•

Is created manually by the user in Primavera Unifier; then automatically populated with the information gathered from class records

•

Shows the records as rows in a flat or tree format

•

Can show rollup values from company and shell BPs at any status; values appear as columns on the sheet

•

Can update item records directly from sheet

•

Supports the Primavera Unifier rules engine

•

Does not support time-based filtering using queries

About Configurable Managers

Setting up A Code and Records-Based Configurable Manager

Oracle Corporation