You are here: Primavera Unifier Administration Mode > Shell Administration > How to create and set up Shells > Shell template modules and managers

Shell template modules and managers

In shell templates you can prepare modules and managers to make standardized templates, which ensure project uniformity and greatly reduce the potential for errors. You can have different templates for different project models. For example, you can have one template for "cookie-cutter" projects that do not change, and you can have another template for projects that might incur substantial changes. Primavera Unifier will copy any prep-work when you use the template to create a new shell, a process called cloning. Manager and module availability can differ depending upon WBS or generic code specification in Primavera uDesigner. See Create a shell by copying a template or shell.

Managers and modules available in all shell templates (both WBS and generic codes)

•

Member Companies: In order to make partner companies that you added at the company level available in your projects, you add them in Member Companies. Member companies added to a shell template automatically copy to a shell during cloning. See Managing Member Companies.

•

Access Control: For modules and managers included in a shell template, you can assign user-mode permissions. Permissions set in a template will automatically copy to a shell during cloning. Keep in mind, records created in user mode may require permission assignment in user mode. See Managing permissions and access control.

•

User Administration: Users and groups added to a template are copied by default from the template to a new shell during cloning. See User and Group Administration.

•

Users—Users added to a template automatically copy to the shell during cloning. Users added to shell templates cannot be deleted, only inactivated.

•

Groups—Groups added to a template, and any users added to these groups, automatically copy to the shell during cloning.

•

Setup:

•

Business Process—You have the option to copy all, or none, of the business processes and their setups that were added to a template. See Setting up Business Processes. If you added a single-record business process to a template, and created a record, that record with all of its data will be copied during cloning. See Single-record business processes.

•

Dashboards—You can define dashboards in a template and opt to include them when you clone a new shell from the template. See Creating a shell instance dashboard in a shell instance or template.

•

Gates—Gates provide a means of automating when a project moves to the next phase. You can define gates in a template and opt to include them when you clone a new shell from the template. See How to Set Up Gates.

•

Planning Manager—This is where you can plan for new projects, and create proposals and forecasts for projects already running in Primavera Unifier. See About the Planning Manager.

•

Resource Manager—This is where you can set up and manage personnel resources in a company, project, or shell. See About the Resource Manager.

•

Information: This is where single-record business processes exist. When you clone a template, any single-record business processes are copied as well. See Single-record business processes.

•

Configurable Modules > Configurable Managers (CM1 through CM25)>: Configurable Managers are designed in Primavera uDesigner, and have flexible coding structures to allow data collection and analysis. See About Configurable Managers.

•

Document Manager: You can create a folder structure for the Document Manager that can be used across shells. These can be created from Folder Structure Templates, or folders can be added manually. Unlike Folder Structure Templates, you can also assign users folder-level permissions (if they are in the shell template), and can import folders and folder properties. See About the Document Manager.

•

Reports: You can create one or more user-defined report templates, which will be used for shell-level user-defined reports. See About User-Defined Reports. You can import user-defined reports into shell templates from shell templates in other companies and Primavera Unifier environments, for example, from uStage to production. See "Importing User-Defined Reports into Project or Shell Templates".

Selections available in only Generic code shell templates

•

Configurable Modules > Generic Cost Manager (CM0): The Generic Cost Manager captures cost-related transactions in a Generic Shell. These can include costs like rent, lease payments, or landscape care that are based on time scales such as monthly, quarterly or yearly. Each generic shell can have one Generic Cost Manager. See About Configurable Managers.

•

Cost Manager > Commitment Summaries: In the same way the schedule of values summarizes all cost information related to a particular commitment business process, the commitment summary tracks commitment record information. See Setting up the Commitment Summary Template.

Selections available only in WBS code shell templates

•

Cost Manager:

•

Cash Flow—Cash flow is the distribution of cost over time - in project management terms, it is the movement of cash into or out of a project measured during a specific time period. See About Cash Flow.

•

Cost Sheet—The cost sheet provides detailed accounting of the project's budget and costs. You can create one cost sheet per template or shell. See Setting up Cost Sheets.
Tip! Set up the standard cost sheet template and copy it into the shell template.

•

Earned Value—The earned value module provides quantitative tracking information about project or shell status using earned value analysis.you can only set User Mode permissions in a template. See About Earned Value Sheets.

•

Funding—The Funding Manager helps you to keep track of where project funding comes from and how it is being spent. You can create one funding sheet per template or shell. See Setting up the Funding Manager.

•

Schedule of values (SOV)—The schedule of values summarizes all cost information related to a particular commitment business process. This is where you define structures for general spends and/or payment applications. You can define a General Spends SOV structure by copying from an SOV template in the Templates log. For Payment Applications, you must define the SOV structure manually based on the payment application business process. This means you must first complete the business process setup for the payment application BP before you can create the structure. See Setting Up Schedule of Values (SOV).

•

Rules: You can define shell-level cost or funding rules. See Creating Rules and Rules Templates.

•

Schedule Manager:

•

Schedule Sheet—A schedule template will be used to create the schedule sheet. Like the cost sheet, once this is created, it cannot be deleted. See About the Schedule Manager.

•

Custom Calendars—Primavera Unifier allows you to create Custom Calendars to be used by the Schedule Manager. See Create a custom calendar in the schedule manager

Oracle Corporation