Using Fragnets in Primavera P6

Using Fragnets in Primavera P6

Fragnets save time by reducing data re-entry but using them unlocks other strategic advantages.

If you are building a schedule for multiple pumps that all share the same logic sequence, such as testing and commissioning, typing out that workflow for every single asset is highly inefficient. Instead, it is better to duplicate the logic.

In Primavera P6, you can achieve this by copying and pasting or by importing the sequence from a saved template. This packaged, repeatable scope of work is known by its shorthand…fragnet (short for fragment network).

It refers to a small, self-contained mini-network of activities and relationships. While they are famous for eliminating repetitive data entry, fragnets come with several other helpful advantages.

This article discusses the usefulness of fragnets to reduce data re-entry. It also explores the collateral benefits that naturally follow.

A Fragnet at its Core

It is not a whole project, and it is not a single activity. It is a pre-built sequence you can drop into a larger schedule wherever that same scope of work shows up.

Think of it like a reusable snippet of code. A developer does not rewrite a sorting function from scratch; they reuse a tested block. Similarly, a scheduler building out ten identical valve overhauls across a plant should not manually build that same 15-activity sequence ten times.

Build the logic once, get it right and deploy it across your organization.

Applications

• Turnarounds and shutdowns — inspecting, cleaning and reassembling the same type of equipment (exchangers, vessels, towers) across a plant
• Construction — Executing floor-by-floor sequences in high-rises or identical unit layouts in residential developments.
• Commissioning — Running standardized test-and-turnover sequences for duplicate equipment systems.
• Utility and infrastructure work — Building repeatable linear segments of pipelines, roadways or transmission lines.

Whenever you have well-chosen naming conventions, nomenclature and network logic you want to preserve, fragnets become handy.

Practical Benefits of Fragnets

The following are some of the practical benefits from using fragnets:

1. Consistency

If five different planners are each manually building out the logic for “test and commission a pump,” you’re going to get five slightly different versions. These can include different relationship types, different durations, missing steps here and there, etc. A fragnet standardizes that logic so every instance of that scope follows the same proven sequence.

• Speed

Building a 5,000-activity turnaround schedule from scratch, activity by activity, is brutal. Building it by assembling forty pre-built fragnets for the equipment types you’re working on is dramatically faster. And it’s a lot less error prone.

• Streamlined Template Management

When you find a logic error or a missing step in a fragnet, correcting it in the master template instantly fixes it for all future schedules. This update will not retroactively fix active schedules, which you must still correct manually. It does prevent the mistake from replicating and saves significant troubleshooting time on all upcoming projects.

• Better Estimating and Historical Data

Because fragnets represent proven, repeatable sequences, they’re also a great foundation for duration estimating. If your “exchanger bundle pull and reinstall” fragnet has run on the last five turnarounds, you’ve got real historical data to inform how long it should take this time. Better than just guessing again!

Building and Using Fragnets

Start with a real, proven sequence. Base your sub-network on a proven historical sequence, rather than building it in a vacuum. Use activities and logic verified by past projects. If you are scheduling a new type of work, expect to refine your fragnet after its initial execution.

Keep it self-contained. A good fragnet requires a clear start and end point, with internal logic that functions independently. Avoid embedding external dependencies inside the template. Instead, add those external relationships when you tie the fragnet into the master schedule.

Use consistent activity ID and naming conventions. Use consistent activity ID and naming conventions. Since you may copy this fragnet into a schedule dozens of times, a clear, consistent naming pattern with searchable placeholders, such as equipment numbers, makes it much easier to keep everything organized after duplication.

Build a reusable fragnet library. Never let a proven fragnet live inside only one project. Standardize your logic by keeping a separate “template” project in P6 for planners to copy from. You could also maintain a folder of exported XML files ready for import.

Tie in the external logic carefully. When you paste a fragnet, only its internal logic comes with it. You must manually link it to the rest of the master schedule by defining what must finish before it starts, and what depends on it finishing. Skipping this step is a common mistake that creates dangerous open-ended activities and broken logic chains.

Watch out for over-standardizing. Not every instance of a scope is truly identical. A fragnet is a starting point, not a rigid rule. Sometimes a specific piece of equipment needs an extra step or a different duration. Resist the urge to force every instance to match the template exactly if the real-world scope genuinely differs.

A Word of Caution

Fragnets are a huge time-saver, but they can also spread bad habits at scale if you’re not careful. A flawed fragnet , e.g., bad logic, unrealistic durations and missing steps, gets multiplied every time it’s reused. This means a small mistake in the template can quietly become a big mistake across the whole schedule.

It’s worth periodically reviewing your standard fragnet library the same way you’d review any other piece of standard documentation. Check that it still reflects how the work gets done, not just how it used to.

Summary

Fragnets are one of those tools that separate schedulers who are grinding through every project from scratch from schedulers who have built up a real toolkit over time.

If you are doing similar work repeatedly, whether across floors, equipment, or project phases, investing the time to build clean, well-tested fragnets pays off fast. You get a faster build process, more consistent logic and a schedule that is a lot easier to trust. Particularly when someone starts asking hard questions about how it was put together!