Skip to main content

Fragnets in Planera

Fragmented networks (fragnets) are used to show specific events, added scope, or delays. This article explains how fragnet fields behave before and after scheduling.

Updated over 2 weeks ago

Latest Update: 12-22-2025

Summary Video

How Fragnets Work

Before running the schedule, fragnet activities rely only on user-entered Actual Start (AS) and Actual Finish/Expected Finish (AF/EF) dates. After running the schedule, Planera automatically assigns Planned Start/Planned Finish (PS/PF) based on those user inputs.

Before Running the Schedule

  1. Add a new activity and set its status

    • PS/PF fields are hidden because the activity was not part of the baseline plan

    • The fragnet activities will appear in the No Dates section of the Progress Update panel

  2. Enter Actual Start and Actual/Expected Finish dates

    • These dates act as the source of truth until the schedule is run

  3. If dates are not provided after the warning

    • The activity reverts to its previous state (including status)

    • Examples:

      • If status was changed to Complete but AS/AF were missing, status returns to Not Started

      • If status changed from Complete → In Progress, and EF was not entered, status returns to Complete with previously saved dates

After Running the Schedule

  1. PS/PF automatically populate

    • Planned dates inherit from the Actual/Expected dates you entered

  2. Progress Status shows “On Time”

    • Since planned = actual, fragnets always align

  3. AS/AF/EF stay visible and editable

    • These remain your main date fields

Behavior in Tables & MS/FS Merging

  1. Before schedule run

    • Only Actual + Expected dates appear in the Updates table

  2. After schedule run

    • Planned dates appear and match the user-input Actual/Expected dates

  3. Master Schedule (MS) merging

    • FS fragnet dates do not appear in the MS merge panel until FS has been scheduled

    • Prevents incomplete fragnet data from being merged early

Quick Reference

Field

Before Schedule Run

After Schedule Run

PS/PF

Hidden

Auto-populated from AS/EF

AS

Required when status changes

Editable

AF/EF

Required when status changes

Editable

Progress Status

Based on input

Always On Time

Did this answer your question?