3.9.1  Sample Problem/Scenario

Some source selection teams find it useful to use a sample scenario or task to aid in the evaluation of a Mission Capability subfactor.  In some cases a sample task or scenario may be particularly useful, such as where the problem-solving skills are themselves a critical discriminator (for example, contracts for engineering services or critical analysis).  If appropriate, make the sample task the first known delivery order/task order.

Suggestions: Limit sample tasks/scenarios to address only the most critical aspects of the program.  Tasks/scenarios that are too broad or complex may overwhelm the offerors in terms of the time and cost of producing an acceptable solution and thus, not provide the insight that was intended to be provided.  Also, keep in mind, your evaluation team will have to read and evaluate each proposed solution.  Sample tasks/scenarios need to be designed with a specific purpose in mind.  They should be focused on obtaining only the information needed to satisfy the intended purpose.  They must not be based on known or contemplated requirements, unless the sample task will become the first order under the contract. (For instance, if your requirement is for scientific or engineering services to solve specific problems then do not ask the offerors to solve those problems in their proposals.  This would be seen as attempting to get the offerors to solve your problems at their expense rather than contracting for their services.)  Be certain to limit redundancy between the sample task/scenario and other Mission Capability subfactors. If sample tasks/scenarios will be viewed as test questions, offerors should be advised that they will not be given the opportunity to improve on their answers during discussions.

Note:  If you include a sample task/scenario, you must discuss in Section M how it will be evaluated and contribute to the rating of the applicable Mission Capability subfactor.