Contract Effort Description Provide a detailed description of the contract or order effort that identifies the key requirements and/or type of effort. This section is of critical importance to future source selection officials. The description should be detailed enough so that it can be used in determining the relevance of this program or project to future source selections. It is important to address the complexity of the contract or order effort, and the overall technical risk associated with accomplishing the effort. Ensure acronyms are identified. Provide a complete description of the contract or order effort that identifies key technologies, components, subsystems, and requirements. For task or delivery order contracts, state the number of orders issued during the period, the number of orders completed during the period, and the number of orders that remain active. A good source for this description can be found in the statement of work, or statement of objectives, requirements document, the acquisition plan, etc. For Interim Evaluations reports, a description of key milestone events that occurred in the review period may be beneficial (e.g., Critical Design Review (CDR), Functional Configuration Audit (FCA)), as well as major contract or order modifications during the period.
For contracts or orders that include multiple functional disciplines or activities, separate them into categories to:
(1) reflect the full scope of the contract or order, and;
(2) allow grouping of similar work efforts within the categories to avoid unnecessary segregation of essentially similar specialties or activities. Each category or area should be separately numbered, titled, and described within the Contract Effort Description to facilitate cross-referencing with the evaluation of the Contractor's performance within each evaluation area.