Content Requirement Sample Clauses

Content Requirement. The Government will assess the offeror’s ability to successfully conduct foreign-language training in response to DoD requirements. All information shall be confined to the appropriate file. The offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. The proposal should not simply rephrase or restate the Government's requirements, but rather shall provide rationale and supporting services to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their capabilities, past performance, and facilities. The government will base its evaluation on the information presented in the offeror's proposal – the proposal must stand on its own. Statements that the offeror understands; statements that it can, or will comply with the Performance Work Statement (PWS) (including referenced publications, technical data, etc.); statements paraphrasing the PWS or parts thereof (including applicable publications, technical data, etc.); and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered unacceptable. Elaborate brochures or documentation, detailed artwork, or other embellishments are not necessary nor desired. Page Limit does not include training materials list, instructor resumes, instructor-training materials, or required syllabi and lesson plans. Page Limit does not include covers for volumes, tables of contents, glossary of abbreviations and acronyms, indices, title pages, cross reference indices, and section dividers/tables if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. Each file of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. The following shall be included in the Narrative discussion:

Content Requirement. All information shall be confined to the appropriate file. The Offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. The Government will use information provided under each Volume strictly to evaluate the applicable Factor/sub-factor and may not use that information to evaluate any other Factor/sub-Factor in other Volumes. Within the Technical Factor Volume, Sections for each sub-factor within the Technical Volume shall be clearly identified. The following information shall be included in the Narrative discussion:

Content Requirement. The PRE shall be required to include in writing to the extent information is reasonably available at the time of such filing: (1) A description of the issue; (2) The potential impact on cost and time or other breach of contract; and (3) An indication of the relief sought.

Content Requirement. Confine all information to the appropriate file. If information is not located in the appropriate file, that information may not be evaluated and may be considered omitted. The Offeror should limit information to essential matters, sufficient to define the proposal in a clear and concise manner, to permit a complete and accurate evaluation of each proposal.

Content Requirement. Offeror’s shall submit all information that the Offeror wishes to have considered with the initial proposal. The Offeror shall present the information in the proposal in a clear, coherent, and concise manner sufficient to demonstrate a clear understanding of contract requirements and method of accomplishing these requirements. Offeror’s proposals with vague or terse statements such as “will comply,” “noted,” and “understood,” etc. are not acceptable. All information shall be confined to the appropriate file. The Offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked.

Content Requirement. The written Claim shall include: (1) A description of the issues in dispute; (2) The basis for the Claim, including documentation and analysis required by the contract and applicable law and rules that allow for the proper determination of the Claim; (3) A detailed cost estimate for any amount sought, including copies of any related invoices; and (4) A specific identification of the relief sought.

Content Requirement. 7.8.5 Extension of Time to Submit Documentation.

Content Requirement. All information shall be confined to the appropriate volume. There will be separate Evaluation Teams for each Volume. The offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Each volume of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the volume. Proprietary information shall be clearly marked. Note: Proposal information shall be presented in each Volume to which it relates. ▇▇▇▇▇▇▇’s will not be credited for information placed in the wrong Volume or failing to include information in each Volume to which such information relates.

Content Requirement. The Contractor offering or planning to offer a User Service shall provide the NUE with a certification (“Officer Content Certification”) of a Contractor or Contractor Affiliate Vice- President expressly providing that based on his or her knowledge, the content of User Data obtained for and used in connection with the User Service complies with the Content Requirement of the Provisioning Requirement. In addition, upon the request by the NUE in the exercise of the sole discretion and professional judgment of the NUE, the Contractor offering or planning to offer a User Service shall provide to the NUE the following data and information in addition to the Officer User Certifications: • Sampling of TN records in Contractor’s SOA/LSMS systems for provisioning its User Services to confirm that the data obtained from the NPAC/SMS is no different from what SOW: þ No o Yes is available to other Users (e.g., in either NPAC/SMS broadcasts or Bulk Data Downloads). • Help Desk tickets for requests by Contractor as User (e.g., for Bulk Data Downloads) to confirm handling is consistent with what is required to be provided to any User making a similar request. Notwithstanding anything herein to the contrary, it shall not be a violation of the Content Requirement that Contractor’s SOA/LSMS systems for provisioning its User Services contains data different from what is contained in the NPAC, such as when User Data is corrected, correlated or otherwise modified, provided that the User Data obtained from the NPAC/SMS is no different from what is available to other Users.