Search the Community
Showing results for tags 'OPTIONAL TASKS'.
Found 1 result
SORRY TITLE SHOULD SAY "OPTIONAL TASKS" Due to the Iraq drawdown, the impending Afghanistan drawdown, depletion in funds, and mission changes we are having difficulty projecting the contractual requirement past the base year. Even for the base year, customers are sending me PWSs/procurement packages (for services) with a large percentage of "optional" tasks. For example, the PWS may include funded or known tasks for $4M and optional tasks for $7M. The outyear requirements are completely uncertain. I have found information regarding a "Phased Tasking" model contract Tasks are broken down into 3 categories Initial Tasks Optional Tasks Future Tasks [*]The contract is signed for a Committed amount Total of Initial Tasks (ordered implicitly at contract start) [*]Maximum Contract value which is Total of initial tasks Total of optional tasks Total of future tasks [*]I cannot find any guidance that limits the number of "optional" tasks however, I want to provide the greatest flexibilty to accomodate the unknowns but not have this contract turn into an open-ended "wish list" that would impede future competition. I would appreciate any feedback or suggestions.