Understanding Fragnets in Construction Scheduling
A fragnet—short for fragment network—is a discrete group of activities added to a construction schedule to represent a change, delay event, or scope modification. Fragnets enable schedule analysts to model events and measure their impact on project completion. Mastering fragnet development is essential for anyone using construction scheduling software for delay analysis or change management.
Fragnets serve two primary purposes: prospective analysis of potential impacts before events occur, and retrospective analysis of impacts after events are complete. Both applications require properly constructed fragnets that accurately represent the event being analyzed. Your construction management software must support fragnet creation and insertion into existing schedules.
Components of a Well-Constructed Fragnet
Effective fragnets include all activities necessary to represent the event being modeled. For a delay event, this might include the delay activity itself, preparatory work needed before resumption, and any recovery activities. For a change, the fragnet includes design time, procurement, and construction activities. Your construction project management software should capture all relevant components.
Each fragnet activity needs appropriate duration, resources, and logic relationships. Durations should be based on reasonable productivity assumptions supported by documentation. Resources should reflect actual requirements. Logic should accurately represent real-world dependencies.
Fragnets also require proper connections to the existing schedule network. These connection points—where fragnet activities link to existing schedule activities—determine how the fragnet affects the overall schedule. Your contractor scheduling software must support precise logic connections.
Creating Fragnets for Delay Events
Delay event fragnets model time lost due to owner actions, differing conditions, third-party impacts, or other causes. The fragnet should capture both the delay period and any consequential effects on the work. Your best construction scheduling software supports delay fragnet creation.
Start by identifying exactly what was delayed and for how long. If equipment delivery was delayed 15 working days, the fragnet should include a 15-day delay activity representing the waiting period. Avoid inflating or deflating the actual delay duration.
Consider ripple effects of the delay. Did the delay affect only one activity, or did it impact a sequence of dependent activities? Did it create resource conflicts requiring re-sequencing? Did weather windows close during the delay, adding additional impact? Your construction scheduling software should capture these secondary effects.
Creating Fragnets for Changes
Change fragnets model the schedule impact of scope modifications. Changes typically include design time, procurement time, and construction time, each represented by appropriate fragnet activities. Your construction management software supports change fragnet development.
Map the change process realistically. Revised drawings require time to produce and review. Changed materials may require procurement. Construction of changed work takes time that may be more or less than original work. Include all phases in the fragnet.
Consider impacts on unchanged work. Sometimes changes affect surrounding activities even though those activities themselves haven't changed. Access restrictions, staging conflicts, or sequence modifications may extend unchanged work. Your construction project management software should capture these indirect impacts.
Insertion Points and Logic Ties
How a fragnet connects to the existing schedule determines its calculated impact. Insertion points should reflect actual relationships between the event and existing activities. Your contractor scheduling software must support various logic relationship types.
Identify which existing activities are truly affected by the event. A delay in electrical rough-in affects drywall (which follows electrical) but may not affect plumbing (which parallels electrical). Connect the fragnet only to activities that were actually impacted.
Choose appropriate relationship types. Most fragnet connections use finish-to-start relationships, but start-to-start or finish-to-finish may be appropriate in some cases. Lag values can represent specific timing requirements. Your best construction scheduling software supports all standard relationship types.
Fragnet Naming and Documentation
Clear naming conventions help identify fragnets within the schedule and support later analysis. Include reference numbers, dates, and brief descriptions in fragnet activity names. Your construction scheduling software should support activity naming that identifies fragnet components.
Document the basis for each fragnet including event description, duration calculations, and logic rationale. This documentation proves essential for credibility in claims and disputes. Your construction management software should integrate fragnet documentation.
Maintain a fragnet log listing all fragnets added to the schedule, their dates, and their impacts. This log supports cumulative analysis and helps track how multiple events contributed to total delay.
Analyzing Fragnet Impact
After inserting a fragnet, recalculate the schedule to determine the impact on project completion. The difference between completion dates before and after fragnet insertion represents the delay impact. Your construction project management software performs these calculations automatically.
If the fragnet activities have float, insertion may not affect project completion. This result indicates that the event consumed available float rather than extending the project. Track float consumption even when completion dates don't change.
Check whether fragnet insertion changed the critical path. Events that shift criticality have different implications than events affecting an already-critical path. Your contractor scheduling software should display critical path before and after fragnet insertion.
Contemporaneous vs. Retrospective Fragnets
Contemporaneous fragnets are inserted at the time events occur, into the schedule version existing at that time. This approach provides the most accurate impact analysis because it uses actual schedule conditions. Your best construction scheduling software supports contemporaneous fragnet insertion.
Retrospective fragnets are created after the fact, often long after project completion. These fragnets must be inserted into historical schedule versions that may not perfectly represent conditions when events occurred. Retrospective analysis is less accurate but sometimes necessary.
Where possible, create fragnets contemporaneously. This practice requires discipline during the project but produces more defensible analysis later. Your construction scheduling software should support ongoing fragnet creation during construction.
Cumulative Fragnet Analysis
Multiple events over a project's life create multiple fragnets whose cumulative effect determines total delay. Analyzing cumulative impact requires inserting fragnets in sequence, each building on the previous state. Your construction management software supports sequential fragnet analysis.
The order of fragnet insertion can affect results when concurrent delays exist. Analyze events in chronological order to most accurately represent how delays accumulated. Your construction project management software should maintain fragnet sequence.
Compare the sum of individual fragnet impacts to total project delay. If these don't match, investigate the difference. Concurrent delays, pacing delays, or analysis errors may explain discrepancies.
Common Fragnet Mistakes
Several common mistakes undermine fragnet credibility. Overly broad logic connections can exaggerate impacts by affecting activities that weren't truly delayed. Inflated durations similarly overstate impacts. Avoid these errors by basing fragnets on documented facts.
Inserting fragnets into the wrong schedule version produces inaccurate results. The critical path at month three differs from month six; using the wrong version misrepresents actual conditions. Your contractor scheduling software must maintain version history.
Failing to document fragnet basis creates credibility problems. Fragnets should be traceable to specific events with supporting documentation. Undocumented fragnets appear manufactured rather than factual.
Fragnets in Dispute Resolution
Well-constructed fragnets form the foundation of schedule delay claims. Courts, arbitrators, and mediators rely on fragnet analysis to understand how specific events affected project completion. Your best construction scheduling software produces the clear, defensible fragnets that support successful claims.
Present fragnet analysis clearly for non-technical audiences. Decision-makers may not be scheduling experts, so explain methodology and results in accessible terms. Graphical representations help communicate schedule impacts.
Prepare for challenges to your fragnets. Opposing parties will question assumptions, durations, and logic connections. Thorough documentation and reasonable assumptions withstand scrutiny.
Best Practices for Fragnet Development
Create fragnets contemporaneously whenever possible. Real-time documentation produces more accurate and defensible analysis than after-the-fact reconstruction. Your construction scheduling software should support ongoing fragnet development.
Base fragnet durations on documented productivity and supported calculations. Avoid round numbers that suggest estimation rather than analysis. Show your work for any duration calculations.
Connect fragnets precisely to affected activities. Broad connections exaggerate impacts; narrow connections may understate them. Analyze actual event effects to determine appropriate connections.
Maintain comprehensive fragnet documentation including event descriptions, duration basis, logic rationale, and impact calculations. This documentation supports analysis credibility and enables meaningful review by others.
Fragnet analysis is a powerful tool for understanding and demonstrating schedule delay impacts. When developed properly using capable construction management software, fragnets provide the factual foundation for fair resolution of schedule disputes.