BAA-11-04-PKV.doc

1-Step Broad Agency Announcement

Overview Information Federal Agency Name: Air Force Research Laboratory, AFRL/RB, Air Vehicles Directorate Broad Agency Announcement Title: Technology Research, Integration, and Demonstration (TRIAD) Program Broad Agency Announcement Type: This is the Initial Announcement Broad Agency Announcement Number: BAA 11-04-PKV Catalog of Federal Domestic Assistance (CFDA) Number(s): 12.800_AF Proposal Due Date and Time: 25 July 2011, 1:00 P.M EST Time. 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. Please note that due to the heightened level of Security to BRAVO on Wright Patterson Air Force Base, proposals remain due to the Contracting Officer on 25 July 2011, by 1:00 P.M. EST. They will be accepted in Area B, Bldg. 167, 2310 8th Street, Wright-Patterson AFB, OH 45433. Proposals will also be accepted at the main Area B Visitor Center, Bldg 81, Wright-Patterson AFB, OH 45433, adjacent to Gate 1B, which is the Springfield Street entrance. Contractors may call Carol South, (937) 255-5455, Steve Brumfield, (937) 656-9639, and/or Scott Hudnell (937) 656-9003, for pick up.

Solicitation Request: Air Force Research Laboratory, AFRL/RB Air Vehicles Directorate, 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. The NAICS Code for this acquisition is 541712, 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.

CCR Registration: Unless exempted by 2 CFR 25.110 all offerors must (1) Be registered in the Central Contractor Registration (CCR) prior to submitting an 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 registration instructions can be accessed from the DISA CCR home page at http://www.ccr.gov.

On-line Representations and Certifications: Potential offerors are notified that effective 01 Jan 2005 to be eligible for an award; they must submit annual Electronic Representations and Certifications, otherwise known as On-line Representations and Certifications Application (ORCA) via the Business Partner Network (BPN) at http://www.bpn.gov/orca. These FAR and DFARS level representations and certifications are required in addition to the representations and certifications specific to this acquisition. Before submitting the Electronic Representations and Certifications, contractors must be registered in the Central Contractor Registration (CCR) Database.

Type of Contract/Instrument: Indefinite Delivery/Indefinite Quantity (IDIQ) contract(s) with Cost Plus Fixed Fee Completion Type task orders. Assistance instruments are not contemplated.

Estimated Program Cost: $44.3M shared ceiling.

Anticipated Number of Awards: The Air Force anticipates awarding two to three awards for this announcement, but reserves the right to award all, part, or none of the proposals received. Offerors must propose to the Basic IDIQ contract and all three task orders in order to be eligible to receive an award. Task Order Only proposals will not be evaluated.

Brief Program Summary: The TRIAD Program will conduct basic, advanced, applied and demonstration/validation research to develop, demonstrate, integrate and transition new air and space vehicle structures technologies to the Warfighter. These technologies will provide cost effective, survivable air and space vehicle platforms capable of accurate delivery of weapons and cargo worldwide. The offeror will require access to a broad range of technical and experimental structural disciplines and expertise to accomplish the TRIAD Program task orders.

Address TRIAD technical questions to: Scott Burns, AFRL/RBSI, 2130 8th Street, Wright-Patterson AFB, OH 45433, (937) 255-8539, Richard.Burns@wpafb.af.mil OR Sarah Miller, AFRL/RBSV, 2790 D Street, Wright-Patterson AFB, OH 45433, (937) 255-0676, Sarah.Miller2@wpafb.af.mil.

Address Task Order technical questions to:

Task Order 1: Mike Falugi, AFRL/RBSA, 2130 8th Street, Wright-Patterson AFB, OH 45433, (937) 938-4949, Michael.Falugi@wpafb.af.mil.

Task Order 2: Andy Swanson, AFRL/RBSA, 2790 D Street, Wright-Patterson AFB, OH 45433, (937) 904-6755, Andrew.Swanson@wpafb.af.mil.

Task Order 3: Brett Hauber, AFRL/RBSA, 2790 D Street, Wright-Patterson AFB, OH 45433, (937) 904-6871, Brett.Hauber@wpafb.af.mil.

Address contracting questions to: Carol South, AFRL/PKVA, 2310 8th Street, Wright-Patterson AFB, OH 45433, (937) 255-5455, Carol.South@wpafb.af.mil. Alternate POCs: Steve Brumfield, AFRL/PKVA, 2310 8th Street, Wright-Patterson AFB, OH 45433, (937) 656-9639, Steven.Brumfield@wpafb.af.mil OR Scott Hudnell, AFRL/PKVA, 2310 8th Street, Wright-Patterson AFB, OH 45433, (937) 656-9003, Scott.Hudnell@wpafb.af.mil.

Full Text Announcement

I.

Program Description: Air Force Research Laboratory, Air Vehicles Directorate, AFRL/RB is soliciting technical and cost proposals on the following research effort:

1. Statement of Objective/Needs: The Structures Division of the Air Vehicles Directorate has been conducting Research and Development (R&D) programs through the Structural Technology Evaluation and Analysis Program (STEAP). STEAP is an Indefinite Delivery/Indefinite Quantity (ID/IQ) program. The Technology Research, Integration & Demonstration (TRIAD) Program will be the follow-on ID/IQ program to STEAP.

Through the use of TRIAD Program task orders, air and space vehicle structures R&D will be conducted to deliver future air and space vehicle capabilities to the Warfighter. This R&D will include, but is not limited to, conceptual design studies, experimental test planning and execution, model fabrication/modification, analytical and experimental data analyses, systems engineering assessments, technology assessments and evaluations, and computational analyses. The R&D activities will be focused around the following Structures Division technical competencies:

(a) Structural Response Prediction: Identifies fluid-thermal-structural coupling requirements necessary for performance predictions in extreme environments (large thermal gradients and transient temperatures, very high mechanical and dynamic loading at elevated temperatures, and long-duration exposure to high-temperature, oxidizing environments). Research needs include aero-thermo-mechanical coupling, nonlinear structural response, aero/acoustic structural coupling, identification of relevant limit states, and integration of material evolution into structural models.

(b) Structural Life Forecasting: Develops techniques to forecast the remaining useful life of aircraft structures. Research needs include multi-scale modeling, local damage to global structural failure, multi-physics and multi-disciplinary science, mechanism-based models, holistic consideration of damage, probabilistic analysis, investigation of damage mechanisms, mechanism-based damage models, and a computational framework for damage models in structural simulations.

(c) Structural Integrity: Develops techniques to extend the remaining useful life of metallic, composite, and hybrid aircraft structures. Research needs include advanced fatigue life prediction tools, fatigue life enhancement concepts, high-fidelity composite damage progression analysis tools, composite/hybrid repair concepts, design tools for composite/hybrid structures, and structural replacement concepts for fatigue-sensitive structures.

(d) Geometry Modeling and Design: Develops efficient modeling methods to enable system design that captures all the relevant physics driving the design. It also develops design space exploration methods to produce optimal and robust design solutions. Research needs include parametric associative modeling, generalized geometric shape and mesh sensitivities, nonlinear analysis of multidisciplinary design optimization (MDO) process, risk-quantified, multi-level design exploration and optimization, and large scale distributed MDO computing framework.

(e) Multidisciplinary Modeling and Analysis: Develops flexible, cost-effective, and risk-quantified methods for analyzing physics to enable system design and technology validation. Research needs include multidisciplinary analysis capability for design, algorithms for obtaining appropriate-fidelity solutions and sensitivities, sensitivity analysis, analysis processes for nondeterministic models, and experimental techniques for method validation.

(f) Adaptive Structures: Develops revolutionary aerospace structures capable of adapting to environmental and mission changes. Research needs include smart materials, shape control, and energy harvesting.

(g) Multifunctional Structures: Develops technologies that increase mission effectiveness by utilizing the structure as an integral host for a variety of functions that improve or enable new system capabilities. Research needs include load bearing RF antennas, structural state sensing, and energy storage concepts.

(h) Hybrid Structures: Develops design concepts, methods, and tools that will allow the optimal use of traditional metallic materials, non-traditional metallic materials, ceramics, and polymer composite materials. Research needs include predicting the complex internal stresses and strains that result from the joining of dissimilar materials for stronger, lighter, and more durable joints.

(i) Thermal Structures: Develops structural concepts that permit rapid-turn, affordable, all weather space access and hypersonic cruise vehicle operations. Research needs include small-radius leading edge concepts, improved thermal protection systems offering durability and operability, hot structures concepts, test and analysis methods, and extreme environment instrumentation.

(j) Experimental Validation: Develops accurate and repeatable structural test and structural response measurement sensor/systems, innovative control and data acquisition techniques/systems, and methods to impose representative aerospace vehicle flight conditions during ground test validation activities (including extreme aerospace test environments). Research needs include structural response measurements (parameters include strain, mechanical force, heat flux, temperature, acceleration, displacement, frequency, and pressure), sensor installation and attachment methods, analytical modeling of distributed feedback systems and sensor networks, industrial communications and applications to enable sensor fusion, dynamic primary feedback correlation with auxiliary sensors, distributed data fusion enabling intelligent control, and generation and application of thermal, acoustic, and mechanical load parameters.

R&D activities within these technical competencies may require the use of technology demonstration vehicles, ground test facilities, flight test facilities and/or laboratory experiments to develop, analyze, and assess air and space vehicle structures technologies. R&D activities will be performed at Air Vehicles Directorate facilities, industry/university facilities, and/or mutually agreed upon locations and will be restricted to the unclassified domain. R&D activities within these technical competencies may require the use of, but not limited to, technical software packages such as ABAQUS, Auto CAD, Lab View, MATLAB, and SolidWorks.

It is anticipated that the offeror may establish teaming arrangements with universities and other companies to successfully accomplish the TRIAD Program task orders. Additionally, the offeror shall be responsible for the overall technical, administrative, and financial management functions of the contract to ensure efficient and effective execution of all task orders. These management functions include, but are not limited to, (1) executive-level participation for meetings and program reviews, (2) planning, scheduling, supervision, and execution of task order activities and milestones, (3) describing status of each task order, (4) outlining contractor activity and progress toward accomplishment of task order objectives, (5) planning, forecasting, and making recommendations on funding and funding changes, and (6) the delivery of reports as required for each task order.

2. Deliverable Items:

a. Data Items: Reference attached DD Forms 1423-1. It is the government’s desire to obtain Unlimited Data Rights whenever possible.

b. Software: Any requirements will be addressed in each task order as determined necessary.

c. Hardware: Any requirements will be addressed in each task order as determined necessary.

d. Other: Any requirements will be addressed in each task order as determined necessary.

3. Schedule:

a. Overall effort: The IDIQ contract will have an ordering period of 60 months, and all orders must be technically complete within 84 months, and all final reports for individual orders must be complete within 87 months.

b. Task Orders: TO 0001, 36 months technical effort, with 3 additional months to complete the final report; TO 0002, 12 months technical effort, with 3 additional months to complete the final report; TO 0003, 45 months technical effort, with 3 additional months to complete the final report.

c. Data Items: To be determined for individual task orders.

d. Software: To be determined for individual task orders.

e. Hardware: To be determined for individual task orders.

4. Other Requirements:

a. Program security classification: Unclassified

b. Export Control: Information involved in this research effort may 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. Export Control will be determined for each individual task order.

c. 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)

d. The contractor shall train personnel in, and follow, appropriate Operations Security (OPSEC) measures during the performance of this program.

5. Other Information:

a. Government Furnished Property (GFP) availability: GFP will be made available as required for each individual task order. As required by DFARS 211.274-4, the clause 252.211-7007, Reporting of Government Furnished Equipment in the DoD Item Unique Identification (IUID) Registry (Nov 2008) will be added to this solicitation in Section VIII, and in any resulting basic IDIQ contract. In addition, the clause FAR 52.245-1, Government Property and/or FAR 52.245-2, Government Property Installation Operation Services will be included in any resulting basic IDIQ contract.

b. Base Support/ Network Access: Clauses will be included in the basic IDIQ contract in the event that base support is required as identified in future task orders, as appropriate.

Contractor personnel, if on site TBD per Task Order, will require access. Clause 5352.242-9001, Common Access Cards (CACS) for Contractor Personnel-AFR (Aug 2004) may be required. The following CAC clause contains the following information:

(1) For installation(s)/location(s) cited in the contract, contractors shall ensure Common Access Cards (CACs) are obtained by all contract or subcontract personnel who meet one or both of the following criteria:

(a) Require logical access to Department of Defense computer networks and systems in either:

(i) the unclassified environment; or

(ii) the classified environment where authorized by governing security directives.

(b) Perform work which requires the use of a CAC for installation entry control or physical access to facilities and buildings.

(2) Contractors and their personnel shall use the following procedures to obtain CACs:

(a) Contractors shall provide a listing of personnel authorized a CAC to the contracting officer. The contracting officer will provide a copy of the listing to the government representative in the local organization designated to authorize issuance of contractor CACs (i.e., "authorizing official").

(b) Contractor personnel on the listing shall each complete and submit a DD Form 1172-2 or other authorized DoD electronic form to the authorizing official. The authorizing official will verify the applicant's name against the contractor's listing and return the DD Form 1172-2 to the contractor personnel.

(c) Contractor personnel will proceed to the nearest CAC issuance workstation (usually the local Military Personnel Flight (MPF) with the DD Form 1172-2 and appropriate documentation to support their identification and/or citizenship. The CAC issuance workstation will then issue the CAC.

(3) While visiting or performing work on installation(s)/location(s), contractor personnel shall wear or prominently display the CAC as required by the governing local policy.

(4) During the performance period of the contract, the contractor shall:

(a) Within 7 working days of any changes to the listing of the contract personnel authorized a CAC, provide an updated listing to the contracting officer who will provide the updated listing to the authorizing official;

(b) Return CACs in accordance with local policy/directives within 7 working days of a change in status for contractor personnel who no longer require logical or physical access;

(c) Return CACs in accordance with local policy/directives within 7 working days following a CACs expiration date; and

(d) Report lost or stolen CACs in accordance with local policy/directives.

(5) Within 7 working days following completion/termination of the contract, the contractor shall return all CACs issued to their personnel to the issuing office or the location specified by local policy/directives.

(6) Failure to comply with these requirements may result in withholding of final payment.

c. Multiple awards subject to Fair Opportunity are anticipated.

d. Data Rights Desired:

(1) Technical Data: Unlimited Rights (negotiated on an order by order basis)

(2) Non-Commercial Software (NCS): Unlimited Rights (negotiated on an order by order basis)

(3) NCS Documentation: Unlimited Rights (negotiated on an order by order basis)

(4) Commercial Computer Software Rights: Commercial Customer 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 noncommercial). 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.

VI. Award Information

1. Anticipated Award Date: 07 Oct 2011

2. Anticipated Funding

a. Funding for the basic program (not per contract): FY11/$0.3M; FY12/$8.7M; FY13/$8.9M; FY14/$8.8M; FY15/$8.8M; FY16/$8.8M.

b. Funding for Task Order 1: FY11/$100K; FY12/$450K; FY13/$700K; FY14/$280K; one award is anticipated.

c. Funding for Task Order 2: FY11/$180K; FY12/$80K; one award is anticipated.

d. Funding for Task Order 3: FY11/$25K; FY12/$100K; FY13/$100K; FY14/$100K; FY15/$75K; one award is anticipated.

e. The above funding profiles are estimates only and will not be a contractual obligation for funding as all funding is subject to change due to Government discretion and availability

3. Number of awards anticipated: Two to three awards, however, the government reserves the right to award all, part, or none of the proposals received.

VII. Eligibility Information

1. Eligible Offeror: This is an unrestricted solicitation. Small businesses are encouraged to propose. Offerors must propose a Basic IDIQ contract in order to be eligible to receive award of one or more Task Orders. Task Order Only proposals will not be evaluated.

2. Cost Sharing or Matching: Cost Sharing is not required. Ratio: 0/0.

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

4. Other:

a. Foreign participation: No.

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

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

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

VIII. Proposal and Submission Information

1. Overview: 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. There is no additional information to be provided.

2. Proposals for Grants and Cooperative Agreements: Will not be accepted.

3. Content and Form of Proposal Submission: The paragraphs below identify proposal format and content. Proposals should be addressed via mail to the Contracting Point of Contact (POC) identified in Section VII.

a. 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/library/factsheets/factsheet.asp?id=9218. 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 BAA 11-04-PKV. Offerors must submit one-original and 3 hard copies and 4 copies on CDs of their Basic Proposals and one-original and 4 hard copies and 5 copies on CDs of their Task Order Proposals via mail 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.

b. Technical/Management Proposal:

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

(bi) Basic Proposals shall be limited to 75 pages, prepared and submitted in Word format.

(bj) Task Order Proposals shall be limited to 25 pages, prepared and submitted in Word format.

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

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

(bm) Pages shall be double-spaced, single-sided, 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom. Lines between text lines must also be 10-point.

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

(bo) Pages shall be numbered starting with the cover page being Page 1, and the last page being Page 75 for the Basic Proposals and 25 for the Task Order Proposals. 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.

(bp) The proposal 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 10 pages for both the Basic Proposal and the Task Order Proposals.

(bq) A CD with the 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.

(br) Due to continuing attempts by numerous offerors to obtain an unfair advantage by failing to conform to the formatting rules above, 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. In addition if the proposal or SOW does not conform to the above requirements, a notification will be sent to the offeror’s company management to advise of the nonconformance.

ii. The 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 Basic Proposal and each Task Order Proposal shall include a SOW detailing the technical tasks proposed to be accomplished under the proposed effort 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.

iv. Any questions concerning the technical proposal or SOW preparation shall be referred to the respective Technical or Task Order POC cited in the Overview Information.

c. Cost/Business Proposal:

i. Separate the proposal into a business section and cost section. Adequate price competition is anticipated. 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 model contract, any information not technically related, etc. Provide rationale for exceptions. Cost proposals have no page limitations; however, offerors are requested to keep cost proposals to 25 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.

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 July 2011, 1:00 P.M 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 Carol South at Carol.South@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 5 July 2011, 3:00 p.m. EST.

5. Intergovernmental Review: None.

6. Funding Restrictions: None.

7. Other Submission Requirements: Proposals must be submitted to:

If by postal mail or hand delivery: Carol South, Det 1 AFRL/PKVA, Bldg 167, 2310 8th St., Wright-Patterson AFB, OH 45433-7801. Alternate POCs: Steve Brumfield, Det 1 AFRL/PKVA, Bldg 167, 2310 8th St., Wright-Patterson AFB, OH 45433-7801 OR Scott Hudnell, Det 1 AFRL/PKVA, Bldg 167, 2310 8th St., Wright-Patterson AFB, OH 45433-7801.

IX. Proposal Review Information

1. 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, which is ranked as the first order of priority, shall be evaluated through an assessment of the proposals on both the Basic ID/IQ contract and the individual Task Order Proposals. Offerors must be determined to be Category I or Category II on the Basic Proposal for Task Order Proposals to be evaluated. The evaluation shall be based on the following criteria that are of equal order of importance:

a. Technical: (for the Basic Proposal) The Basic proposal is more important than the Individual Task Orders

v. Knowledge and technical experience in the ten technical competencies of the Structures Division

vi. Availability of qualified technical personnel and their experience in the ten technical competencies of the Structures Division

vii. Past corporate experience in the ten technical competencies of the Structures Division

viii. Management controls for tracking technical and financial progress on individual task orders and qualified personnel for managing task order programs

b. Technical: (for the Task Order Proposals)

ix. New and innovative approach proposed to accomplish the technical objectives

x. Soundness of the offeror’s technical approach and understanding of the scope of the technical effort

xi. Offeror’s past experience with the individual task order technologies

xii. Availability of qualified technical personnel to support the individual task order programs

xiii. Organization, clarity, and thoroughness of the proposed SOW for the individual task orders

c. Cost/Price: 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: 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.

2. Review and Selection Process

a. Categories: The proposal for the Basic Program will be evaluated first. The technical and cost proposals for the individual Task Orders will be evaluated at the same time and categorized as follows :

i. Category I: Proposal is well conceived, scientifically and technically sound, pertinent to the program goals and objectives, and offered by a responsible contractor with the competent scientific and technical staff and supporting resources needed to ensure satisfactory program results. Proposals in Category I are determined to be acceptable, but will be recommended for award based on availability of funds. They are normally displaced only by other Category I proposals.

ii. Category II: Proposal is scientifically or technically sound, but requires further development, and may be recommended for award, but at a lower priority than Category I.

iii. Category III: Proposal is not technically sound or does not meet agency needs.

b. Offerors must propose on the Basic ID/IQ contract and on all three Task Orders. The Basic ID/IQ Proposal must be determined Category I or II in order for Task Order proposals to be evaluated.

c. 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 30 Sep 2011. 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 Requirements: See Section I.

3. Reporting: Contract Data Requirements List (CDRL) as attached to this announcement will generally apply.

VII. Agency Contacts

1. Address TRIAD technical questions to: Scott Burns, AFRL/RBSI, 2130 8th Street, Wright-Patterson AFB, OH 45433, (937) 255-8539, Richard.Burns@wpafb.af.mil OR Sarah Miller, AFRL/RBSV, 2790 D Street, Wright-Patterson AFB, OH 45433, (937) 255-0676, Sarah.Miller2@wpafb.af.mil.

2. Address Task Order technical questions to:

a. Task Order 1: Mike Falugi, AFRL/RBSA, 2130 8th Street, Wright-Patterson AFB, OH 45433, (937) 938-4949, Michael.Falugi@wpafb.af.mil.

b. Task Order 2: Andy Swanson, AFRL/RBSA, 2790 D Street, Wright-Patterson AFB, OH 45433, (937) 904-6755, Andrew.Swanson@wpafb.af.mil

c. Task Order 3: Brett Hauber, AFRL/RBSA, 2790 D Street, Wright-Patterson AFB, OH 45433, (937) 904-6871, Brett.Hauber@wpafb.af.mil.

3. Address contracting questions to: Carol South, AFRL/PKVA, 2310 8th Street, Wright-Patterson AFB, OH 45433, (937) 255-5455, Carol.South@wpafb.af.mil. Alternate POCs: Steve Brumfield, AFRL/PKVA, 2310 8th Street, Wright-Patterson AFB, OH 45433, (937) 656-9639, Steven.Brumfield@wpafb.af.mil OR Scott Hudnell, AFRL/PKVA, 2310 8th Street, Wright-Patterson AFB, OH 45433, (937) 656-9003, Scott.Hudnell@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: 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. Wide Area Work Flow:

NOTICE: Any contract award resulting from this solicitation will contain the clause at DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports (Mar 2008), which requires electronic submission of all payment requests. The clause cites three possible electronic formats through which to submit electronic payment requests. Pursuant to that clause, the Department of Defense is adopting Wide Area Work Flow-Receipt and Acceptance (WAWF-RA). Any contract resulting from this solicitation will establish a requirement to use WAWF-RA for invoicing and receipt/acceptance, and provide coding instructions applicable to this contract. Contractors are encouraged to take advantage of available training (both web-based and through your local DCMA office), and to register in the WAWF-RA system. Information regarding WAWF-RA, including the web-based training and registration, can be found at https://wawf.eb.mil. Note: This WAWF-RA requirement does not apply to Universities that are audited by an agency other than DCAA.

4. Item Identification and Valuation. Any contract award resulting from this solicitation may contain the clause at DFARS 252.211-7003, Item Identification and Valuation, (Aug 2008) which requires unique item identification and valuation of any deliverable item for which the Government’s unit acquisition cost is $5,000 or more; subassemblies, components, and parts embedded within an item valued at $5,000 or more; or items for which the Government’s unit acquisition cost is less than $5,000 when determined necessary by the requiring activity for serially managed, mission essential, or controlled inventory. Also included are any DoD serially managed subassembly, component, or part embedded within a delivered item and the parent item that contains the embedded subassembly, component, or part. Per DFARS 211.274-3 Policy for Valuation, it is DoD policy that contractors shall be required to identify the Government’s unit acquisition cost for all items delivered, even if none of the criteria for placing a unique item identification mark applies. Therefore, your proposal must clearly break out the unit acquisition cost for any deliverable items. Per DFARS 211.274-3 Policy for Valuation, “The Government’s unit acquisition cost is the Contractor’s estimated fully burdened unit cost at time of delivery to the Government for cost type or undefinitized line, subline, or exhibit line items” (Per DoD, “fully burdened unit costs” to the Government would include all direct, indirect, G&A costs, and an appropriate portion of fee). If you have questions regarding the Unique Item Identification requirements, please contact the Contracting Point of Contact listed above.

For more information, see: http://www.acq.osd.mil/dpap/pdi/uid/index.html.

5. Limitations on Pass-Through Charges. As prescribed in FAR 52.408(n)(1) & 52.408(n)(2), provisions 52.215-22, “Limitations on Pass Through Charges – Identification of Subcontract Effort (Oct 2009),” and 52.215-23, “Limitations on Pass-Through Charges (Oct 2009),” are contained in this solicitation (as shown below). Any contract valued greater than the threshold for cost or pricing data threshold, except fixed price contracts awarded on the basis of adequate price competition, resulting from this solicitation, shall contain the Clause at FAR 52.215-23 (or Alt I).

52.215-22 – Limitations on Pass-Through Charges—Identification of Subcontract Effort (Oct 2009)

(a) Definitions. “Added value, excessive pass-through charge, subcontract, and subcontractor,” as used in this provision, are defined in the clause of this solicitation entitled “Limitations on Pass-Through Charges” (FAR 52.215-23).

(b) General. The offeror’s proposal shall exclude excessive pass-through charges.

(c) Performance of work by the Contractor of a subcontractor.

(1) The offeror shall identify in its proposal the total cost of the work to be performed by the offeror, and the total cost of the work to be performed by each subcontractor, under the contract, task order, or delivery order.

(2) If the offeror intends to subcontract more than 70 percent of the total cost of work to be performed under the contract, task order, or delivery order, the offeror shall identify in its proposal—

(i) The amount of the offeror’s indirect costs and profit/fee applicable to the work to be performed by the subcontractor(s); and

(ii) A description of the added value provided by the offeror as related to the work to be performed by the subcontractor(s).

(3) If any subcontractor proposed under the contract, task order, or delivery order intends to subcontract to a lower-tier subcontractor more than 70 percent of the total cost of work to be performed under its subcontract, the offeror shall identify in its proposal—

(i) The amount of the subcontractor’s indirect costs and profit/fee applicable to the work to be performed by the lower-tier subcontractor(s); and

(ii) A description of the added value provided by the subcontractor as related to the work to be performed by the lower-tier subcontractor(s).

(End of Provision)

52.215-23 – Limitations on Pass-Through Charges (Oct 2009)

(a) Definitions. As used in this clause--

“Added value” means that the Contractor performs subcontract management functions that the Contracting Officer determines are a benefit to the Government (e.g., processing orders of parts or services, maintaining inventory, reducing delivery lead times, managing multiple sources for contract requirements, coordinating deliveries, performing quality assurance functions).

“Excessive pass-through charge,” with respect to a Contractor or subcontractor that adds no or negligible value to a contract or subcontract, means a charge to the Government by the Contractor or subcontractor that is for indirect costs or profit/fee on work performed by a subcontractor (other than charges for the costs of managing subcontracts and any applicable indirect costs and associated profit/fee based on such costs).

“No or negligible value” means the Contractor or subcontractor cannot demonstrate to the Contracting Officer that its effort added value to the contract or subcontract in accomplishing the work performed under the contract (including task or delivery orders).

“Subcontract” means any contract, as defined in FAR 2.101, entered into by a subcontractor to furnish supplies or services for performance of the contract or a subcontract. It includes but is not limited to purchase orders, and changes and modifications to purchase orders.

“Subcontractor,” as defined in FAR 44.101, means any supplier, distributor, vendor, or firm that furnishes supplies or services to or for a prime Contractor or another subcontractor.

(b) General. The Government will not pay excessive pass-through charges. The Contracting Officer shall determine if excessive pass-through charges exist.

(c) Reporting. Required reporting of performance of work by the Contractor or a subcontractor. The Contractor shall notify the Contracting Officer in writing if—

(1) The Contractor changes the amount of subcontract effort after award such that it exceeds…