[Feature] Cost Estimation

[amenity]

As a project or team manager, I want to analyze the costs of individual components of a project so that I can arrive at an estimate for the expected cost of implementation.

In-scope:

• Simple table calculations for components (facilities) that roll up into the larger project or program.

Out-of-scope:

• Tying these estimates to FDUs: it makes more sense to offer the functionality without FDUs at first, but one proposed goal would be to eventually tie these back to FDUs.

Additional notes: Ability to list assets involved in a project facility (i.e. component) and then estimate the cost associated with those assets. Then, user can roll up the cost to a project facility, and therefore a project or program.

[zappfyllc]

@amenity @john Nathan's "Facility Attributes" (i.e. Component Attributes) is a proposed mechanism for drilling into the detail needed for implementation and ultimately estimating costs that get turned into a "task order" (double check on lingo, but I believe that's what Nathan said) that is sent to the contracting office. To cut down on the list of "facility attributes" irrelevant to a given project or project component, Nathan has a separate table that references what facilities get what attributes.

Essentially, in Moped speak, we would have a project component attributes dropdown when editing a project component that serves as a pick-list, and that list is filtered by the component being edited. Related to #3662 but I think it's more vital to the actual cost estimation functionality.

[amenity]

@zappfyllc — interesting. So should component-attribute-tracking be represented in #3662? Is it ~MVP~ 1.0?

[amenity]