PAF4232 - Laserfiche WebLink

New Search

Second, a major consideration is finding a comfortable level of "contractual detail" for both the Corps and the local sponsors - so we can execute acost-sharing agreement (without killing ourselves on a specification process!). And assure we run smoothly as a partnership throughout the feasibility study. Remember, what we' 11 develop together are essentially "specs" between partners with common purpose - so too little, or too much, detail from that perspective is not useful. We'll have to merge the needs of the technical consideration above with the contractual one here. THE SCOPE AS MANAGEABLE PIECES Throughout the Corps, in preparing PMPs, terms such as product, sub-product, major task, work element, activity, task, subtask etc are used to dis-aggregate the scope into manageable pieces. Let's offer the following illustrative definitions for this (somewhat subjective) nomenclature: 1. Product - A product represents the ultimate outcome or deliverable of a process (i.e. the feasibility report -the findings of the entire feasibility phase of the study). 2. Sub product - A significant component of a product, that can be differentiated from the whole and still be considered astand-alone deliverable (i.e. the socio- economic appendix of the feasibility report). i~. 3. Major TaskJWork Element -Represents the broadly defined analyses or ~r undertakings that are required to develop sub-products and products (i.e. economic analysis of the socio-economic appendix). 4. Task/Activity -The specific undertaking required to develop a work element, which can normally be characterized byman-hours. More specific than a work element (above) and represents one of many undertakings that comprise a work element (e.g., estimate flood damages as part of the economic analysis). 5. One may even define sub-task/activities, sub-sub-task/activities, and so on, depending on how far one wants to or can differentiate more and more specific individual activities (i.e. inventory of the floodplain). We could stop at the sub-task level (inventory of the floodplain), which is acceptable, but only if the task is defined. What constitutes an "inventory"? Without stating what data is to be recorded, any set of data could be called an inventory of the floodplain. The sub- tasking above, however it's formatted, should describe something in particular - example: that the inventory is of structures, defined by the location, type, condition, ground and first floor elevations and what frequency flood first inundates each structure. By specifying this, it also tells what it is not - in this example, it is not an inventory of linear feet of roads, sewers, electric and phone lines, number of cars and trucks.