Loren Data's SAM Daily™

FBO DAILY ISSUE OF JULY 25, 2007 FBO #2067
MODIFICATION

10 -- MNK-BAA-07-0005 - Concept Weapon Simulation Software Development (CWSSD)

Notice Date

7/23/2007
 

Notice Type

Modification
 

NAICS

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

Contracting Office

Department of the Air Force, Air Force Materiel Command, AFRL - Eglin Research Site, 101 West Eglin Blvd Suite 337, Eglin AFB, FL, 32542-6810, UNITED STATES
 

ZIP Code

00000
 

Solicitation Number

MNK-BAA-07-0005
 

Response Due

9/5/2007
 

Archive Date

9/7/2007
 

Point of Contact

Mark Fitzgerald, Contract Specialist, Phone (850)883-2670, Fax (850)882-9599, - Carol Abbott, Contracting Officer, Phone 850-883-2664, Fax 850-882-9599,
 

E-Mail Address

mark.fitzgerald@eglin.af.mil, carol.abbott@eglin.af.mil
 

Description

Attachment/Amendment 1 to MNK-BAA-07-0005 follows: AIR FORCE RESEARCH LABORATORY MUNITIONS DIRECTORATE BROAD AGENCY ANNOUNCEMENT (BAA) MNK-BAA-07-0005 For CONCEPT WEAPON SIMULATION SOFTWARE DEVELOPMENT (CWSSD) A--INTRODUCTION: The Air Force Research Laboratory Munitions Directorate, Lethality and Vulnerability Branch (AFRL/MNAL) is interested in receiving proposals for the Concept Weapon Simulation Software Development (CWSSD) Program under this Broad Agency Announcement (BAA) MNK-BAA-07-0005, with the intent of negotiating one or more contracts for the CWSSD Program. B--REQUIREMENTS: (1) Program Goal & Objective: The goal of this work is to develop/prototype software that will be used to facilitate advancement of weapon concepts/employment. The objective is to design, develop, combine and/or demonstrate engineering, engagement (one-on-one), mission (few-on-few), systems-of-systems, and campaign (many-on-many, military worth) level techniques, tools, and research methods which will enable quick and effective evaluation of advanced weapon concepts. (2) Technical Requirements: Research involves, but is not limited to, intercommunicative weapons, novel destruct mechanisms, non-lethal destruct mechanisms, multiple targeting, and time critical delivery. Accomplishing the program goals/objectives may involve a variety of weapon-related aspects, e.g., sensors, aerodynamics, autopilots, navigation and guidance schemes, propulsion, warheads, fuzes, datalinks, error filters, environment (wind, fog, dust), lethality, vulnerability, and threats. Scenario development and visualization at various levels of weapon interaction are also expected. Interface and utilization of existing tools includes, but is not limited to, ESAMS, RADGUNS, MATLAB Simulink, FLAMES, EADSIM, CFAM, and STORM. The contractor must demonstrate an overall understanding of the concept weapon system software development process, familiarity with software simulation codes listed above and the technical capability to perform the requirements described herein. (3) Program Tasking: (a) Task Order 0001: Task Order 0001 will be to develop software design methods that will define a comprehensive target set along with the specific characteristics associated with a generic target set consisting of terrorists, improvised explosive devices (IEDs) and chemical and biological weapons. The offeror shall research all aspects of the generic target set and develop a breakdown of the different classes and their particular identifying characteristics for use in design and software development of concept weapon characteristics used to engage these targets. As an example, IED may currently be used to define a hidden artillery shell rigged with a detonator. However another form may be a vehicle filled with fertilizer-based explosives rigged to explode and do similar damage. The comprehensive target set should include as many varieties as possible of the generic targets that might exist and their specific characteristics. (b) Subsequent Task Orders: May be issued based on contractor?s strengths demonstrated during performance of Task Order 0001. (4) Management: The contractor shall be responsible for meeting all requirements of this contract, including but not limited to, cost, technical, schedule, security, subcontractor management and technical risk assessment and management. The contractor shall communicate the technical and programmatic status through Data Requirements submissions discussed in Section/paragraph B(5) and scheduled meetings and interchanges discussed in Section/paragraph B(6). (5) Data Requirements: The following data submittals are expected to be required for each contract/task order awarded. Provided below are the Requirement Title, Data Item Description (DID) number and submission frequency. (a) Monthly status reports: DI-MGMT-80368/T. (b) Contract Work Breakdown Structure Cost/Schedule Breakdown Structure: DI-MGMT-8133B/T. Contractor format is acceptable. (Contract/Task Order Award) (c) Performance and Cost Report: DI-FNCL-80912. Contractor format is acceptable. (Monthly, Per Task) (d) Contract Fund Status Report (CFSR): DI-MGMT-81468. Contractor format is acceptable. (Quarterly) (e) Project Planning Chart (Detailed Integrated Master Schedule): DI-MGMT-80507A/T. Contractor format is acceptable. (Per Task Order Award) (f) Program review agenda, charts, minutes (Conference Agenda): DI-ADMN-81249A; Presentation Material: DI-ADMN-81373/T; and Conference Minutes: DI-ADMN-81250A. Contractor format is acceptable. (As Conducted, for Contract/Task Orders) (g) Software (i.e., simulation models) developed or purchased under contract (Computer Software Product End Items): DI-MCCR-80700. (Per Task Order) (h) Final technical report (Scientific and Technical Reports)(Final Report): DI-MISC-80711A/T. The Final Report must document the entire Task Order effort and must include relevant data and results from other technical data that would not otherwise be published. The Final Technical Report must be submitted electronically through secure means in Microsoft Word 2003 or later, compatible format. The Government must be given authorization to read and write to the electronic document. Final Reports may be published in Defense Technical Information Center (DTIC) by the Government. (As Required, Per Task Order) NOTE: The contractor may propose additional elements or submittal of combined elements or DIDs, as appropriate, for the proposed program. (6) Meetings and Reviews: The Government anticipates the following program meetings and reviews: Kickoff within a month of contract start date at contractor?s facilities; Technical Interchange Meetings (TIM) quarterly and/or at times coinciding with key program milestones or decision points to be held at the contractor?s facility, and other meetings that may alternate locations between the contractor?s facilities and Eglin AFB; and a Final Program review at completion of the program at Eglin AFB, FL. In addition to quarterly reviews and formal design reviews, informal program status interchanges (such as weekly teleconferences) are anticipated. The contractor may propose to conduct or participate in other meetings with subcontractors, Government agencies, or third parties, as deemed necessary. (7) Proprietary Items: Contractors are discouraged from using proprietary material in any software developed for this contract. Proposals shall identify any proprietary materials, products, software, or processes to be used by the prime or subcontractor(s) in the performance of this program, and shall provide cost and details for acquisition of data rights or licenses. (8) Security Requirements: Portions of this program may be classified, and it is anticipated a DD Form 254 will apply to the awarded contract. If so, security clearances at the SECRET level will be required. Emissions Security (EMSEC) requirements will apply. Generation of classified material is authorized only on equipment approved for classified processing by Air Force EMSEC authorities. Based upon the proposed technical approach, the Government may provide a Security Classification Guide at contract award or during the performance of the contract, whenever the requirements of the guide, as it pertains to the contract performance, can be determined. (Also see paragraphs B(9) and C(6), below) (9) Special Requirements: International Traffic in Arms Regulations (ITAR) Export Control restrictions shall apply. (10) Subcontracting Plan: Subcontracting plans shall be required in accordance with Federal Acquisition Regulation (FAR) Part 19. C--ADDITIONAL INFORMATION: (1) Number/Type of Contracts: The Government anticipates negotiating one or more Indefinite Delivery, Indefinite Quantity (IDIQ), Cost-Plus-Fixed-Fee type contracts for this effort. Task Orders will be issued along with each contract awarded and during the life of the contract(s) as required. (2) Expected Award Date: Late September 2007 (3) Anticipated Period of Performance: The basic IDIQ contract ordering period will be 5 years. The period of performance for individual Task Orders will vary. (4) Government Estimate: The Government expects to fund a maximum of $9.98M on all contracts for this Research and Development. This figure assumes approximately $1M for each FY07 - FY11, respectively. The ceiling maximum for any one IDIQ contract will be $4.99 million. This funding profile is an estimate only and is not a promise of funding, as all funding is subject to changes/availability and Government discretion. (5) Government Furnished Property (GFP): At least some work performed under these contracts will be performed on-site (e.g., at the Eglin AFB Government facility). Therefore the Government will provide some office space and computer support based on availability and the number of personnel or man-hours required on each task. The Government shall determine the amount of office space and computer support to be provided. (6) Notice to Foreign-Owned Firms: A determination has been made for this solicitation, that all foreign participation as the prime contractor will be prohibited. (7) NAICS: The NAICS code for this action is 541710. (8) Communications/Questions: Address all questions or requests for additional information to both of the business Points of Contact shown in paragraph F(1). D-- PROPOSAL PREPARATION INSTRUCTIONS: (1) Proposal submittals should reference ?MNK-BAA-07-0005 (CWSSD)?, and should be submitted, not later than 2:00 PM Central Time, 5 Sep 07, to AFRL/MNK, attention Mr. Mark Fitzgerald and Mr. Chris Slayton. Offerors should be alert for any amendments to this BAA including due date changes. Proposals should be designed to demonstrate substantive knowledge in all areas of the CWSSD program. All submittals received will be reviewed and evaluated using the Evaluation Criteria found in Section E - Basis for Award. Thus, proposals should address all areas indicated by these factors, demonstrating how the contractor intends to achieve the requirements outlined in Section B-Requirements, and Task 0001. Additionally, the proposals shall include any partners, subcontractors, etc., to be utilized, discuss risk (schedule and cost) assessment, technology maturity level required to meet requirements, and identify the software that will be used in the concept weapon simulation software development. (2) General: All offerors should apply the restrictive notice prescribed in the provision at FAR 52.215-1 (e), Restriction on Disclosure and Use of Data, to trade secrets or privileged commercial and financial information contained in their proposals. Any classified material must be provided in a separate Annex and must be properly marked and handled as such. Only provide classified material to technical points of contact shown in paragraph F(2). (3) Formal Technical Proposal: Volume 1 -Technical Proposal shall include a broad Statement of Work (SOW) suitable for incorporation into the basic IDIQ contract. Additionally, a SOW suitable for incorporation should be provided for Task Order 0001. Volume 1 should fully address the approach in accomplishing the Program objectives/requirements of Section B above and Task Order 0001. The contractor must also provide a summary of relevant past and present capabilities and experience. Relevant experience is defined as performance by the proposed program manager, lead technical investigator and/or chief engineer/scientist supporting weapon characterization software development programs within the last 5 years, and past efforts by other key personnel proposed by the offeror for performance of this contract. State the capacity in which these individuals acted in these relevant programs. The offeror must provide sufficient technical discussion and technical detail to establish the soundness of the proposed approach; provide an adequate basis for assessing program technical cost and schedule risk; and form a sound basis for the cost proposed in Volume 2. Proposals failing to provide adequate technical detail and discussion may be considered technically unresponsive to this BAA. (4) Formal Cost Proposal: The Volume 2 formal cost proposal must provide a cost summary, and must reflect in detail all anticipated costs for a Task Order. This includes but may not be limited to: labor categories expected to be utilized, associated hours required per category, direct labor rates, computer hour rates, materials, travel, other direct costs, and all indirect cost rates/totals (e.g., fringes, overhead, Material Handling, G&A, Cost of Money, etc.). The offeror shall also include estimates for the cost/value of any Government Furnished Property (GFP), and all costs expected to be incurred by the Government associated with providing the equipment, facilities and support necessary to meet the Research and Development requirements. Any costs associated with data or data rights shall be separately identified in the cost proposal. Contractors should expect to certify Cost and Pricing data prior to award of Task Order 0001, and other Task Orders as required by FAR. (5) Page Limits and Preparation Guidance: Formal Technical Proposal shall be limited to a total of 50 pages, which includes charts, figures, tables, etc. Proposed SOWs and resumes may be included as appendices, and will not be counted in the page limitations. The Government reserves the right to remove from consideration any excess pages. Formal Cost Proposal will have no page limitation; however, cost proposals exceeding 30 pages are discouraged. Cost proposal spreadsheets must be submitted in Microsoft Excel format and bear the MNK-BAA-07-0005 marking. A page is defined to be one side of an 8.5 x 11-inch piece of paper with information on it. Print size is 12-point type, in Arial or Times New Roman. Technical Proposals must be in both hard copy and electronic media (CD-ROM or DVD), and must bear the MNK-BAA-07-0005 marking. Proposals submitted on disk are to be submitted in Microsoft Word 2003 or later format and PDF. Note: The Government intends to work proposals and awards through electronic means. To do business with the Air Force Research Laboratory/Munitions Directorate (AFRL/MN), you must have software packages that are compatible with Microsoft Office 2003. Formal Proposals shall be submitted as hardcopy document six paper copies, and one copy of both the Technical and Cost Proposals should be submitted on CD or DVD. E-mail and fax submissions will not be accepted. Formal Proposals must be submitted to AFRL/MNK Contracting Office (unclassified) to the parties shown in Section F ? Points of Contact, paragraph (1). Classified Technical Proposals shall be addressed to parties shown in Section F(2). (Note: Submittal of Proposals constitutes authorization by the contractor for limited reproduction and dissemination within Government agencies and National Laboratories for evaluation purposes only, as stated in FAR 52.215-1(e). (6) Proposal Preparation Costs: The cost of preparing initial Proposals in response to this announcement is not considered an allowable direct charge to any resulting contract, or any other contract. It may, however, be an allowable expense as a normal bid and proposal indirect cost specified in FAR 31.205-18. (7) Data Rights: The Government anticipates unlimited data rights to all data generated under this contract. The contractor is instructed to address data rights assertions, licenses, patents, etc., in Proposals. (8) Contractual Authority: Offerors are advised that only the Contracting Officer is legally authorized to contractually bind or otherwise obligate the Government. The Government reserves the right to award one, multiple, or no contracts, based on the proposals received and the requirements of the Government. (9) Cover Page: Each submittal must have a cover page with the following data: BAA Name and Number; Company Name and Address; Technical Point of Contact (POC); Business/ Contracting POC; e-mail addresses for all POCs; CAGE Code; DUNS Number; Business Size. E?BASIS FOR AWARD: Proposal Evaluation Criteria: Proposals will be evaluated as to their likelihood of success in achieving the section B-Requirements, utilizing the Factors and Sub-factors below. Additionally, a risk assessment will be made of the offers, and selections will be made based on the Best Value to the Government. Factors and Sub-factors are listed in descending order of importance except where stated otherwise. Although Cost is less important than Technical, it is still considered a significant factor. Factor (1) Scientific/Technical Merit ? Sub-factors (a) through (d) of this Factor are of equal importance. (a) Soundness of offeror?s proposed technical approach (b) Extent to which the Proposals demonstrate that the defined requirements can be accomplished with the proposed technology (c) Scope and feasibility of proposed research (d) Scope of technologies to be investigated Factor (2) Capabilities and Experience ? Sub-factors (a) through (c) in this Factor are of equal importance. (a) Personnel/Management: Experience and capabilities of all key personnel (both technical and management); experience and capabilities to manage technical risks, control cost and schedule. (b) Facilities, equipment and techniques necessary to accomplish the project. (c) Subcontract Management: Experience and capabilities to manage subcontractor performance, cost and schedule; nature and extent of reliance on subcontractor. Capabilities and experience may include unique combinations of these sub-factors, which are integral factors for achieving proposal objectives. Experience may be best indicated by work performed on programs of similar scope and complexity within the last 5 years. Any resumes should be in a separate Appendix, which is not included in the Technical Proposal page limits. The government team may request supplemental historical information if required to confirm/verify experience and capabilities. Factor (3) Cost ? Reasonableness and realism of proposed costs. The total cost to be evaluated will include the cost of performing the contract, the cost of testing, and any applicable offsets for GFP or acquisition of data rights. F--POINTS OF CONTACT: (1) Business/Contracting/Cost Info: Address all concerns to both: Mark Fitzgerald, Contract Specialist, (850) 883-2670 at mark.fitzgerald@eglin.af.mil, and Chris Slayton, Contracting Officer, at Christopher.slayton@eglin.af.mil. Address and fax for both: AFRL/MNK, 101 West Eglin Blvd, Suite 337, Eglin AFB FL 32542-6810; and fax (850) 882-9599. (2) Programmatic/Technical Issues and Information: Program Manager, David M. Hogg, phone (850) 883-5210; Fax: (850) 882-2563; e-mail david.hogg@eglin.af.mil or alternate Program Manager, 2LT Chris Hergenreter, phone (850) 882-4576; e-mail christopher.hergenreter@eglin.af.mil. Address: AFRL/MNAL, 101 West Eglin Blvd, Suite 309, Eglin AFB FL 32542-6810.
 

Place of Performance

Address: Vicinity of Eglin AFB and Fort Walton Beach, Florida

Zip Code: 32542

Country: UNITED STATES
 

Record

SN01349475-W 20070725/070723220742 (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 |