Attachment 1 Submittal Instructions.docx

ATTACHMENT 1: SUBMITTAL INSTRUCTIONS

STEP 1 WHITE PAPER

The White Paper should include a discussion of the nature and scope of the effort and the offeror’s proposed technical approach. The Government will review the White Papers in accordance with the evaluation criteria set forth in this announcement.

The White Paper shall be limited to 20 pages, prepared and submitted in Word format. Font shall be standard 12-pt business font(s) Arial/Times New Roman/Calibri. Character spacing must be “normal,” not condensed in any manner. Pages shall be single-spaced (standard spacing), pages shall be double-sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom. All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Illustrations, flowcharts, drawings, and diagrams are part of the page count, therefore if adding such items, be mindful of the page limitation. All pages shall be numbered starting with the cover page being page 1 and the last page being page 20.

The Government reserves the right to exclude any information or pages in excess of the limit above. The Government may determine a White Paper does not meet the needs of this CSO due to this exclusion of material beyond the submission limit.

The White Paper will be formatted as follows:

Top of Page 1, include the following:

· CSO Number

· Title of Program

· Name of Company, Business Size

· Company Commercial and Government Entity (CAGE) code

· Dunn & Bradstreet (D&B) Data Universal Numbering System (DUNS) number

· Contracting POC and Technical POC with telephone numbers and email addresses

· If the proposed work to be performed is classified, add the following information: Classified level at which company is cleared, contract address for forwarding classified material (name, address, zip code), cognizant security office (name, address, zip code), and offeror’s security officer’s name and telephone number).

Also include:

· Period of Performance and Task Objectives

· Technical Summary and Proposed Deliverables

· Technical Portion: The technical portion of the White Paper shall include a discussion of the nature and scope of the research and the offeror’s proposed technical approach/solution. It should also include any proposed deliverables. Resumes, descriptions of facilities and equipment. Statement of Work is not required at this point.

· Anticipated schedule: A rough schedule of milestones and final “scaling ready” solution should be included for the Government to understand the proposed timelines of the White Paper if awarded.

· Anticipated Price (Rough Order of magnitude (ROM) Detailed price information is not required but provide a time-phased bottom line figure.

STEP 2 PROPOSAL

Technical Proposal

The Technical Proposal portion of the submission shall not exceed 8 pages, excluding cover page and table of contents. Any pages submitted in excess of the 8-page limit will not be considered or evaluated.

Suggested page limitations for individual sections are listed below; however, these are guidelines and not strict limitations.

I. ABSTRACT. 1 page executive summary and overview.

II. SCOPE. This proposal is submitted in response to the (Insert Program/Acquisition Name) Commercial Solutions Opening (CSO) on….. [Cite the Project Title. Include recommended or not to exceed page count.

a. Objective. [A clear and concise description of the objective of the proposed project.]

b. Background. [Provide the necessary technical and scientific background to support the scientific and technical merits of the proposed project.]

c. Programmatic. This effort will support the DAF Enterprise IT initiative [topic number] aimed at developing [capability area or topic title] technologies or methodologies. [Describe the Offeror’s management plan for the proposed project; list supporting and collaborating organizations and subcontractors; clearly identify roles and responsibilities of each organization and subcontractor supporting the project].

d. Relevance. [Describe the relevance of the proposed project in terms of DAF IT mission, end-user needs and the technology maturity of the proposed project.]

III. CREDENTIALS. [Describe the Offeror’s qualifications to perform the proposed work. Summarize the relevant credentials of the primary performing center, and supporting academic and industrial partners. Describe specific examples of similar work performed, and equipment and/or facilities available to perform the proposed work. List summary qualifications of the Key Personnel. Focus on information directly relevant to the proposed work. 4 pages suggested.]

e. Summary of Credentials.

f. Summary of Qualifications for Key Personnel.

g. Summary of Facilities to Perform the Proposed Work.

IV. WORK TO BE PERFORMED. [Provide details of the work to be performed by task and subtask. Include not to exceed page count.]

h. General. [Provide an overview.]

i. Detailed Tasks. [Describe the details of all tasks needed to perform the proposed work. Clearly distinguish base period tasks and option tasks as appropriate.]

BASE PERIOD (YEAR 1)

1. Task 1: Task Title 1 [Describe what will be accomplished, how the task will be performed, the resources allocated to the task (personnel, hours, materials, etc.), appropriate metrics to measure progress, and deliverables from the task. Describe applicable subtasks. Ensure task description clearly identifies why the task is necessary to accomplish project objectives. Do not include pricing details here.]

2. Task 2: Task Title 2

3. Task N: Task Title N [Define as many tasks as necessary to achieve the stated objective(s).]

OPTION 1 (YEAR 2) (If applicable)[Define as many Option Periods as necessary and only if applicable to achieve the state objective(s). Proposed work shall not exceed X years.]

4. Task N+1: Task Title N+1

5. Task N+2: Task Title N+2

6. Task N+M: Task Title N+M

V. PERFORMANCE SCHEDULE. [Depict the tasks and sub-tasks and the duration of performance of each in a Gantt chart or other suitable chart. Briefly describe the proposed period of performance. Insert not to exceed page count.]

VI. REFERENCES. [List any relevant documents used to develop the technical approach. Insert not to exceed page count.]

PRICE PROPOSAL

The price proposal must include pricing information sufficiently detailed for meaningful evaluation of the proposal. Since the CSO will result in a FAR Part 12 commercial contract, detailed costs will not be required. For pricing purposes, Offerors should assume a contract start date of approximately ten (10) days after submission of the proposal.

Since a FAR Part 12 commercial contract is the anticipated award type, the requirements of the Truth in Negotiations Act (TINA) are not applicable. However, if the contracting officer determines additional information is necessary to support a determination of a fair and reasonable price, other than certified cost and pricing data may be requested.

The responsibility for providing adequate supporting data and attachments lies solely with the offeror. In addition, the offeror must also bear the burden of proof in establishing reasonableness of proposed prices; therefore, it is in the offeror’s best interest to submit a fully supportable and well-prepared price proposal.

The offeror shall prepare the Price Proposal (with the exception of the narrative information described below) using Microsoft Excel format. Include the Topic Number and the Project Title on all pages.

j. Format. Price proposals shall be formatted as follows.

(1) Paper Size – 8.5 X 11-inch paper

(2) Margins 1-inch

(3) Spacing – single

(4) Font – Times New Roman, 12 Point

(5) Electronic Software: Microsoft Word, Excel, or Adobe Acrobat

k. Additional Information: The following information should be contained in a cover sheet attached to the price proposal:

(1) Full company name and address

(2) CSO number submitting proposal against

(3) Point of contact, name, title, and phone and fax number

(4) CAGE code

(5) DUNS number

(6) Will you require the use of any Government property in the performance of this work? If yes, identify.

NOTE: If an offeror takes exceptions to the requirements called out in the announcement, the exceptions should be clearly stated in the price proposal.

CONTRACTOR STATEMENT OF WORK (SOW)

A SOW must be included with the full proposal as part of the submission. The SOW should not exceed 10 pages in length and must be a separate and distinct document suitable for incorporation into the procurement instrument. Do not include proprietary data or markings in the SOW. Pages should be numbered and the initial page should have a date (document date) shown under the title.

The proposed SOW must accurately describe the work to be performed. The proposed SOW must also contain a summary description of the technical methodology as well as the task description, but not in so much detail as to make the SOW inflexible. The SOW template should include the following sections and specifically respond to the Statement of Objectives (SOO) the Government provided with the Request for Proposal (RFP):

1. OBJECTIVE. This section is intended to give a brief overview of the project and should describe why the work is being pursued and what the Offeror intends to accomplish.

2. SCOPE. This section includes a statement of what the SOW covers. This should describe the capability area (CSO topic) to be investigated, goals, and milestones for the effort.

3. BACKGROUND. The Offeror must identify appropriate documents that are applicable to the effort to be performed. This section includes any information, explanations, or constraints that are necessary to understand the project tasks and requirements. This section should describe the effort’s relationship to previous and ongoing efforts.

4. TASKS AND TECHNICAL REQUIREMENTS. This section contains the detailed description of tasks that are necessary to perform the proposed work. These tasks will represent the work to be performed in any potential contract award, and, thus, shall be considered contractually binding. This section should be developed in an orderly progression and presented in sufficient detail to establish the feasibility of accomplishing the overall program goals. This section should clearly distinguish base period tasks from option tasks. The sequence of performance must be presented by fiscal year and task order, as in Section IV of the Technical Proposal. The SOW must contain every task to be accomplished. Note that the Government reserves the right to modify and negotiate the language in the SOW prior to any potential contract award.

4.1 Task descriptions must be definite, realistic, and clearly stated. Use the phrase “the contractor shall” whenever the work statement expresses a provision that is binding. Use “should” or “may” whenever it is necessary to express a declaration of purpose. Use “will” in cases where no Offeror requirement is involved (e.g., power will be supplied by the Government. Use active voice in describing work to be performed.

4.2 Do not use acronyms or abbreviations without first defining them. Place abbreviations and acronyms in parentheses following the first usage of the spelled- out phrase.

4.3 If presentations and meetings are identified in the Offeror’s schedule, the Offeror must include the following statement in the SOW: “Conduct presentations and meetings sat times and places specified in the contract schedule.”

4.4 The desired project structure consists of base period tasks, focused on demonstrating the feasibility of the technology, and option tasks, which cover design, fabrication, testing, and evaluation of the final product. Execution of option tasks will be dependent upon and determined by the contractor’s performance during and the results produced from the base period tasks.