Why Engineering Project Templates Matter in Primavera P6

For engineering organizations managing multiple capital projects, repeatability and standardization are not just nice-to-haves—they are cost and schedule drivers. Primavera P6 project templates allow you to pre-configure the Work Breakdown Structure (WBS), activity logic, resource assignments, cost accounts, and calendars that reflect your company’s standard execution approach. Instead of starting each new project from scratch, you apply a proven template, cut setup time by hours or even days, and drastically reduce the risk of omitted tasks or misaligned resources.

Engineering projects share recurring phases: feasibility, front-end engineering design (FEED), detailed engineering, procurement, construction, and commissioning. A well-built P6 template captures these phases and their dependencies, so every project inherits the same baseline logic. This consistency makes it easier to compare performance across portfolios and to enforce corporate governance requirements.

Step 1: Structure Your Enterprise Project Structure (EPS) for Template Reuse

Before creating a single activity, ensure your EPS is organized to support template inheritance. The EPS is the hierarchy that holds all projects in Primavera P6. Templates live inside the EPS as special projects, and their properties—like resource assignments, calendars, and costs—can be inherited by child projects.

Create a dedicated node for templates, for example Corporate Templates > Engineering. Assign a responsible manager and ensure the node has appropriate security settings so that only authorized planners can modify the template. If your organization uses rate tables or global calendars, set those at the EPS level so your template can reference them.

Best Practice: Node Permissions

  • Give read-only access to most users on the template node.
  • Allow full control only to senior planners who maintain the master templates.
  • Use Project Codes to tag templates (e.g., “Engineering,” “Civil,” “Oil & Gas”).

External reference: Oracle’s Primavera P6 EPS Setup Guide provides more details on structuring nodes for template management.

Step 2: Create the Initial Template Project

Open Primavera P6 and navigate to the EPS tree. Select your template parent node, right-click, and choose Add Project. Fill in the dialog with a descriptive Project ID (e.g., ENG_TEMPLATE_V2) and a name such as Engineering Project Template – Lumped Duration. Set the start date to a neutral point (e.g., the first Monday of the current year) and the planned finish date as a placeholder—these will be overridden when the template is copied.

In the Defaults tab, pre-populate the project’s default calendar (e.g., a standard 5-day workweek with your organization’s holidays). Also, set default price units (hours vs. dollars) and default duration type (e.g., Fixed Duration & Units). These settings flow to every new project created from the template.

Key Defaults to Configure

  • Resource Assignments: Time units (Hours, Days, Weeks).
  • Cost Conversion: How hours translate to currency (link to the default rate table).
  • AutoCalc: Turn on or off for new activities.
  • Working Days: Calendar name and exceptions (country holidays).

Step 3: Build the Work Breakdown Structure (WBS)

The WBS is the skeleton of your engineering project template. It should mirror the typical project lifecycle. For an engineering template, a recommended WBS might look like this:

  1. Project Management – Kickoff, status reviews, closeout.
  2. Engineering – FEED, detailed design, 3D model reviews.
  3. Procurement – Long-lead items, vendor document review, expediting.
  4. Construction – Site prep, foundations, structural, MEP.
  5. Commissioning & Startup – Pre-commissioning, performance tests, handover.

Assign WBS Categories if your organization tracks different cost types. For each WBS element, set the Default Project Phase and ensure the WBS Weight is defined if you use earned-value management. WBS elements can also carry WBS Codes that mirror your corporate coding system.

Pro Tip: Use WBS Notes

Add a note to each WBS element explaining what activities should fall under it. When a planning engineer copies the template, they see guidance inline, reducing questions and interpretation errors.

Step 4: Define Activities and Their Logic

Add standard activities under each WBS node. For an engineering project template, you typically include:

  • Milestones: “Project Kickoff,” “FEED Freeze,” “IFD Issue,” “Construction Start,” “Mechanical Completion.”
  • Activities with Predecessors/Successors: E.g., “Prepare P&IDs” → “P&ID Review” → “P&ID Approval.”
  • Default Durations: Use typical durations (e.g., 10 days for design reviews) that will be refined later.

Apply Activity Codes like “Phase,” “Discipline,” “Area” to enable filtering and grouping. This is especially powerful in a template because every new project inherits the same code structure, making cross-project rollups easy.

Set Activity Types correctly: Task Dependent (standard), Resource Dependent (if resources drive duration), Level of Effort (e.g., project management), and Start/Finish Milestone. For engineering templates, most design activities should be Task Dependent.

Linking Activities

Create a complete logic network inside the template. Use Finish-to-Start relationships with appropriate lag (e.g., review activities might have 2-day lag after submittal). Avoid excess leads and lags as they make the template less generic. Instead, mark the template as a “skeleton” that planners later adjust for specific project constraints.

Step 5: Assign Resources and Roles

One of the biggest time-savers is pre-assigning resources or roles to activities. Instead of specifying individuals (who may not be available), use Roles—e.g., “Senior Process Engineer,” “Structural Designer,” “Procurement Specialist.” Then assign the role to the activity. Later, when the project is created from the template, the project manager can substitute specific resources for roles using the Resource Assignment page.

If your organization uses Resource Curves, configure default spreading for each role (e.g., designers work 80% in first week, 100% remainder). Curves inherited from the template save hours of manual entry.

For cost-loaded templates, assign Cost Accounts at the WBS or activity level. Use a standard cost account structure like 100.100 – Engineering Labor, 200.100 – Equipment. This ensures cost codes are consistent across all projects.

External reference: Oracle’s Resource Management in Primavera P6 describes role hierarchies and rate tables in detail.

Step 6: Set Calendars and Calendar Exceptions

Your template should include at least three global calendars:

  • Standard 5-Day Workweek: Mon–Fri, 8 hours/day.
  • Engineering Calendar: 5-day week with common holidays (e.g., Dec 25, Jul 4).
  • Construction Calendar: 6-day week or 10-hour days if appropriate.

Assign the most common calendar to the project default, and then assign specific calendars to WBS nodes or individual activities. For example, site activities might use the construction calendar while design activities use the engineering calendar. Templates make calendar assignment fast because you can set WBS-level calendars that propagate to new activities automatically.

Step 7: Save as a Template

When you have finalized the WBS, activities, logic, resources, and calendars, it’s time to save the project as a template. Navigate to File > Save As and choose Save as Template. A dialog appears with options:

  • Include Resource Assignments: Check this to keep your role and resource data.
  • Include Cost Accounts: Keep for cost-loaded templates.
  • Include Activity Codes: Absolutely—these are the key to filtering.
  • Include Baselines: If you want a baseline template, keep this off unless you plan to maintain baselines centrally.

Give the template a clear name and description. Use naming conventions such as ENG_TMPL_FEED_2025 to make searching in the EPS easy. After saving, the original project remains in the EPS—you can delete it or keep it as a master reference.

Step 8: Use the Template to Create New Projects

To seed a new project, right-click on the target EPS node and select Add Project. In the dialog, find the “Copy from Template” option (or “Copy from Project”). Browse to your template .PLF file or the EPS template node location, select it, and click Copy. Primavera P6 will create a full copy as a new project with a new project ID and name you specify.

Alternatively, you can use Project Portfolios to maintain a library of templates. Advanced users can even store templates in a Template Library database using P6’s Administrator module.

Post-Creation Steps

  • Adjust start/finish dates to match the real project timeline.
  • Replace roles with actual resource names (using the Resource Assignment page or Role Substitution feature).
  • Review durations and logic—templates are starting points, not final schedules.
  • Assign unique project codes (location, project manager, client, etc.).

Advanced Template Features

Baseline Templates

You can create a baseline of your template and include it in the template file. When multiple projects copy the same baseline, you have a consistent performance measurement yardstick across the portfolio.

Template Updates and Versioning

Periodically review your template to incorporate lessons learned. If you update the template after it has been used, note that existing projects already created will not automatically update. You can re-apply the template using the Merge Template feature (available as a P6 extension or via SDK), but this requires careful change management.

Using User-Defined Fields (UDFs)

Add UDFs to the template to capture metadata like “Required Sign-Off,” “SOW Reference,” or “Review Status.” These fields appear in every new project, ensuring important attributes are not overlooked.

Common Pitfalls and How to Avoid Them

  • Overfitting: Building a template with too many specific resources or overly tight logic. Keep activities generic; use roles instead of named people.
  • Ignoring Calendars: Templates with a single calendar can cause issues for projects with different work hours. Provide multiple calendar options in the template.
  • Neglecting Code Structures: Without activity or WBS codes, you lose the ability to filter and report. Always include at least three code levels (phase, discipline, area).
  • Forgetting to Update: A stale template becomes a liability. Schedule a biannual review with senior planners to incorporate changes in corporate policy or lessons from completed projects.

Conclusion: Building a Sustainable Template Practice

A well-crafted engineering project template in Primavera P6 is more than a convenience—it is a strategic asset. It enforces standard work breakdown, logic, and resource structures that enable consistent reporting, earned-value management, and portfolio-level analysis. By following the steps outlined—from EPS design to activity logic and role-based resourcing—you can reduce project setup time, improve data quality, and focus your planners on analysis and optimization rather than repetitive data entry.

Start small: build a template for one project type (e.g., small brownfield engineering) and refine it based on feedback. Then expand to other project classes. Remember to document your template in a procedure manual so that all planners understand what the template includes and what they must adjust. With this foundation, your engineering project management office can deliver projects faster and with greater consistency, ultimately driving better predictability and performance.