BAA_RVKV-2013-0005_FINAL.pdf

‐ i ‐

BROAD AGENCY ANNOUNCEMENT

BAA-RVKV-2013-0005

AIR FORCE RESEARCH LABORATORY

SPACE VEHICLES DIRECTORATE

ANNOUNCEMENT OVERVIEW

NAICS CODE: 541712

FEDERAL AGENCY NAME: Air Force Research Laboratory, Space Vehicles Directorate

BROAD AGENCY ANNOUNCEMENT TITLE: L-Band Radio Frequency (RF) Power Amplifier for the GPS Spacecraft Navigation Payload

BROAD AGENCY ANNOUNCEMENT TYPE: Initial Announcement

CATALOG OF FEDERAL DOMESTIC ASSISTANCE (CFDA) NUMBER(S): Not applicable; as the use of a grant/cooperative agreement is not appropriate.

PROPOSAL DUE DATE AND TIME: Proposals are due by 3:00 PM, Mountain Daylight Time (MDT) on 06 Sep 2013 delivered to AFRL Det 8/RVKVE, Attn: Anne Green 3550 Aberdeen Ave SE, Bldg. 424, Kirtland AFB NM 87117-5776. Proposals received after this due date and time shall be governed by the provisions of Federal Acquisition Regulations (FAR) 52.215-1(c)(3). It should be noted that this installation observes strict security procedures to enter the facility.

These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered “late”. As such, hand-delivery of proposals is strongly discouraged.

Note: If offerors use commercial carriers in for delivery of proposals, carriers may not honor time-of-day delivery guarantees on military installations. Early proposal submission is encouraged.

BRIEF PROGRAM SUMMARY:

This is a Broad Agency Announcement (BAA) describing the research area of interest of an L- Band RF Power Amplifier for the GPS Spacecraft Navigation Payload. Multiple awards of a contract are anticipated with a period of performance of 36 months (33-month technical period of performance, plus an addition 3 months for the delivery of a final S&T report). The full Announcement can be accessed at the following website www.fbo.gov.

ESTIMATED PROGRAM COST: Anticipated funding for the program (not per contract or award): FY 13 $0.2M, FY 14 $3.5M, FY 15 $3.8M and FY16 $2.3M, total $9.8M. This funding profile is an estimate only and not a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that, due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

GENERAL INFORMATION: This acquisition is unrestricted. Small businesses are encouraged to propose on all or any part of this Announcement. The NAICS Code for this acquisition is 541712 (for Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology), and the small business size standard is 1000 employees for Space Vehicles and Guided Missiles, their propulsion units, propulsion unit parts, and auxiliary equipment and parts. This BAA is issued under the provisions of FAR 6.102(d)(2) that provides for the

‐ ii ‐ competitive selection of research proposals. Proposals submitted in response to this BAA that are selected for award are considered to be the results of full and open competition and in full compliance with the provisions of Public Law 98-369, the Competition in Contracting Act of 1984. There will be no other announcement issued for this requirement. Offerors should be alert for any BAA amendments that may permit extensions to the proposal submission date or make other changes to the announcement.

TYPE OF CONTRACTS/INSTRUMENTS: The Air Force reserves the right to award the instrument best suited to the nature of research proposed. Accordingly, the Government may award any appropriate contract type under the Federal Acquisition Regulation. It is anticipated that awards under this BAA will generally be Cost-Plus-Fixed-Fee (CPFF), completion form contracts. NOTE: Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.)

SYSTEM FOR AWARD MANAGEMENT (www.sam.gov) is the official U.S. government system that consolidates the capabilities of CCR/FedReg, ORCA and EPLS.

Central Contractor Registration (CCR): Unless exempted by 2 CFR 25.110 all offerors must (1) Be registered in the Central Contractor Registration (CCR) prior to submitting an application (for an assistance award) or proposal; (2) Maintain an active CCR registration with current information at all times during which it has an active Federal award or an application or proposal under consideration by an agency; and (3) Provide its DUNS number in each application or proposal it submits to the agency.

On-Line Representations And Certifications (OCRA): Potential offerors are notified to be eligible for an award, they must submit annual Electronic Representations and Certifications, otherwise known as ORCA via the System for Award Management (www.sam.gov). These FAR and DFARS level representations and certifications are required in addition to the representations and certifications specific to this acquisition.

ANTICIPATED NUMBER OF AWARDS: The Air Force anticipates awarding two (2) or more contracts. The Government reserves the right to select all, part, or none of the proposal(s) received in response to this announcement, subject to the availability of funds. However, the Air Force reserves the right to make a single award or no awards pursuant to this BAA.

AGENCY CONTACTS:

Technical Points of Contact:

Primary Program Manager: Michael Brasher, AFRL/RVEP, Kirtland AFB, NM, Phone 505-846-4564, Email michael.brasher@kirtland.af.mil

Alternate Program Manager: Lt Holly Bradley, AFRL/RVSE, Kirtland AFB, NM, Phone 505-846-1450, Email holly.bradley@kirtland.af.mil

Contracting Point of Contact:

Contract Specialist: Anne Green, AFRL Det 8/RVKVE, Kirtland AFB, NM, Phone 505- 846-5575, Fax 505-846-5576, Email: anne.green@kirtland.af.mil

Contracting Officer: Rita Varley, AFRL Det 8/RVKVE, Kirtland AFB, NM, Phone 505-846- 4398, Fax 505-846-5576, Email rita.varley@kirtland.af.mil

BROAD AGENCY ANNOUNCEMENT

BAA-RVKV-2013-0005

AIR FORCE RESEARCH LABORATORY/SPACE VEHICLES DIRECTORATE

FULL TEXT ANNOUNCEMENT

NAICS CODE: 541712

FEDERAL AGENCY NAME: Air Force Research Laboratory, Space Vehicles Directorate

BROAD AGENCY ANNOUNCEMENT TITLE: L-Band Radio Frequency (RF) Power Amplifier for the GPS Spacecraft Navigation Payload

BROAD AGENCY ANNOUNCEMENT TYPE: Initial Announcement

CATALOG OF FEDERAL DOMESTIC ASSISTANCE (CFDA) NUMBER(S): Not applicable; as the use of a grant/cooperative agreement is not appropriate.

PROPOSAL DUE DATE AND TIME: Proposals are due by 3:00 p.m., Mountain Daylight Time (MDT) 06 Sep 2013 delivered to AFRL Det 8/RVKVE, Attn: Anne Green 3550 Aberdeen Ave SE, Bldg. 424, Kirtland AFB NM 87117-5776. Proposals received after this due date and time shall be governed by the provisions of Federal Acquisition Regulations (FAR) 52.215-1(c)(3). It should be noted that this installation observes strict security procedures to enter the facility.

These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered “late”. As such, hand-delivery of proposals is strongly discouraged.

NOTE: If offerors use commercial carriers for delivery of proposals, carriers may not honor time-of-day delivery guarantees on military installations. Early proposal submission is encouraged.

I. PROGRAM DESCRIPTION

The Air Force Research Laboratory, Space Vehicles Directorate is soliciting technical and cost proposals on the following research effort:

A. Statement of Objective/Needs: To advance the state-of-the-art and increase scientific knowledge of L-band Radio Frequency power amplifiers for the GPS spacecraft navigation payload. In particular, RF power amplifiers for transmission at the L1 (1575.42 MHz), L2 (1227.60 MHz) and L5 (1176.45 MHz) frequencies are of primary interest.

The primary technical objective of this program is to apply innovative techniques and approaches for the development activities required to design, fabricate, integrate, test and deliver an advanced technology, high power, high efficiency and reliable L-band RF power amplifier (TRL 5+ -- space qualifiable) that is compatible with GPS L-band navigation signal transmission. This power amplifier must be thermally and radiation tolerant (compatible with the GPS orbit environment). This amplifier may be based on either advanced semiconductor materials or alternative technologies that would be applicable to both the existing GPS program of record spacecraft navigation payload and any future enhancements to the constellation. An amplifier based on the results of such a development program would be capable of replacing the Gallium Arsenide (GaAs) Solid State Power Amplifiers (SSPAs) currently used for the L-band transmitters. Note that “capable of replacing” should not be interpreted to mean an exact duplication of the form, fit and function of the existing GaAs SSPAs. The signal output should meet or exceed the current GPS “Gold Standard.” The reliability and long-term operation of this technology under GPS operating conditions should be characterized and optimized for space applications. The implications and design features needed to survive in the GPS medium earth orbit (MEO) environment should be considered.

1. Program Design Criteria and Assumptions:

For the purposes of this BAA, the basic architecture of an L-band RF power amplifier includes the actual radio frequency amplifier, power supply/conditioner, and monitoring and control. The focus of the effort will be the radio frequency section as shown in Figure 1. The term power amplifier (PA) will be used to refer to this module only.

The input to the amplifier is the low power radio frequency signal at one of the navigation frequencies (L1, L2 or L5) modulated with the corresponding navigation signals. The intent of this program is to perform the research and development activities necessary to identify and validate an amplifier design/architecture suitable for application in all these frequency ranges and for all current and projected GPS navigation signals and modulations.

Preliminary research by the Government suggests that the system design criteria listed in Table 1 should be considered as a starting point for the development of the L-band RF power amplifier. These criteria are notional. Preliminary system requirements will be established during the initial design phase of this effort and then updated as necessary during the development cycle to meet any changes in performance, cost, and schedule requirements. For the purposes of this BAA, available spacecraft bus voltages to the navigation payload should be considered in the range from 28 VDC to 100 VDC.

Table 1: Advanced Technology Power Amplifier (RF Section Only) Parameter Threshold Objective

Frequency of Operation L1, L2 or L5 L1, L2 or L5

Input RF Power 5dBm 5dBm

Output RF Power (L1, L2, L5) 250W, 110W, 90W 400W, 150W, 150W Power Added Efficiency 45%, >30% at -5dB backoff 60%, >40% at -5dB backoff

AM/PM Distortion < 10 deg/dB < 2.5 deg/dB

Bandwidth +/- 50 MHz +/- 50 MHz

Gain Flatness +/- 1 dB ± 0.5 dB

Parameter Threshold Objective

Group Delay variation 120 psec 90 psec

Input VSWR 2:1 max 1.6:1 max

Output VSWR 1.75:1 max 1.43:1 max

Stability

Power Amplifier shall not oscillate or be damaged under all transient or steady state conditions

Power Amplifier shall not oscillate or be damaged under all transient or steady state conditions

Life 5 years 15 years Nominal Operating Temperature (baseplate)

10 to 30 deg C 0 to 40 deg C

Random vibration

0.1 g2/Hz from 20-1000Hz, - 6 dB/decade to 2000Hz (16grms)

Same as threshold

*Radiation (total dose) 500 krad 1500 krad Radiation (dose rate) TBD Operate Through Single Event Upset (SEU) TBD Operate Through

*Environmental total dose exposure (unshielded)

B. Program Strategy:

The Advanced Technology L-Band Power Amplifier for GPS program will be separated into phases to better manage technical and programmatic risks. Table 2 lists the planned phases of this program.

Table 2: Planned Program Phases Phase 1 Concept development to the Preliminary Design Review (PDR) milestone

Phase 2

System design development to the Critical Design Review (CDR) milestone;

will include laboratory demonstrations for concept / design validation

Phase 3

Fabrication, integration, test and delivery of the engineering demonstration unit at a TRL 5+ (delivery of residual hardware to AFRL)

C. Definitions:

Frequency of operation: The amplifier design/architecture is intended to be compatible with a specific instantiation of the design/architecture that can support either L1 (1575.42 MHz), L2 (1227.60 MHz) or L5 (1176.45 MHz) center frequency of operation. A design that can operate simultaneously or is switchable to operate at multiple of these frequencies is desirable but not the focus of this effort.

Input RF Power: The nominal modulated input RF signal is a constant envelope signal at the desired carrier frequency, and is modulated with the appropriate navigation signals. This includes several code cases, in which some or all of the navigation signals are present, for example as described in the IS-GPS-200F specification (available at www.gps.gov).

Output RF Power: Power in watts delivered to a 50 ohm load, at the fundamental frequency, and excluding any power at the harmonic frequencies.

Power Added Efficiency: Defined as the ratio of the quantity (output RF power minus the input RF power) to the input DC power. For the present amplifier specifications in Table 1, it will be approximately equal to the drain efficiency, defined as the output RF power divided by the input DC power.

AM/PM Distortion: Defined as the change in output phase as a function a change in input power (phase change in degrees / dB change in input power).

Bandwidth: The 3dB bandwidth of the amplifier.

Gain Flatness: Gain variation in dB measured between two specified frequencies.

In this case, the range of frequencies is fo +/- 15 MHz where fo is the frequency at band center.

Group Delay variation: This is measured for combinations of code modulations and RF output power (nominal and -5dB backoff). The transmitter absolute group delay requirement ensures that it is possible to meet the panel differential group delay requirement.

Input VSWR: Measured at the RF input relative to 50 ohms, at nominal temperature for the frequency band of the center frequency ±15MHz.

Output VSWR: Measured at the RF output connector relative to 50 ohms, at nominal temperature for the frequency band of the center frequency ±15MHz.

Life: This is the projected Mean Time to Failure of the power amplifier when operating at nominal temperatures and peak output power in a representative environment. It is expected that this will be determined primarily by failure and life limiting mechanisms in the amplifier device. The achievement of this goal will be demonstrated by device reliability testing/analysis and design practices that will not introduce other life limiting features into the overall amplifier section.

D. Deliverable Items:

1. Data Items: Exhibit A of the model contract, DD Form 1423, Contract Data Requirement List (CDRL) are representative of the types of data that may be required. Data deliverables are subject to negotiations.

2. Hardware: RF Amplifier

3. Software: As required to operate the Engineering Design Unit (EDU) hardware to include both source code and an executable file(s) to be provided on CD-ROM disk(s).

E. Schedule:

1. Overall effort: 36 months (33 months technical effort + 3 months for preparation and submittal of the scientific and technical report)

2. Data Items: Specified on individual CDRL(s)

3. Hardware: 34 months after award

4. Software: 34 months after award

F. Other Requirements:

1. Program security classification: Secret--see DD Form 254. Offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil. The offeror must possess, or acquire prior to award of a contract, a facility clearance equal to the highest classification stated on the Contract Security

Classification Specification (DD Form 254) attached to this Announcement (AFFARS provision 5352.215-9000).

2. Export Control: Information involved in this research effort will be subject to Export Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710-774). If effort is subject to export control then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

3. Export-Controlled Items: As prescribed by DFARS 225.7901-4, DFARS 252.225- 7048, EXPORT-CONTROLLED ITEMS (JUNE 2013) is contained in this Announcement (as shown below). This clause shall be contained in ALL resulting contracts.

DFARS 252.225‐7048 EXPORT‐CONTROLLED ITEMS (JUNE 2013)

(a) Definition. “Export‐controlled items,” as used in this clause, means items subject to the Export Administration Regulations (EAR) (15 CFR Parts 730‐774) or the International Traffic in Arms Regulations (ITAR) (22 CFR Parts 120‐130). The term includes:

(1) “Defense items,” defined in the Arms Export Control Act, 22 U.S.C. 2778(j)(4)(A), as defense articles, defense services, and related technical data, and further defined in the ITAR, 22 CFR Part 120.

(2) “Items,” defined in the EAR as “commodities”, “software”, and “technology,” terms that are also defined in the EAR, 15 CFR 772.1.

(b) The Contractor shall comply with all applicable laws and regulations regarding export‐controlled items, including, but not limited to, the requirement for contractors to register with the Department of State in accordance with the ITAR. The Contractor shall consult with the Department of State regarding any questions relating to compliance with the ITAR and shall consult with the Department of Commerce regarding any questions relating to compliance with the EAR.

(c) The Contractor's responsibility to comply with all applicable laws and regulations regarding export‐controlled items exists independent of, and is not established or limited by, the information provided by this clause.

(d) Nothing in the terms of this contract adds, changes, supersedes, or waives any of the requirements of applicable Federal laws, Executive orders, and regulations, including but not limited to—

(1) The Export Administration Act of 1979, as amended (50 U.S.C. App. 2401, et seq.);

(2) The Arms Export Control Act (22 U.S.C. 2751, et seq.);

(3) The International Emergency Economic Powers Act (50 U.S.C. 1701, et seq.);

(4) The Export Administration Regulations (15 CFR Parts 730‐774);

(5) The International Traffic in Arms Regulations (22 CFR Parts 120‐130); and

(6) Executive Order 13222, as extended.

(e) The Contractor shall include the substance of this clause, including this paragraph (e), in all subcontracts.

(End of clause)

G. Other Information:

1. Government Furnished Property (GFP): None anticipated to be made available under any resulting contract.

2. Data Rights Desired:

a. Technical Data: Government Purpose Rights

b. Non-Commercial Software (NCS): Government Purpose Rights

The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for our air, space, and cyberspace forces. As such, rights in technical data and NCS developed or delivered under this contract are of significant concern to the government. The Government will therefore carefully consider any restrictions on the use of technical data, NCS, and NCS documentation which could result in transition difficulty or less-than full and open competition for subsequent development of this technology.

In exchange for paying for development of the data, the Government expects technical data, NCS, and NCS documentation developed entirely at Government expense to be delivered with Unlimited Rights.

Technical data, NCS, and NCS documentation developed with mixed funding are expected to be delivered with at least Government Purpose Rights. Offers that propose delivery of technical data, NCS, or NCS documentation subject to Government Purpose Rights should fully explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated, how the incorporation will benefit the program, and address whether those portions or processes are segregable. The Government expects that delivery of technical data, NCS, and NCS documentation subject to Government Purpose Rights will fully meet program needs.

Offers that propose delivery of technical data, NCS, or NCS documentation subject to Limited Rights, Restricted Rights, or Specifically Negotiated License Rights will be considered. Proposals should fully explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a government contract will be incorporated and how the incorporation will benefit the program.

Offerors are reminded that the Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software (the assertions list), required under DFARS 252.227-7013 and DFARS 252.227- 7014, is included in Section K and due at time of proposals. Assertions must be completed with specificity with regard to each item, component, or process listed.

Nonconforming assertions lists will be rejected.Note that DFARS 252.227-7014(d) describes requirements for incorporation of third party computer software (commercial and nonconmmercial). Any commercial software to be incorporated into a deliverable must be clearly identified in the proposal. Because many commercial software licenses are not transferrable or may not be acceptable to the Government, commercial software licenses proposed for delivery to the Government must be approved by the contracting officer prior to award.

As used in this subparagraph, the terms Unlimited Rights, Government Purpose Rights, Specifically Negotiated License Rights, and Limited Rights in technical data are as defined in DFARS 252.227-7013. The terms Unlimited Rights, Government Purpose Rights, Specifically Negotiated License Rights, and Restricted Rights in noncommercial computer software and noncommercial software documentation are as defined in DFARS 252.227-7014. The term Commercial Computer Software is as defined in DFARS 252.227-7014.

II. AWARD INFORMATION

A. Anticipated Funding: Anticipated funding for the program (not per contract or award): FY 13 $0.2M, FY 14 $3.5M, FY 15 $3.8M and FY16 $2.3M, total $9.8M. This funding profile is an estimate only and not a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that due to unanticipated budget fluctuations funding in any or all areas may change with little or no notice.

B. Anticipated Number of Awards: The Air Force anticipates awarding two (2) or more contracts. The Government reserves the right to select all, part, or none of the proposal(s) received in response to this announcement, subject to the availability of funds. However, the Air Force reserves the right to make a single award or no awards pursuant to this BAA.

C. Anticipated Award Date: Dec 2013

III. ELIGIBILITY INFORMATION

A. Eligible Offeror/Applicants: This is an unrestricted Announcement. Small businesses are encouraged to propose on all or any part of this Announcement.

B. Cost Sharing or Matching: Cost sharing is not a requirement.

C. Federally Funded Research and Development Centers (FFRDCs): The following guidance is provided for FFRDCs contemplating submitting a proposal, as either a prime or subcontractor, against this BAA. FAR 35.017-1(c)(4) prohibits an FFRDC from competing with any non-FFRDC concern in response to a Federal agency request for proposal for other than the operation of an FFRDC (with exceptions stated in DFARS 235.017-1(c)(4)). There is no regulation prohibiting an FFRDC from responding to a Announcement. However, the FFRDC’s sponsoring agency must first make a determination that the effort being proposed falls within the purpose, mission, general scope of effort, or special competency of the FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, the non-sponsoring agency must make a determination that the work proposed would not place the FFRDC in direct competition with domestic private industry. Only after these determinations are made would a determination be made concerning the FFRDC’s eligibility to receive an award.

D. Government Agencies: If a Government agency is interested in performing work, contact the Program Office identified in the BAA. If those discussions result in a mutual interest to pursue your agency's participation, the effort will be pursued independent of this announcement.

E. Other:

1. Foreign participation: TBD Notice to Foreign-Owned Firms: Such firms are asked to immediately notify the Contracting POC cited in Section VII before deciding to respond to this announcement. Foreign contractors should be aware that restrictions might apply which could preclude their participation in this acquisition.

2. This acquisition involves data that are subject to export control laws and regulations.

Only contractors who are registered and certified with the Defense Logistics Services Center (DLSC) and have a legitimate business purpose may participate in this Announcement. Contact the Defense Logistics Services Center, 74 Washington

Avenue N., Battle Creek, Michigan 40917-3084 (1-800-352-3572) for further information on the certification process. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your proposal.

3. There are no limits to the number of proposals an offeror may submit.

4. You may be ineligible for award if all requirements of this Announcement and any amendments are not met on the proposal due date as identified above.

IV. PROPOSAL/APPLICATION AND SUBMISSION INFORMATION:

A. Proposal/Application Package:

Proposals submitted shall be in accordance with this announcement. There will be no other solicitation issued in regard to this requirement. The Government intends to evaluate proposals and may award proposals received without negotiation/discussion;

however, the Government reserves to right to negotiate with those offeror(s) whose proposal is selected for funding.

Offerors should be alert for any BAA amendments that may permit extensions to the proposal submission date or make other changes. There is no additional information to be provided.

1. Content and Form of Submission for Proposals: The paragraphs below identify proposal format and content. Elaborate or excessive technical or cost proposals are neither invited nor desired. Proposals should be addressed and delivered as specified in this announcement.

a. General Instructions: Offerors should apply the restrictive notice prescribed in FAR 52.215-1(e) Instructions to Offerors—Competitive Acquisition. Offerors should consider proposal instructions contained in the Broad Agency Announcement (BAA) Guide for Industry, which can be accessed on line at http://www.wpafb.af.mil/shared/media/document/AFD-120614-075.pdf. This guide is specifically designed to assist the offeror in understanding the BAA proposal process. Technical/management and cost volumes should be submitted in separate volumes, and must be valid for 180 days. Any inconsistency in this Announcement and the BAA Industry Guide shall be resolved by giving precedence to this BAA. Proposals must reference the BAA number. Offerors must submit one-original and three (3) hard copies of their proposals, and one electronic copy. A CD-ROM is the acceptable media for submittal; CD-RWs are not acceptable. Offerors are advised that only contracting officers are legally authorized to contractually bind or otherwise commit the Government. The cost of preparing proposals in response to this BAA is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in

FAR 31.205-18.

b. Technical/Management Proposal:

(1) Page Limitation: The Proposal shall be limited to 75 pages, prepared and submitted in Microsoft Word format. Font shall be no smaller than 12 pitch or proportional 10-point font Arial. Character spacing must be “normal,” not condensed in any manner. Pages shall be double-spaced, double-sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on all sides. Lines between text lines must also be 10-point. All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams.

These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items.

Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 75. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc. The proposal page limit does not include blank pages, title pages, tables of content, lists, tabs, coversheets, or the offeror’s proposed Statement of Work (SOW); however, the same formatting rules apply to the SOW, which is limited to 7 pages. A CD-ROM with the Microsoft Word version of your Technical/Management Proposal and the SOW must be submitted with the hard copies of the proposal, and must match the hard copy. Please note: The Government will check the proposal and SOW for conformance to the stated requirements. Any pages in excess of the stated page limitation after the format check will not be considered.

(2) Content: The proposal shall include a discussion of the nature and scope of the research and the technical approach. The technical proposal must convey an understanding of the problems or limitations of the general technology area and the intended application(s). The technical proposal shall include the following items:

(a) Executive Summary: Describe the proposed program, objectives, and approach. A description of the innovation and benefits of the proposed approach and relationship to previous efforts should be discussed. It should summarize the technical issues addressed by the offeror’s proposal without repeating the requirements. This should provide a vision of what will ultimately be achieved and what solution this effort will produce.

(b) Program Description: Describe the techniques, methods, materials, or ideas that will be addressed in this proposal, their innovation, and to what degree they advance the state-of-the-art.

(c) Program Plan: Describe in detail the planned approach and how the plan will be executed. This section should include all technical aspects of the approach. Provide technical detail and analysis necessary to support the technical approach proposed. Clearly identify the core of the intended approach. The “new and creative” solution to the problem(s) should be developed and analyzed in this section. Include a risk assessment of key technical, schedule or cost areas and their potential impact on the program. Identify why proposed subcontractors were selected and what tasks they are to perform.

(d) Contractor’s Statement of Work (C-SOW):

1. A contractor developed C-SOW is required to accurately describe the work to be performed, is enforceable, and void of inconsistencies. If, in the Government’s opinion, the C-SOW does not reflect these requirements, changes or adjustments may be required which could delay or preclude the award. The C-SOW must be a separate and distinct part of the proposal. 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 C-SOW inflexible. DO NOT INCLUDE THE CONTRACTOR’S NAME, OR ANY

PROPRIETARY INFORMATION IN THE SOW.

2. The following is offered as the format for the C-SOW. Begin this section on a new page. Start your C-SOW at Paragraph 1.0.

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.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.0 ‐ Background: The contractor 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.0 ‐ Technical Requirements:

This section contains the detailed description of tasks which represent the work to be performed which are contractually binding. Thus, this portion of the 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.

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 contractor requirement is involved; e.g., power will be supplied by the Government. Use active voice in describing work to be performed.

Do not use acronyms or abbreviations without spelling‐out acronyms and abbreviations at the first use; Place the abbreviation in parenthesis immediately following a spelled‐out phrase. This provides the definition for each subsequent reuse. As an option, a glossary may contain definitions of acronyms and abbreviations.

If presentations/meetings are identified in your schedule, include the following paragraph in your SOW:

“Conduct presentations/meetings at times and places specified in the contract schedule.”

(e) Milestone Chart: A Milestone Chart should indicate when specific objectives are expected to be met in the overall program schedule and should identify the specific accomplishments necessary to proceed to the next task. Provide a schedule of when the deliverable items identified in the BAA are to be delivered.

(f) Facilities and Equipment description: Describe the facilities that can be used to achieve the goals of the program, in terms of manufacturing capability, testing facilities, and/or any relevant specialized equipment.

(g) If Government Furnished Property is requested you are required to submit the following information with your offer—

1. A list or description of all Government property that the offeror or its subcontractors propose to use. The list shall identify the accountable contract under which the property is held and the authorization for its use (from the contracting officer having cognizance of the property);

2. The dates during which the property will be required for use (including the first, last, and all intervening months) and, for any property that will be used concurrently in performing two or more contracts, the amounts of the respective uses in sufficient detail to support prorating the rent;

3. The amount of rent that would otherwise be charged in accordance with FAR 52.245-9, Use and Charges; and

4. The voluntary consensus standard or industry leading practices and standards to be used in the management of Government property, or existing property management plans, methods, practices, or procedures for accounting for property.

(h) Description of Relevant Prior Work: Provide a list of related previous or current government, commercial, or internally funded work during the past five years. For each such effort, provide the principal investigator, title of effort, contract number, brief summary of results, dollar value, and a technical and contracting point of contact, including phone numbers, for the funding organizations.

(i) Management Plan: Offerors should provide an approach that demonstrates the ability to effectively and efficiently manage and administer the research program to a successful conclusion.

(j) Resumes of Key Individuals: Include brief summaries of resumes of relevant key individuals including any consultants or subcontractors that might be proposed.

(3) Any questions concerning the technical/management proposal or C-SOW preparation shall be referred to the Technical POC cited in Section VII.

c. Cost/Business Proposal:

(1) Separate the proposal into a cost section and business section. The business section should contain all business aspects to the proposed contract, such as type of contractual instrument, any exceptions to terms and conditions of the announcement, any information not technically related, etc. Provide rationale for exceptions. Identify any technical data that will be delivered with less than unlimited rights. Adequate price competition is determined not to exist because the absence of precise Government specifications and varying technical approaches proposed for R&D efforts. Cost proposals have no page limitations; however, offerors are requested to keep cost proposals under 100 pages as a goal. The proposal shall be furnished with supporting schedules and shall contain a labor hour breakdown per task. Refer to Det 8 AFRL Cost Proposal Instructions (Attachment C).

(2) Subcontracting plans, for efforts anticipated to exceed $650,000, shall be submitted along with the technical and cost proposals*. Reference FAR 19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) for subcontracting plan requirements. The DOD Small Business program goals can be accessed at http://www.acq.osd.mil/osbp/about/sbProgramGoals.shtml. If a company has a Master Subcontracting Plan, as described in FAR 19.704, a copy of the plan shall be submitted with the proposal. *Small businesses are exempt from this requirement.

(3) Prospective offers are to identify any foreign nationals that are anticipated to be working on the project, both at the contractor and subcontractor level.

Information required includes, but is not limited to, place of origin, current status (copy of documentation required), and provide an explanation of their anticipated level of involvement on the proposed effort.

d. Proposal Content Summary: You may be ineligible for award if all requirements of this Announcement are not met on the proposal due date. Reference Section VIII for a checklist of the requirements.

B. Proposal Submission Dates and Times: Proposals are due by 3:00 PM Mountain Daylight Time (MDT) on or before 06 Sep 2013. Proposals received after the due date and time specified shall be governed by the provisions of FAR 52.215-1(c) (3). It should be noted that this installation observes strict security procedures to enter the facility.

These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered “late”. As such, hand-delivery of proposals is strongly discouraged. Note: If offerors use commercial carriers in for delivery of proposals, carriers may not honor time-of-day delivery guarantees on military installations. Early proposal submission is encouraged.

1. Funding Restrictions: The cost of preparing white papers/proposals in response to this announcement is not considered an allowable direct charge to any resulting contract or any other contract, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18.

2. Other Submission Requirements: Proposals must be submitted to AFRL Det 8/RVKVE, Attn: Anne Green 3550 Aberdeen Ave SE, Kirtland AFB NM 87117-5776

V. PROPOSAL/APPLICATION REVIEW INFORMATION:

A. Evaluation Criteria: The following criteria, which are listed in descending order of importance, will be used to determine the proposal(s) recommended for award. The Government reserves the right to select all, part, or none of the proposals received in response to this announcement, subject to the availability of funds.

Technical Importance to Air Force programs Funds Availability

No further evaluation criteria will be used. Individual proposal evaluations will be performed using these evaluation criteria without regard to other proposals submitted under this BAA. Cost realism and reasonableness shall also be considered to the extent appropriate.

B. Review and Selection Process: The proposals will be evaluated and categorized as follows:

Highly Recommended: Proposals are recommended for acceptance if they demonstrate technical merit, importance to Air Force programs and sufficient funding is available, and normally are displaced only by other Highly Recommended proposals

Selectable: Proposals are recommended for acceptance if they demonstrate technical merit, importance to Air Force programs, sufficient funding is available, but may require further development, but at a lower priority than Highly Recommended proposals. To ensure a diversity of approaches, a Selectable proposal may be prioritized over a Highly Recommended proposal if the Selectable proposal presents a unique approach unlike any of the Highly Recommended proposals.

Not Selectable: Proposal does not demonstrate technical merit, does not meet Air Force needs, or sufficient funding is not available.

VI. AWARD ADMINISTRATION INFORMATION:

A. Award Notices: Offerors will be notified whether their proposal is recommended for award, by letter or e-mail, on or about 22 Nov 2013. The notification is not to be construed to mean the award of a contract is assured, as availability of funds and successful negotiations are prerequisites to any award.

B. Administrative and National Policy Requirements: As included in Model Contract and Section K Representations and Certifications

C. Reporting: Exhibit A of the model contract, DD Form 1423, Contract Data Requirement List (CDRL) is representative of the types of data that may be required.

VII. AGENCY CONTACTS

A. Questions of a technical nature shall be directed to the technical point of contact, as specified below:

Primary Program Manager: Michael Brasher, AFRL/RVEP, Kirtland AFB, NM, Phone 505-846-4564, Email michael.brasher@kirtland.af.mil

Alternate Program Manager: Lt Holly Bradley, AFRL/RVSE, Kirtland AFB, NM, Phone 505-846-1450, Email holly.bradley@kirtland.af.mil

B. Questions of a contractual/business nature shall be directed to the contract specialist/ contracting officer, as specified below:

Contract Specialist: Anne Green, AFRL Det 8/RVKVE, Kirtland AFB, NM, Phone 505- 846-5575, Fax 505-846-5576, Email: anne.green@kirtland.af.mil

Contracting Officer: Rita Varley, AFRL Det 8/RVKVE, Kirtland AFB, NM, Phone 505-846- 4398, Fax 505-846-5576, Email rita.varley@kirtland.af.mil

Any correspondence must reference the BAA title and number.

C. Ombudsman: The Ombudsman clause, AFFARS 5352.201-9101 OMBUDSMAN (NOV 2012) will be contained in any contracts or agreements resulting from this Announcement. The AFRL Ombudsman is Barbara G. Gehrs, Director of Contracting, AFRL/PK, (937) 904-4407, email: Barbara.Gehrs@wpafb.af.mil .

VIII. OTHER INFORMATION

A. Acquisition of Commercial Items: Based upon market research, the Government is not using the policies contained in FAR 12, Acquisition of Commercial Items, in its Announcement for the described supplies or services. However, interested persons may identify to the contracting officer their interest and capability to satisfy the Government’s requirement with a commercial item within 15 days of this notice.

B. Non-Government Advisors: Offerors are advised that data included in the technical and cost/business proposals submitted to the Government in response to this BAA may be released to non- Government advisors for review and analysis. Any non-Government advisor will strictly serve in an advisory capacity only to the Government evaluators.

Non-Government advisors will have appropriate Organizational Conflict of Interest clauses in their contracts with AFRL and will initiate any required Non-Disclosure Agreements. All offerors must clearly indicate in their proposals if they have any objections or concerns regarding the use of non-Government advisors (See Attachment E – Use of Non- Government Advisors).

C. Support Contractors: Only Government employees will evaluate the proposals for selection. Offerors are advised that employees of commercial firms under contract to the Government may be used to administratively process proposals, monitor contract performance, or perform other administrative duties requiring access to other contractors' proprietary information. These support contracts include nondisclosure agreements prohibiting their contractor employees from disclosing any information submitted by other contractors or using such information for any purpose other than that for which it was furnished. Any objection to administrative access must be in writing to the Contracting Officer and shall include a detailed statement of the basis for the objection.

D. Communication: Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. Discussions with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.

E. Debriefings: When requested, a debriefing will be provided. The debriefing process will follow the time guidelines set out in FAR 15.505 and 15.506, but the debriefing content may vary to be consistent with the procedures that govern BAAs (FAR 35.016).

F. Forward Pricing Rate Agreements: Offerors who have forward pricing rate agreements (FPRA’s) and forward pricing rate recommendations (FPRR’s) should submit them with their proposal.

G. Proposal Content Checklist: You may be ineligible for award if all requirements of this Announcement are not met on the proposal due date.

1. Proposals are due to the specified point of contact.

2. Proposals are due no later than the due date and time specified in this announcement.

3. Proposal page limits are strictly enforced. See Section IV of the Announcement for page limits.

4. Completed Section K Certifications and Representations (Attachment B) are due with the proposal.

5. The Cost/Business Proposal must contain all information described in the Content and Form of Proposal Section.

6. For any subcontracts proposed, the Cost/Business Proposal must contain a subcontractor analysis IAW FAR 15.404-3(b).

7. The Cost/Business Proposal must contain any exceptions to the Model Contract Terms and Conditions (Attachment A). However, be advised that the document awarded may include contract line items (CLINs)/clauses/articles in addition to those in the models, and/or some of the CLIN/clauses/articles in the models may be deleted, depending on the specific circumstances of the individual program. Any additions or deletions will be discussed with the offeror prior to award of the document. In the interest of streamlining and in order to be in position to award within days of completion of the technical evaluation, it is imperative that you review the model contract appropriate for your business type and provide with your proposal any exceptions to terms and conditions.

8. Offerors other than small businesses are to include a subcontracting plan in Microsoft Word Readable or Adobe format on a CD-ROM as well as a hard copy.

9. Proposals must be submitted in the format specified in Section IV.

10. Offerors who have Forward Pricing Rate Agreements (FPRA’s) and Forward Pricing Rate Recommendations (FPRR’s) should submit them with their proposal.

11. A DD Form 254 is applicable; offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

IX. ATTACHMENTS

Attachment A – Model Contract (pdf portfolio including the following documents)

– Exhibit A: DD Form 1423, Contract Data Requirements List (CDRL)

– DD Form 254, Contract Security Classification Specification

Attachment B – Section K, Representations and Certifications

Attachment C – Det 8 Air Force Research Laboratory AFRL - RVK Cost Proposal Instructions

Attachment D– Proposal Content Checklist

Attachment E – Use of Non-Government Advisors