BAA-09-01-PKS-Call50.doc

BAA 09-01-PKS Call 50

1-Step Broad Agency Announcement

Overview Information

NAICS Code: 541712 Federal Agency Name: Air Force Research Laboratory, AFRL/RYAR Sensors Exploitation Branch

Broad Agency Announcement Title: Compact Automatic Target Recognition (ATR) & Sustainable Environment (CASE) Broad Agency Announcement Type: This is the initial announcement.

Broad Agency Announcement Number: STROEB II BAA, 09-01-PKS, Call 50 Catalog of Federal Domestic Assistance (CFDA) Number(s): N/A

Proposal Due Date and Time: 25 Feb 2013 at 3:00PM Eastern Standard Time (EST). NOTE: Proposal receipt after the due date and time 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.” Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, they may not honor time-of-day delivery guarantees on military installations. Early proposal submission is encouraged.

Solicitation Request: Air Force Research Laboratory, AFRL/RYAR Sensors Exploitation Branch, Wright Research Site is soliciting technical and cost proposals on the research effort described below. Proposals should be addressed to the Contracting Point of Contact (POC) stated in Section VII of the Full Text Announcement. This is an unrestricted solicitation. Small businesses are encouraged to propose on all or any part of this solicitation. 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 500 employees. Proposals submitted shall be in accordance with this announcement. There will be no other solicitation issued in regard to this requirement. Offerors should be alert for any BAA amendments that may permit extensions to the proposal submission date.

System for Award Management (SAM) Registration (Deviation): FAR 52.204-99 is included by reference in lieu of FAR 52.204-7, Central Contractor Registration (CCR), and DFARS 252.204-7004, Alternate A, Central Contractor Registration. SAM is the primary Government repository for prospective federal awardee information and the centralized Government system for certain contracting, grants, and other assistance related processes. It replaces CCR/FedReg, On-line Representations and Certifications (ORCA) and the Excluded Parties Lists System (EPLS). Contractors shall be registered in the SAM database prior to submitting an invoice and through final payment of any contract, basic agreement, basic ordering agreement, or blanket purchasing agreement resulting from this solicitation. Contractors may obtain information on registration and annual confirmation requirements via the SAM accessed through https://www.acquisition.gov or by calling 866-606-8220.

Type of Contract/Instrument: 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 FAR or Other Transaction (OT) for Prototype, grant, cooperative agreement, or OT for Research. The Air Force may also consider award of an appropriate technology transfer mechanism if applicable. It is anticipated that awards under this BAA will generally be a Cost Plus Fixed Fee Indefinite Delivery/Indefinite Quantity (ID/IQ) Type contracts. Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.)

Estimated Program Cost: $24,375,000.00 Anticipated Number of Awards: The Air Force anticipates awarding up to three (3) IDIQ basic awards based on this announcement.

Brief Program Summary: Air Force Research Laboratory’s Sensor Directorate, Layered Sensing Exploitation Division’s (AFRL/RYA’s) Combat Identification (CID) program matures, evaluates and demonstrates a wide range of sensor exploitation technologies for advanced capabilities sufficient to be transitioned to the warfighter. The primary objective for CID is to condense sensor data from weapon systems into object ID tags such as “target, friendly, neutral or unknown”. AFRL/RYA accomplishes this goal by exploiting mature sensor technologies to develop long range, high confidence object identification algorithms. Raw data can originate from any sensor type such as active radars or passive cameras. Detection algorithms can be any standard signal processing method such as doppler hits from radar sensors or change detection hits from infrared sensors. Other signal processing algorithms then convert the information to formats suitable for humans, computers, or some combination thereof, to comprehend.

Budget constraints are forcing program managers to factor overall cradle-to-grave lifetime costs of new and legacy sensor object identification weapon systems. Some legacy systems have substantial costs. For example, generating supervised training data sets sometimes requires target measurements in a very controlled environment that are expensive to collect. Then reducing the data is notoriously very labor intensive and expensive. Therefore, some systems, the cost to generate and maintain target databases increases each year and will eventually become unsustainable. Consequently, this Compact ATR and Sustainable Environment (CASE) effort will develop CID technologies which are cost effective yet still robust enough to prevent horrible outcomes such as fratricide.

The final goal of the program deals with proprietary rights. Most platforms currently in DoD inventory are comprised of contractor proprietary sub-systems where the Government is constrained to return to the developmental contractor for all enhancements. This slows or prevents innovation while at the same time driving up yearly operational costs . The CASE program will strive to not repeat these mistakes by investigating the potential for a new open architecture CID environment. The hope is that future government program managers and engineers will have complete flexibility to enable third-party upgrades to any sub-system that uses CASE technologies on any platform resulting in huge savings to taxpayers.

Address technical questions to: Pat Marshall, 2241 Avionics Circle, Wright Patterson AFB, OH 45433, (937) 938-4294, pat.marshall@wpafb.af.mil Address contracting questions to: Jennifer Kleiv, Contract Negotiator, 2310 Eighth St, Bldg 167, Wright Patterson AFB, OH 45433-7801, (937) 656-9828, jennifer.kleiv@wpafb.af.mil or Joel B. Harrah, Contracting Officer, 2310 Eighth St, Bldg 167, Wright Patterson AFB, OH 45433-7801, (937) 255-5306, Joel.Harrah@wpafb.af.mil

Full Text Announcement

1. Program Description: Air Force Research Laboratory, AFRL/RYAR Sensors Exploitation Branch is soliciting technical and cost proposals on the following research effort:

BASIC IDIQ

COMPACT ATR AND SUSTAINABLE ENVIRONMENT (CASE)

STATEMENT OF WORK

I. Objective: Lessons-learned from several decades of prior research will be utilized in this effort to develop the next generation of CID sensor exploitation algorithms and databases. CASE addresses robustness, sustainability, efficiency and low cost concerns associated with the development, operation and maintenance of current and future non-cooperative Automated Target Recognition (ATR) technologies. Research will focus on reducing template/database dimensionality and cost for single and multi-phenomenology ATR, while maintaining target identification performance. Tradeoffs must be evaluated with respect to DoD research investment versus, for example, potential lifetime operational cost savings. This includes time and funds required to create and maintain target, friendly, neutral or unknown CID databases. CASE will develop and demonstrate the ability to add new target representations to ATR databases rapidly, including possibly on-the-fly target insertion.

II. Scope: This Compact ATR and Sustainable Environment (CASE) program will concentrate on addressing efficiency and sustainability issues associated with the development, operation and maintenance of current non-cooperative ATR technology. This effort entails the enhancement, development, demonstration, optimization, and evaluation of existing and emerging CID ATR systems. Research is focused on reducing template/database dimensionality and cost for single and multi-phenomenology ATR, while maintaining target identification performance. Emphasis will be to develop new ATRs that meet mission requirements at a reasonable cost. Mission requirements and operational overhead have to be taking into account at the earliest stages of ATR algorithmic design or legacy modification. Technology developments will be demonstrated in both laboratory and field environments, including real time flight demonstrations. CASE will also explore the migration of compact ATRs to operational use.

The contractor is expected to maintain a disciplined, validated and efficient capability to exercise, analyze and evaluate system-of systems solutions for the CID of targets. The contractor must have past experience in CID ATR technologies to include identification, tracking, registration, fusion, sensor resource management, and other related technologies using Synthetic Aperture Radar (SAR), High Range Resolution radar (HRR), Ground Moving Target Indicator radar (GMTI), Electro-optic/Infrared (EO/IR), Laser Radar (LADAR) and possibly Vibrometry sensors. Basically any sensor system used to facilitate high confidence CID ATR capabilities. Targets include both Civilian and Military vehicles.

During the performance of this contract, a continuous review of new technologies, which may apply to the problem of making CID technologies more robust and efficient with lower costs, will be researched. Once a potential technology has been tested and vetted to the point that a successful demonstration is viable, focus will then switch to addressing and supporting the transfer of technologies to military operations. This will be accomplished by developing integrated ground, air and space system concepts that are optimized to meet the critical needs of the USAF military applications. Although detection and tracking technologies are included, this program emphasizes the identification aspects of various sub-classes of targets including those deemed as potential eminent threats. During situational awareness, asset protection and intelligence object identification parameters may also be extracted and passed to combat commanders. Alternate developmental concepts may be initiated at any time for new object identification tasks highlighted via intelligence channels. This program will also enhance military operations by developing quick-reaction technologies and capabilities for aircraft that carry any sensor payload or weapon system. Quick reaction sensor instrument sensor analysis and hardware development/fielding will also be important aspect of the work conducted at the contractor’s laboratory research facilities and flight test sites.

Technical efforts will be covered by the specific Task Orders (TOs) issued by the Contracting Officer within the scope of the SOW incorporated in the Basic IDIQ contract. These TOs may involve technical assessments, hardware and software modifications and development, systems engineering development and integration, technology and/or technology application demonstrations in the laboratory or in a flight test or as a participant in a larger demonstration or exercise. The approach of a particular TO may be to first assess the utility of various proposed CID system alternatives that satisfy air-to-air, air-to-ground, ground-to-ground, and ground-to-air mission needs. This may be as simple as a low cost trade study being conducted of past, current, and future technologies of interest to this CASE effort. Or, a particular TO may conduct technology experiments, modeling, simulation, and analytical efforts, laboratory and flight demos, etc., that culminate in operational demonstrations of new CID sensor systems and their alternatives.

TOs will be used to convey technical requirements. The issuance of future TOs will allow the flexibility to provide necessary research for any CID activities. Note that the Basic IDIQ is simply a framework used to issue TOs.

III. Background: Air Force Research Laboratory’s Sensor Directorate, Layered Sensing Exploitation Division’s (AFRL/RYA’s) Combat Identification (CID) program matures, evaluates and demonstrates a wide range of sensor exploitation technologies for advanced capabilities sufficient to be transitioned to the warfighter. The primary objective for CID is to condense sensor data from weapon systems into object ID tags such as “target, friendly, neutral or unknown”. AFRL/RYA accomplishes this goal by exploiting mature sensor technologies to develop long range, high confidence object identification algorithms. Raw data can originate from any sensor type such as active radars or passive cameras. Detection algorithms can be any standard signal processing method such as doppler hits from radar sensors or change detection hits from infrared sensors. Other signal processing algorithms then convert the information to formats suitable for humans, computers, or some combination thereof, to comprehend.

Budget constraints are forcing program managers to factor overall cradle-to-grave lifetime costs of new and legacy sensor object identification weapon systems. Some legacy systems have substantial costs. For example, generating supervised training data sets sometimes requires target measurements in a very controlled environment that are expensive to collect. Then reducing the data is notoriously very labor intensive and expensive. Therefore, some systems, the cost to generate and maintain target databases increases each year and will eventually become unsustainable. Consequently, this Compact ATR and Sustainable Environment (CASE) effort will develop CID technologies which are cost effective yet still robust enough to prevent horrible outcomes such as, fratricide.

The final goal of the program deals with proprietary rights. Most platforms currently in DoD inventory are comprised of contractor proprietary sub-systems where the government is constrained to return to the developmental contractor for all enhancements. This slows or prevents innovation while at the same time driving up yearly operational costs . The CASE program will strive to not repeat these mistakes by investigating the potential for a new open architecture CID environment. The hope is that future government program managers and engineers will have complete flexibility to enable third-party upgrades to any sub-system that uses CASE technologies on any platform resulting in huge savings to taxpayers.

IV. Technical Requirements: The following describe notional areas of potential research that may be conducted under this CASE effort via future TOs. Refer to TOs for actual technical requirements.

1. Characterization and development of infrared, visible, hyper-spectral, ultraviolet, millimeter, laser, acoustic, etc., sensor systems.

2. Object signature measurements in any sensor spectrum.

3. Object salient features derivation and extraction for database development.

4. Objects in real-world environmental environments modeling and simulation including propagation and detection phenomenology investigations.

5. Development and optimization of automatic object identification algorithms.

6. Simulation of CID weapons and/or payloads against objects for evaluation of effectiveness and confidence levels.

7. Signal processing algorithm development and testing to include implementation of algorithms on high performance data processors.

8. Laboratory, flight-line, and aerial integration and testing.

9. Data reduction and ground truthing programming methods.

10. Optimization of legacy CID systems for reduction in object database size and complexity while maintaining existing confidence levels.

11. Use of the latest technology advancements and developing innovative approaches to the CID problem.

12. Related tasks per quick-reaction/urgent need DoD requirements.

New object classification concepts will be explored on a continuing basis along with revisiting legacy CID systems and ideas when necessary. Efforts include designing and fabricating specialized equipment and conducting lab/field/flight tests for the confirmation of concepts, identify problem areas and to collect necessary test or calibration data. As part of performing research, operation of existing or purchasing of new special test equipment, utilizing the most recent technology may be required.

V. Funding Profile(up to 3 IDIQ Basic Contracts):

VI. Deliverable Items:

Data Items: Data shall be delivered in accordance with the Contract Data Requirements List (CDRL) items identified in the attached listing.

Software: Software deliverables are anticipated as required, and will be considered during the evaluation of each Task Order (TO) proposal.

Hardware: Hardware deliverables are anticipated as required, and will be considered during the evaluation of each TO proposal.

VII. Government Furnished Property (GFP): GFP will be later determined as necessary for each individual TO.

VIII. Base Support: Base support will be later determined as necessary for each individual TO.

IX. Security Requirements: Refer to attached DD254.

OPSEC: Procedures, policies and awareness is required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the lifecycle of the contract. The Critical Information List will be provided upon request by the RY Security Office. While working on a government installation OPSEC will be provided by the RYOY Security Office. The contractor shall participate with the Government in the development of a Program Protection Plan (PPP), to include the identification of Critical Program Information (CPI), and shall also participate with the Government in determining countermeasures needed to safeguard the CPI throughout the acquisition process. The contractor shall plan for and execute program protection in accordance with the PPP and program guidance.

Export Control: International Traffic in Arms Regulations (ITAR) (Export Control) applies. The contractor shall be required to generate or require access to export-controlled items.

X. Associated Contractor Agreement (ACA): To be determined upon review of proposals. It is expected that ACAs or NDAs, where suitable, will apply to this program.

XI. Miscellaneous: Government anticipates close coordination with the contractor during the course of this program. The number, type, and location of various design reviews, video teleconferences, meetings, program reviews, etc., are negotiable. It is the intent of the Government to participate with contractors during all tests fostering informal and frequent exchanges of information and to pursue an overall strategy consistent with cooperation and success. Contractor is expected to provide access for appropriate Government personnel to the documentation necessary to gain visibility into the technical progress, schedule, management and financial status, and any other documentation required to complete this program. Data transactions shall include both paper and electronic media, as mutually agreed upon. Interim and Final Program reviews may be held at Government facilities at WPAFB, OH. To save on travel costs, VTC technology may be utilized.

TASK ORDER (TO) 0001

COMPACT ATR AND SUSTAINABLE ENVIRONMENT (CASE)

STATEMENT OF OBJECTIVE

TO 0001 TITLE: “Compact Feature ATR Feasibility Study”

I. Background: Legacy Automated Target Recognition (ATR) technologies have long logistic tails and proprietary issues when it comes to improvements, updates, and maintenance issues. This inherently makes it difficult, time consuming and costly to taxpayers for cradle-to-grave Combat ID (CID) weapon systems.

II. Objectives:

Identification of potential solutions: The contractor shall address cost, efficiency, and sustainably limitation issues associated with the development, operation and maintenance of current ATR CID technologies. The hope is that complex, extensive image/signature template databases may be replaced with low cost sustainable ATRs that use compact feature sets. This would allow for object databases to be quickly updated possibly on the fly. Updates may occur when, for example, new objects (e.g., targets, friendly’s, etc.) of interest or signatures are obtained. Or, updates may be necessary when, for example, a new salient feature of a particular target object is discovered. If updates to legacy ATRs are not feasible then the only option may be a replacement in its entirety with a more efficient and less costly version that still maintains or increases combat performance results. Even though any sensor system is of interest, this TO should concentrate on EO, IR, Radar and/or 3D sensing type sensors.

Analysis of potential solutions: Research shall then switch to analysis of potential solutions or areas of opportunity for compact feature ATRs. Investigation of potential novel parametric target representations will be utilized to generate a study of CID tradeoffs based on salient (robust and discriminative) features. These features may be derived from physical and/or phenomenological attributes that may lead to compact feature sets for class-level and type-level identification of military and civilian ground targets. The contractor shall analyze feature uncertainty and utilize this to predict object identification performance. This study shall also include multi-phenomenology ATRs that may exploit compact databases to include an evaluation of their performance. Metrics that assess ATR efficiency and sustainability improvements will also be established with justifications from reliable sources. Analysis results may require some modeling and simulation which shall be left to the discretion of the contractor.

Recommendation of possible solutions: Lastly, the contractor shall recommend potential solutions, supported by the analysis, in the final report and not just those recommended in the SOO or this TO. Results may be used as a “way forward” for subsequent TOs. Pros and Cons of all issues identified shall be addressed in the final report. Conclusions from this TO’s final report will be used by DoD program managers in the development of future CID investments.

III. Deliverables:

TO 0001 Reporting Requirements: See required CDRL items below.

TO 0001 Deliverable Items: Reports and Data TO 0001 Data Deliverables Required:

CONTRACT DATA REQUIREMENTS LIST (CDRL) for TO 0001

TO 0001 Other Deliverable Items:

i. Software: None identified for TO 0001.

ii. Hardware: None identified for TO 0001.

iii. Other: None identified for TO 0001.

IV. Schedule:

TO 0001 Schedule:

a. Period of Performance: 12 months (9 months Technical Effort, 3 months Final Report)

b. Data Items: Refer to CDRL items above for TO 0001

c. Software: N/A

d. Hardware: N/A V. Funding:

TO 0001 Funding Profile:

VI. Security

TO 0001 Security Requirements: Refer to the DD254 attached.

TO 0001 Export Control: The contractor will be required to generate or require access to export-controlled items.

TO 0001 OPSEC: General OPSEC procedures, policies and awareness are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the lifecycle of the contract. The Critical Information List will be provided upon request by the RYY Security Office. While working on the government installation OPSEC will be provided by the RYOY Security Office

VII. Miscellaneous

TO 0001 Associated Contractor Agreement (ACA): To be determined upon review of proposals.

TO 0001 Government Furnished Property (GFP): N/A

TO 0001 Base Support: N/A TO 0001 Contractor Acquired Property: NA

TO 0001 Computer/Network Access: N/A

TO 0001 Hazmat: N/A TO 0001 Ozone Depleting: N/A

TO 0001 GFI and/or Software: N/A

TO 0001 Human Use: N/A

TO 0001 Animal Use: N/A

BASIC IDIQ and TASK ORDER (TO) 0001

2. Other Requirements:

iv. Program security classification: This effort requires a SECRET facility clearance and SECRET safeguarding capability. A solicitation-ready DD254 has been processed and included as an attachment. Offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

v. 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.

vi. Export-Controlled Items: As prescribed by DFARS 204.7303, DFARS 252.204-7008, “Export-Controlled Item (APR 2010)” is contained in this solicitation (as shown below). This clause shall be contained in ALL solicitations and resulting contracts.

EXPORT-CONTROLLED ITEMS (APR 2010)

(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)

3. Other Information:

vii. Multiple awards, up to 3, subject to Fair Opportunity are anticipated.

viii. Data Rights Desired:

(1) Technical Data: Unlimited Rights

(2) Non-Commercial Software (NCS): Unlimited Rights

(3) NCS Documentation: Unlimited Rights

(4) Commercial Computer Software Rights: Customary License

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.

4. Award Information

b. Anticipated Award Date: Basic IDIQ and TO 0001: 20 May 13

c. Anticipated funding: (Entire program up to three (3) Basic IDIQ Awards)

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.

d. Number of awards anticipated: Up to three (3) Basic IDIQ awards and (3) TO 0001 awards subject to fair oportunity.

5. Eligibility Information

e. Eligible Offeror: This is an unrestricted solicitation. Small businesses are encouraged to propose on all or any part of this solicitation.

f. Cost Sharing or Matching: Cost Sharing or matching is not required.

g. Federally Funded Research and Development Centers: The following guidance is provided for Federally Funded Research and Development Centers (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 solicitation. 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 (in this case AFRL) 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.

h. 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.

i. Other information:

i. Foreign participation: No.

ii. 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 solicitation. 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.

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

iv. You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date as identified above.

6. Proposal and Submission Information

j. Overview: 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 award some, all, or none of the 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. For additional information, a copy of the Broad Agency Announcement (BAA) Guide for Industry is available at: http://www.wpafb.af.mil/shared/media/document/AFD-120614-075.pdf.

Please Note: If you intend to submit a grant or assistance instrument, go on to Section 2 below which discusses how to find the grant opportunity, prepare the cover page, and complete the certification. This section also provides the process for electronic submission of proposals for grants and cooperative agreements. If, however, you intend to propose a contract, proceed directly to Section 3 below—“Content and Form for Proposal Submission.”

b. Content and Form of Proposal Submission: The paragraphs below identify proposal format and content. Offerors must propose the following to be considered for ID/IQ award:

· A basic ID/IQ contract proposal and a proposal for Task Order OOO1,

· A SOW for T.O. 0001 must be submitted in response to T.O. 0001 SOO, and

· A cost proposal for T.O. 0001.

1. General Instructions: Offerors should apply the restrictive notice prescribed in the provision of 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. Proposals must reference the announcement number STROEB II BAA, 09-01-PKS, Call 50. Offerors must submit one-original and 5 hard copies of their proposals via mail or other carrier to the Contracting POC, identified in Section VII. 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.

2. Technical/Management Proposal:

i. Page Limitations: The following describes the page limitations on the proposal submittal:

(a) Technical/Management Proposal shall be limited to 25 pages for T.O 0001 and the Basic ID/IQ, prepared and submitted in Microsoft Word format.

(b) Font shall be standard 10-point business font Arial.

(c) Character spacing must be “normal,” not condensed in any manner.

(d) Pages shall be double-spaced (must use standard double-space function in Microsoft Word), double sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom.

(e) 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.

(f) Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 25 for T.O. 0001 and for the Basic ID/IQ. 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.

(g) The proposal 25 page limit does not include the offeror’s proposed Statement of Work (SOW); however, the same formatting rules apply to the SOW, which is limited to 5 pages. The SOW is required for T.O. 0001.

(h) A CD/DVD 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 copies.

(i) Please note: the Government will check the MS Word version of 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.

ii. The Technical/Management proposal shall include a discussion of the nature and scope of the research and the technical approach. Additional information on prior work in this area, descriptions of available equipment, data and facilities and resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal. The Technical/Management volume shall include a SOW detailing the technical tasks proposed to accomplished the provided SOO and suitable for contract incorporation. Do not include any proprietary information in the SOW. Refer to the BAA Guide for Industry referenced above to assist in SOW preparation. If Government Furnished Property is requested you are required to submit the following information with your offer—

(a) A list or description of all Government property that the offeror or its subcontractors propose to use on a rent-free basis. 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);

(b) The dates during which the property will be available 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;

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

(d) 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.

iii. Any questions concerning the Technical/Management proposal or SOW preparation shall be referred to the Technical POC cited in the Overview Information and VII.

3. Cost/Business Proposal:

i. Separate Cost/Business Proposal into a business section and cost section. Adequate price competition is anticipated.

(a) The business section should contain all business aspects to the proposed contract, such as type of contractual instrument proposed, any exceptions to terms and conditions of the announcement model contract, CAGE Code, and any business information not technically related, etc. Provide rationale for exceptions. Identify any technical data that will be delivered with less than unlimited rights.

(b) Cost proposals have no page limitations; however, offerors are requested to keep cost proposals to less than 50 pages as a goal. The proposal shall be furnished with supporting schedules and shall contain a person hour breakdown per task. Refer to the BAA Guide for Industry for detailed proposal instructions. Cost proposal is required only for Task Order 0001, not the Basic Contract.

ii. 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. Small business concerns are exempt from this requirement. If an ID/IQ contract arrangement is anticipated, the basis for the subcontracting plan should reflect the entire ceiling amount.

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

4. Proposal Due Date and Time: 25 Feb 2013, 3:00 P.M. Eastern Standard Time (EST) NOTE: Proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3).

NOTE: Intent to Propose: Offerors that anticipate submitting a proposal are requested to submit an e-mail to Jennifer Kleiv, at jennifer.kleiv@wpafb.af.mil containing the name of the contractor, the POC, and the contractor’s intent to submit a proposal. This “Intent to Propose” is requested by 1 Feb 2013, 4:00 p.m. EST.

5. Intergovernmental Review: N/A

6. Funding Restrictions: N/A

7. Other Submission Requirements: Proposals must be submitted to: Jennifer Kleiv, Det 1 AFRL/RQKSR, Bldg 167, 2310 8th St., Wright-Patterson AFB, OH 45433-7801.

II. Proposal Review Information

a. Evaluation Criteria: The selection of one or more sources for award will be based on an evaluation of each offeror’s proposal (both technical and cost/price aspects) to determine the overall merit of the proposal in response to the announcement, as well as on Agency need and funding availability. The technical aspect shall be evaluated based on the following criteria:

a. Basic IDIQ Contract Technical Evaluation (Deemed Equal Importance as TO 0001): Technical aspect shall be evaluated based on the following criteria that are of descending order of importance:

i. Unique and innovative approach proposed to accomplish the technical objectives. New and creative solutions and/or advances in knowledge, understanding, technology, and the state of the art.

ii. The offeror’s understanding of the scope of the technical effort.

iii. Soundness of the offeror’s technical approach.

ii. Availability of qualified technical personnel and their experience with the applicable technologies.

vi. Availability, from any source, of necessary research, test, laboratory, or shop facilities.

b. Task Order(s) Technical Evaluation (Deemed Equal Importance as the Basic IDIQ Contract): Technical aspect shall be evaluated based on the following criteria that are of descending order of importance:

i. Unique and innovative approach proposed to accomplish the technical objectives. New and creative solutions and/or advances in knowledge, understanding, technology, and the state of the art.

ii. The offeror’s understanding of the scope of the technical effort.

iii. Soundness of the offeror’s technical approach.

iii. The potential for AFRL to transition the research and development deliverables to future Government needs. Any proposed restriction on technical data or computer software will be considered.

iv. Availability of qualified technical personnel and their experience with the applicable technologies.

vi. Availability, from any source, of necessary research, test, laboratory, or shop facilities.

c. Task Order(s) Cost/Price Evaluation (Substantial factor but second in priority to TO Technical Evaluation): Cost/Price includes the reasonableness and realism of the proposed cost and fee and consideration of proposed budgets and funding profiles. Cost/Price is a substantial factor, but ranked as the second order of priority. (If an offeror proposes the use of GFP other than any GFP identified in this BAA, and that proposed GFP provides the offeror an unfair competitive advantage, then FAR 45.202 requires rental equivalent be applied to the Cost Factor for evaluation purposes only).

d. Proposal Risk Assessment (Basic and Task Orders): Proposal risk for technical, cost, and schedule will be assessed as part of the evaluation of the above evaluation criteria. Proposal risk relates to the identification and assessment of the risks associated with an offeror's proposed approach as it relates to accomplishing the proposed effort. Tradeoffs of the assessed risk will be weighed against the potential payoff.

b. Review and Selection Process

a. Categories: The technical and cost proposals will be evaluated at the same time and categorized as follows:

i. Category I: Demonstrates technical merit. Is important to agency programs. The offeror presents relevant experience and access to adequate resources. Risk is acceptable. The cost/price is reasonable and realistic. Proposals in Category I are recommended for acceptance (subject to availability of funds) and normally are displaced only by other Category I proposals.

ii. Category II: Demonstrates technical merit; is important to agency programs; and presents relevant experience and access to adequate resources; but requires further development. Risk is acceptable. The cost/price is reasonable and realistic. Category II proposals are recommended for acceptance, but at a lower priority than Category I.

iii. Category III: Does not demonstrate technical merit; does not meet agency needs; does not present adequate experience or resources; the risk level is unacceptable; or the cost/price is not reasonable or realistic.

b. No other evaluation criteria will be used. The Air Force reserves the right to select for award any, all, part or none of each proposal received.

VI. Award Administration Information

1. Award Notices: Offerors will be notified whether their proposal is recommended for award, by letter or e-mail, on or about 5 Apr 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.

2. Administrative and National Policy Requirements: See Section I.

3. Reporting: Refer to attached CDRL items.

VII. Agency Contacts

1. Address technical questions to: Pat Marshall, 2241 Avionics Circle, Wright-Patterson AFB, OH 45433, (937) 938-4294, pat.marshall@wpafb.af.mil

2. Address contracting questions to: Jennifer Kleiv, Contract Negotiator, 2310 Eighth St, Bldg 167, Wright Patterson AFB, OH 45433-7801, (937) 656-9828, jennifer.kleiv@wpafb.af.mil or Joel B. Harrah, Contracting Officer, 2310 Eighth St, Bldg 167, Wright Patterson AFB, OH 45433-7801, (937) 255-5306, Joel.Harrah@wpafb.af.mil VIII. Other Information

1. Acquisition of Commercial Items: Based upon market research, the Government is not using the policies contained in Part 12, Acquisition of Commercial Items, in its solicitation 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.

2. Support contractors: Only Government employees will evaluate 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.

3. Communications: 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.

4. Debriefings: When…