List of Abbreviations and Acronyms iii

0. INTRODUCTION 1

0. MRE RA PROGRAM DESCRIPTION 2

0. MRE RA Details 3
1. Objectives 3
2. Task Description Document 4
3. Deliverables 4

4. Financial Reports 4
5. Detailed Plan….…………………………………………………………………………5
6. Integrated Program Team Meetings 5
7. Program Reviews and Reports 5

0. EVALUATION CRITERIA 5
1. Mandatory Requirements 5
2. Evaluation Factors 5

1. Technical Merit 6
2. Past Performance and Experience 6
3. Cost and Cost Realism 6

3. Evaluation Process 6
2. Tentative Evaluation Schedule 6

0. PROPOSAL PREPARATION INSTRUCTIONS 7
1. Proposal Content 7

1. General Instructions 7
2. Proposals 7

1. Technical Proposals 7

1. Past Performance & Experience Proposals 8
2. Cost Proposal 9
3. Page Limitations 11

2. Proposal Submission and Electronic Format 12

1. General Information 12
2. Submission of Electronic Proposals 12

0. SPECIAL CONSIDERATIONS 13
1. Contracts Planned for Award 13
2. Period of Performance 13
3. Government Furnished Information 13
4. Government Furnished Equipment and Facilities 14
5. Contract Type 14
6. Restriction on Disclosure and Use of Data 14
7. Proposal Preparation Cost 14
8. Small Business 14
9. Draft Contract Submission 14

0. PROGRAM PROTECTION AND SYSTEMS SECURITY 14
1. Classified Proposals 14
2. Contract Security Specification 14

0. COMMUNICATIONS WITH THE MRE RA PROGRAM OFFICE 14

Appendix A – Draft Mission Needs Statement A-1

Appendix B - Sample MRE RA Task description document B-1

Appendix C - Sample Contract Data Requirements List C-1

Appendix D - Section 845 Model Agreement D-1

Appendix E - Sample DD-254 E-1

The Program Executive Office for Cruise Missiles and Joint Unmanned Aerial Vehicles (PEO(CU)) is entering the Determination of Mission Needs phase for the next priority UAV system of the Naval UAV Executive Steering Group: Naval MAE. For the purposes of this analysis, the terms MAE (Medium Altitude Endurance) and MRE (Multi-Role Endurance) are interchangeable. This analysis is one of the SECNAV and DoD required elements for a Milestone 0 on a possible acquisition program (Figure 1).

MRE is potentially an organic, sea-based endurance UAV. It will be a flexible asset capable of many different missions (ISR, C4I, SEAD, etc.), and is potentially lethal. Basing mode (CV, LHA, CG/DDG/FFG) is a study variable that should consider and trade-off vehicles, size/weight limits, survivability, littoral operations, deck cycles, logistics/support and force levels for around the clock coverage.

Proposal evaluation criteria (Section 4.0) are provided to inform industry how the proposals will be evaluated. The evaluation criteria reflect the objectives of the MRE RA Program and their relative importance. Proposal preparation instructions (Section 5.0) provide a general outline as to how proposals should be formatted and submitted.

2.0 MRE PROGRAM DESCRIPTION

MRE RA Program is seeking proposals leading to the award of one or more contracts to accomplish the objectives of Section 3.1.

The MRE RA Program goal is to conduct a review of the MRE Draft Mission Needs Statement (MNS) by performing a credible Risk Assessment. The Draft MNS is a compilation of over 20 requirements, decomposed into a single document in Appendix A. Successful analysis will find appropriate, cost-effective naval solutions the requirements. This analysis will lead to documentation for planned approval by the Naval UAV Executive Steering Group (ESG) in early FY02.

A broad IPT with government and each prime contractor represented will form to:

• Agree upon a common set of scenarios and threat definition
• Receive continuing updates as deficiencies are prioritized
• Identify best-value requirements & synthesize final MNS
• Provide input for CONOPS
• IRD Development
• Present findings of RA and the MNS to ESG

All MRE RA prime contractors will work in the IPT to pool non-proprietary data to establish a common matrix of parameters & attributes spanning the entire system of payloads, C4I and aircraft, that will form the backbone of an Interim Requirement Document (IRD). These parameters may be used by all primes in their System Analysis and Risk Assessment (SARA). The focus of the IPT is credible requirement development for the MRE system. Detailed discussions of a proprietary nature will only occur at individual contractor program reviews, at contractor facilities (Figure2).

The IPT will have continuing access to Program Office discussions with resource sponsors, doctrine commands, CINCs and other fleet representatives as they occur. The Program Office is committed to the free and open flow of information, especially as the various customers prioritize requirements. Further, the Program Office intends to involve contractor teams in the development of the CONOPS and ORD, as they mature.

The MRE RA Program is seeking proposals from those offerors who have demonstrated capability as either systems integrators or manufacturers of aircraft or UAV Systems. The Program Office is primarily concerned with a best-value system solution to the Draft MNS requirements. As such, the government is interested in system analysis of all study areas, but will consider proposals that address only selected areas.

As the second element of the RA, offerors will perform a System Design & Definition (SDD) of potential system solutions (developed by the offeror with guidance given by the Program Office). This is intended to determine the basic viability of a UAV solution, the most effective configuration (payloads, C4I, aircraft) and naval basing strategy of the MRE UAV system. This will focus later Navy efforts. Trades identified in the SDD (i.e. survivability/affordability) will lead to IPT recommended tailoring of requirements (i.e. a draft ORD) for ESG approval.

The third element is the System Analysis and Risk Assessment (SARA). Contractors will complete system engineering of their matrix of designs, and perform analysis to define risk areas, assess risk levels, and define risk mitigation strategies.

Contractors should provide three basic deliverable products:

• Final MNS recommendations in Mission Area Analysis (MAA)
• System Design and Definition (SDD) of payloads, C4I, air vehicles, as appropriate
• System Analysis and Risk Assessment (SARA)

This effort will be a concerted government / industry teamed evolution, where the Program Office will provide continuing advice and consent on requirement definition, engineering design insight when requested, and Naval perspective when required.

3.2 Task Description Document

3.4 Financial Reports

The contractor shall provide a monthly Contract Funds Status Report (CFSR), Cost Performance Report (CPR), or similar contractor format accounting throughout the duration of the MRE RA Program.

3.5 Detailed Plan

3.6 Integrated Product Team (IPT) Meetings

Formal IPT meetings will occur at a government site (NAS Patuxent River, MD), four times during the program; Contract Award, as a Final Review, and twice between. The Program Office will work closely with the contractors for scheduling, and coordinate through informal and formal meetings.

3.7 Program Reviews and Reports

Contractor(s) will make recommendations for individual program reviews. Contractor(s) will have wide latitude to determine the format and substance as well as frequency and location of program reviews and reports. Contractor(s) must provide a copy of all presentation materials and reports to the MRE RA Program office using Microsoft applications described in Section 5.2.2.2 by CD-ROM.

0. EVALUATION CRITERIA
1. Mandatory Requirements

The offeror’s MRE RA proposal must meet the following mandatory requirements in order to be considered for award:

It is NOT mandatory to propose a complete study. Offerors may propose to perform only selected study areas (such as payloads only, C4I only) of the MRE RA Program.

2. Evaluation Factors

Proposals shall be evaluated using the following weighted criteria. Technical Merit is substantially more important than the other criteria, each of which is of equal importance to each other.

1. Technical merits of the proposal
2. Past Performance and Experience
3. Cost

The Government reserves the right to award one or more contracts for any efforts, described in this BAA.

1. Technical Merit

The technical merit of the proposal will be judged on, but not limited to:

• definition of study objectives
• approach to analysis, including proposed study areas
• depth of planning
• coherence: logic, consistency and completeness

2. Past Performance and Experience

The offeror will be evaluated on their quality of performance and experience in related contracts, with attention to system engineering, UAVs, advanced military aircraft design, and operational mission analysis.

3. Cost

The offeror will be evaluated on the total proposed cost and the cost realism to execute the proposed work.

3. Evaluation Process

All proposals will be read electronically. Proposals will be evaluated using the criteria in Section 4.0. Offerors will first be evaluated against the mandatory requirements. If the evaluation determines an offeror does not meet the mandatory requirements, no further evaluation of that offeror will be conducted and the offeror will not be considered for award.

4. Tentative Evaluation Schedule

1. PROPOSAL PREPARATION INSTRUCTIONS
1. Proposal Content

The offeror shall provide pertinent information in sufficient detail to supply evaluators with a clear understanding of the offeror’s approach and facilitate evaluation of the proposal against the stated evaluation criteria.

Proposals should clearly and convincingly demonstrate that the offeror has a thorough understanding of MRE RA Program objectives, that the work proposed will clearly contribute to achievement of those objectives, and that the offeror has developed a sound approach to address and mitigate associated risks.

Clarity, brevity, and logical organization should be emphasized during proposal preparation. Elaborate brochures or other presentations beyond those sufficient to produce a complete and effective proposal are neither necessary nor desired.

Proposals shall be offered on a stand-alone basis. Overlap of this proposal with ongoing efforts shall be identified and discussed in the proposal. However, the offeror’s performance on the proposed contract should NOT be contingent on any other contract.

The Government reserves the right NOT to make an award if such award is determined to be contrary to the best interests of the Government. Proposals should be prepared in the English language and cost based on U.S. currency. Engineering data, dimensions and measures must be in English units.

2. Proposals

Technical, Past Performance & Experience and Cost proposals shall be submitted as separate documents, reference the BAA number and be valid for a minimum of 180 days after the published closing date for submission of proposals. Within the page limit constraints described below, organization and structure of proposals is up to the discretion of the offeror.

All proposals shall contain the following information, which will not be included as part of the page limitations specified in Section 5.1.2.3:

• Cover page indicating the offeror’s name, title of proposal and BAA number
• Table of Contents
• List of Tables and Drawings

1. Technical Proposal

The Technical proposal shall address the contractor approach to meeting the requirements described in Section 3.0. The proposal shall describe the offeror’s organizational capability to successfully accomplish the contract resulting from this BAA and shall be specific and complete in every detail. The proposals shall not merely offer to do work according to the requirements of this BAA, but shall outline the actual methods and effort proposed as specifically as possible. Repeating the requirements without sufficient elaboration will not be acceptable. The proposals shall include information regarding planning, scheduling and resources, so that the Government may evaluate management and its ability to execute the MRE RA Program requirements.

1. Executive Summary

The proposal shall contain an Executive Summary that provides a concise abstract of the thrust of the proposal, TDD and basic approach to be utilized. The purpose of the Executive Summary is to provide an overview for the technical reviewers.

2. Contract Data Requirements List (CDRLs)

The offeror’s proposal shall identify the contract deliverables and delivery schedule. Sample CDRLs are given in Appendix D.

3. Detailed Plan (DP)

The offeror shall propose a draft DP for executing the program. The DP expands upon the TDD and shall include sufficient detail to ensure compliance with the program objectives specified in the proposed TDD and the MRE RA Program requirements. The plan shall contain a schedule that details the offeror’s timetable for executing the contract. Each major task identified in the TDD should appear as a separate line on the schedule. The schedule shall identify the significant events and critical path the offeror will achieve.

The offeror shall prepare and submit a cost proposal. If the proposed hours/costs are less than the total proposed effort, the contractor shall describe the difference (IR&D, Contractor funded effort, etc.) and provide detailed traceability. The offeror may utilize their own functional cost categories (for substantiation) and computer-generated format for the application of rates and factors.

Tables shall be provided for each of the following:

• Total Proposed Cost
• Mission Area Assessment
• SDD - Payload Analysis
• SDD - C4I Analysis
• SDD - Air Vehicle Analysis
• System Analysis & Risk Assessment

The proposal(s) shall provide the following information in support of the proposed costs.

• Material Costs - The offeror shall identify the total estimated material costs and provide an explanation of how costs were derived (e.g., vendor quotes, engineering estimates, etc.). For those material cost elements which comprise the top 80% of the total value of material cost, the proposal shall identify the expected source of supply and the basis on which these costs were estimated.
• Labor Estimates - The offeror shall identify its total estimated labor hours needed to perform the contract. Labor hours shall also be broken down by labor category. A brief description of the labor category, how the labor estimate was derived, (e.g., engineering estimates, comparison with similar present or past efforts, the application of factors, etc.) and all assumptions utilized are to be provided.
• Rates - The offeror shall provide, by year, the estimated hourly rates for each proposed labor category, overhead rates, general and administrative rates, FCCOM rates, and any other pricing factors used in developing the proposal. The offeror shall provide an explanation of how the rates were derived (e.g., Forward Pricing Rate Agreement (FPRA), application of industry standards, etc.), and the base to which each rate was applied. When a FPRA is cited, a copy of the agreement is required with the offer. Proposed rates and factors and assumptions shall be forwarded to the cognizant Government Administrative Contracting Officer concurrently with proposal submittal for review and use in the Government's evaluation.
• Subcontracts - The offeror shall identify and fully discuss anticipated subcontracts, including an explanation of the work to be performed, the costs involved, and the basis on which the estimated costs were obtained. For any subcontracts which comprise greater than 20% of the total program cost, excluding prime contractor burdens applied to subcontractor costs, the proposal will provide the same Cost Element Summary as specified above.
• Total Contract Estimated Cost and Fixed Fee By Month - For purposes of determining the initial amount available for payment and allotted to the incrementally funded contract and the period of performance for which the initial increment will cover, proposals shall identify the total proposed contract estimated cost and fixed fee by month.
• Other Costs - The offeror shall include information on any proposed costs not included in the above sections. The offeror shall provide, by category, an explanation of each cost, the estimate, and identification of how the estimate was derived.

2. Page Limitations

Proposals should be as brief as possible, as deemed sufficient by the offeror. The following are guidelines for maximum page counts:

The following information pertains to the page limitations:

• A transmittal letter may be used to forward proposals to the MRE RA Program. It does not impact page count.
• A cover page, table of contents, listing of tables and drawings may be used and will not apply against the page count. Annexes, appendices and other attachments to the proposal apply to the page limitation unless specifically omitted from the page count by this BAA Information Package. CDRLs are omitted from the page limit.
• Font shall be Times New Roman, 12-point, and the text shall be double-spaced. Pages shall be 8.5"x11" with 1" margins on all sides, page set up 100%.
• For purposes of assessing compliance with the page count, proposals will be viewed using the print preview function.

3. Proposal Submission and Electronic Format

This section outlines specific proposal submission requirements.

1. General Information

Proposals in response to this BAA shall be addressed to:

The offeror shall submit four copies of the proposals on electronic media, as described in paragraph 5.2.2, below.

Proposals received after the cutoff date specified herein shall be treated in accordance with the restrictions of FAR 52.215-10 (Late Submissions, Modifications, And Withdraws Of Proposals) (Feb 1997).

2. Submission of Electronic Proposals

This section is intended to provide information to the contractor on the electronic format and application software to be used for submitting proposals. The MRE RA Program is simply soliciting the cooperation of the interested contractors, and in no way should any information regarding electronic products listed below be construed as a government endorsement of such products.

2. Operating System and Applications

The Government will review the proposals via the Microsoft Windows NT Advanced Server/Windows for WorkGroups network. The offeror shall submit proposals using Microsoft Office 97. These applications include Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Project. The offeror should provide proposals using appropriate files in the above applications. Use of other application software for submission of proposals is discouraged.

3. Electronic Media

Contractors shall submit their proposals on CD-ROM. There is no limit to the number of disks that can be submitted, as long as the page requirements of paragraph 5.1.2.3 of this document are met. THE CONTRACTOR SHALL PROVIDE SEPARATE DISKS FOR COST PROPOSALS.

5. File Naming Conventions

There is no limit to the number of files that may be submitted.

Please note that the files should be named in the sequence that they would normally be read by an evaluator and shall have the following names:

• Executive Summary exsum.### e.g. exsum.doc
• Technical Proposal tech#.### e.g. tech1.doc, tech2.doc, tech3.doc
• Task Description Document tdd#.### e.g. tdd1.doc
• Past Performance ppe#.### e.g. ppe1.doc, ppe2.doc
• Cost Proposal cost#.### e.g. cost1.xls, cost2.xls, cost3.xls, cost4.xls

5. Additional Suggestions

The MRE RA Program would also like to make the following recommendations:

1. Embedded sound or video (e.g., MPEG), or hyperlink files into the proposal documents is acceptable, however:
2. Graphics which are embedded into documents should be kept as simple as possible. Complex graphics require longer periods for the computers used in the evaluation system to draw, and redraw, these figures and scrolling through the document is slowed significantly.

0. SPECIAL CONSIDERATIONS
1. Contracts Planned for Award

The Government plans to award multiple contracts for all study areas (MAA, SDD-P/L, SDD-C4I, SDD-A/V, SARA), but may award contracts for selected study area options based on an assessment of the proposal’s contribution to the MRE RA Program Objectives.

The MRE RA Program Office expects to use the contract provided in Appendix D.

6.2 Period of Performance

Total length of the anticipated period of performance for the MRE RA Program is from contract award until 01FEB01.

6.3 Government Furnished Information

At contract award, the Program Office will provide:

1. MRE Draft Mission Needs Statement, Rev 1
2. 2010 Naval Force Structure (long range plans)
3. 2010 Threat database (classified SECRET)

During the course of the contract period, the Program Office will provide updates of requirement prioritization from fleet users, via IPT meetings.

6.4 Government Furnished Equipment and Facilities

There will be no Government Furnished Equipment or Facilities.

6.5 Contract Type

Offerors are required to provide a revised draft of the Model Agreement with their proposal. It will not be used for proposal evaluation. The Government intends to award without discussion.

0. PROGRAM PROTECTION AND SYSTEMS SECURITY
1. Classified Proposals

Proposals will be UNCLASSIFIED. An offeror that desires to submit proposals containing classified defense information should contact Mr. Michael McLoughlin at (301) 757-5898.

2. Contract Security Specification

It is anticipated that some work performed under the contracts awarded in response to this BAA will be classified. If appropriate, the offeror should provide a proposed Contract Security Specification (DD Form 254) tailored to its specific proposal based on its expectations of the level and type of material to be delivered or required during the course of the contract. See Appendix E sample DD-254.

0. COMMUNICATIONS WITH THE MRE RA PROGRAM OFFICE

This section contains information to facilitate communications between industry and the MRE RA Program office. Provided below is the point of contact within the MRE RA Program office for questions pertinent to this solicitation.

It is requested that all comments and questions be submitted to Mr. McLoughlin at above address.