Jump to content
The Wifcon Forums and Blogs

Search the Community

Showing results for tags 'OPTIONAL TASKS'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Instructions and Terms of Use
    • Terms Of Use
    • Before You Register, Before You Post
  • Contracting Forum
    • Section 809 Panel
    • Polls
    • For Beginners Only
    • Contracting Workforce
    • Contract Award Process
    • Contract Pricing Including CAS & Allowable Costs
    • Contract Administration
    • Schedules, GWACS, MACs, IDIQs
    • Subcontracts & Subcontract Management
    • Small Business, Socioeconomic Programs
    • Proposed Law & Regulations; Legal Decisions
  • Federal Contracting: A New Beginning
    • The Competition in Contracting Act

Blogs

  • The Wifcon Blog
  • Vern Edwards' Blog
  • Don Mansfield's Blog
  • Bob Antonio's Blog
  • NCMAExecutiveDirector's Blog
  • Professor Ralph Nash's Blog
  • Emptor Cautus' Blog
  • Centre Knowledge Blog
  • Leftbrainpro.com Answer Blog
  • SmallGovCon.com
  • Patterns of Procurement
  • Steve Gess

Product Groups

There are no results to display.

Categories

  • Rules & Tools
  • Legal Opinions
  • News

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. 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.
×