Skip to Main Content
ProPricer BOE Pro Ideas
Status Planned
Created by Guest
Created on Oct 24, 2024

FEE and POP by PBS

Feature Request: FEE and POP Inheritance at PBS Level

Summary:
Enable users to define FEE overrides and Period of Performance (POP) at the PBS (e.g., CLIN) level so that all underlying tasks automatically inherit the specified FEE% and/or are constrained by the PBS-level POP. This reduces repetitive data entry and ensures consistent application of financial and schedule controls across related tasks.

Problem Statement:
Currently, users must manually update the FEE% and POP for each individual task under a PBS/CLIN. This is time-consuming and prone to inconsistency, especially on large contracts with many tasks. The lack of a PBS-level control increases the risk of misaligned FEE settings or tasks scheduled outside the intended POP, leading to compliance issues, rework, and difficulty maintaining accurate, auditable contract data.

Proposed Solution:
Allow users to assign a FEE override and/or POP at the PBS (CLIN) level, with all child tasks automatically inheriting these values.
Support configuring either FEE only, POP only, or both at the PBS level.
When a PBS-level FEE or POP is updated, propagate the changes to all associated tasks that have not explicitly opted out of inheritance.
Enforce POP constraints so that task dates cannot extend beyond the PBS-level POP unless explicitly overridden with appropriate permissions.
Provide clear indicators at the task level showing whether FEE and POP are inherited from the PBS or have been manually overridden.

Benefits:
Reduces manual effort and data entry by allowing centralized control of FEE and POP at the PBS/CLIN level.
Improves consistency and accuracy of FEE% and POP across all related tasks.
Decreases the likelihood of schedule or financial discrepancies and associated compliance risks.
Simplifies ongoing contract maintenance, especially for large PBS structures with many child tasks.
Enhances user confidence and efficiency by aligning system behavior with how CLIN-level controls are typically managed in practice.

  • Attach files
  • Guest
    Jun 23, 2025

    It is on our CLIN Table and if the estimator/pricer wants this field to be sent to CE, they will have the option to do so as a summary field. The user does not select anything other than CLIN and the fee and contract type are tied to it and sent to CE appropriately.

  • Guest
    Jun 19, 2025

    Would like to see if we can add contract type to this request.