Loren Data's SAM Daily™

FBO DAILY ISSUE OF APRIL 12, 2006 FBO #1598
MODIFICATION

A -- 2006 MEDICAL SCIENCE AND TECHNOLOGY (S&T) CHEMICAL AND BIOLOGICAL DEFENSE TRANSFORMATIONAL MEDICAL TECHNOLOGIES INITIATIVE (TMTI)

Notice Date

12/9/2005
 

Notice Type

Modification
 

NAICS

541710 — Research and Development in the Physical, Engineering, and Life Sciences
 

Contracting Office

Other Defense Agencies, Defense Threat Reduction Agency, Defense Threat Reduction Agency (Headquarters), DTRA Annex 8725 John J. Kingman Road, MSC 6201, Fort Belvoir, VA, 22060-6201
 

ZIP Code

22060-6201
 

Solicitation Number

DTRA01-06-BAA-01
 

Response Due

1/6/2006
 

Point of Contact

Robert Celeste, Contract Specialist, Phone 703-767-3568, Fax null, - Laurie Hull, Contracting Officer, Phone 703-767-3568, Fax null,
 

E-Mail Address

TMTI.BAA@DTRA.MIL, TMTI.BAA@dtra.mil
 

Description

This amendment revises the proposal preparation instructions, general instructions, proposal evaluation and general information as follows: 1) Section VI. PROPOSOSAL PREPARATION, A. 2. Cost Information is revised as follows: “All pricing information shall be rounded to the nearest penny.” 2) Section VI. PROPOSAL PREPARATION, C. Volume I - Technical Proposal, 1. is revised as follows: “1. Page Limitations: The technical volume shall not exceed 40 pages for Integrated Technical/Management Arrangement proposals, and 25 pages for Independent Research and Development Project proposals. A page is defined as 8 ˝ x 11 inches, single-spaced, with one-inch margins, and type not smaller than 12 points. A smaller font is allowed for tables and figures. Each page of the technical volume shall be counted except the following:” 3) Section VII. GENERAL INSTRUCTIONS APPLICABLE TO ALL PROPOSALS, A. Supplemental Proposal and Contract/Agreement Documentation, is revised to add Paragraph 9. Statement of Work as follows: “10. Statement of Work. Provide a SOW approximately 3-5 pages in length that is a separate and distinct document suitable for incorporation into the procurement instrument. Do not put proprietary data or markings in the SOW. Format shall be as follows: 1.0 Objective 2.0 Scope 3.0 Background 4.0 Tasks/Technical Requirements 1st sub-level 4.1 Task 2nd sub-level 4.1.1 Sub-task 3rd sub-level 4.1.1.1 second level sub-task 5.0 Other to include Contract Data Requirement Lists (CDRLs) and other deliverables To assist the Government in the preparation of the contractual SOW, the offeror is required to submit a proposed SOW which accurately describes the work to be performed. The proposed SOW must 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 following is offered as the format for the SOW. (1) 1.0 - Objective: This section is intended to give a brief overview of the specialty area and should describe why it is being pursued, and what you are trying to accomplish. (2) 2.0 - Scope: This section includes a statement of what the SOW covers. This should include the technology area to be investigated, objectives/goals, and major milestones for the effort. (3) 3.0 - Background: The offeror shall identify appropriate documents that are applicable to the effort to be performed. This section includes any information, explanations, or constraints that are necessary in order to understand the requirements. It may include relationship to previous, current and future operations. It may also include techniques previously tried and found ineffective. (4) 4.0 - Tasks/Technical Requirements: (a) This section contains the detailed description of tasks which represent the work to be performed which are contractually binding. Thus, this portion of SOW should be developed in an orderly progression and in enough detail to establish the feasibility of accomplishing the overall program goals. The work effort should be segregated into major tasks and identified in separately numbered paragraphs according to the decimal system above. Each numbered major task should delineate, by subtask, the work to be performed. The SOW must contain every task to be accomplished to include a schedule. (b) The tasks must be definite, realistic, and clearly stated. Use “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. (c) Do not use acronyms or abb NOTE: THIS NOTICE MAY HAVE POSTED ON FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (09-DEC-2005). IT ACTUALLY APPEARED OR REAPPEARED ON THE FEDBIZOPPS SYSTEM ON 10-APR-2006, BUT REAPPEARED IN THE FTP FEED FOR THIS POSTING DATE. PLEASE CONTACT fbo.support@gsa.gov REGARDING THIS ISSUE.
 

Web Link

Link to FedBizOpps document.
(http://www.fbo.gov/spg/ODA/DTRA/DTRA01/DTRA01-06-BAA-01/listing.html)
 

Place of Performance

Address: 8725 John J. Kingman Road, MS 6201, Fort Belvoir, VA

Zip Code: 22060

Country: USA
 

Record

SN01025259-F 20060412/060410221627 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |