FA8650-16-S-5001-Call002-SOO.pdf

BROAD AGENCY ANNOUNCEMENT BAA# FA8650-16-S-5001

MATERIALS & MANUFACTURING DIRECTORATE

WHITE PAPER CALL 002

“ADVANCED POWER TECHNOLOGY OFFICE – ENERGY INNOVATION”

WHITE PAPER DUE DATE AND TIME: White Papers are due no later than 21 AUGUST 2017, 3:00 pm EST by postal mail or hand delivery only to: Mr.

Scott Beeler AFRL/RQKMS, Bldg. 45, 2130 8th St., Wright-Patterson AFB, OH 45433.

Offerors must refer to BAA FA8650-16-S-5001, and its amendments which must be read in conjunction with this Call for White Papers. This Call for White Papers will be governed by the “TWO-STEP” process described in Section IV of the open-ended BAA FA8650-16-S-5001.

PROPOSAL DUE DATE AND TIME: To be provided in the Requests for Proposals sent to offerors that submit White Papers considered to meet the needs of the Air Force

1. Statement of Objectives:

1.0 PROGRAM GOAL

1.1 The goal of this program is to execute and maintain a strong, sustainability- driven Research Development Test and Evaluation (RDT&E) Program for the Air Force (AF).

1.2 All program efforts shall be performed through the use of individual contracts. Associated CDRL Data Items, see paragraph 2 Deliverable Items.

2.0 SCOPE

2.1 This program shall research, assess, develop, perform physical, mechanical, chemical, and environmental testing, evaluate, demonstrate, and transition new alternative energy and energy efficiency technologies to provide increased capabilities and benefits to AF installations, equipment, and aircraft. These capabilities and benefits may include (but are not limited to) fuel efficiency improvements, holistic energy resiliency improvements, and reduction in the logistical burden for expeditionary forces. Ideally, the solutions will maximize the benefit of a combination of the following:

2.1.1 Increased energy resiliency/reliability: energy resilience is defined as the adaptive capacity to maintain critical mission functions even during unexpected disruptions.

2.1.2 Increased cost-effectiveness: evaluate the trade-offs between lowest price and other priorities such as sustainability and resilience.

2.1.3 Increased environmental sustainability.

2.2 This program shall focus on the demonstration and evaluation of the capabilities of Technology Readiness Level 6 technologies. It will plan for the future transition/implementation of the technologies developed or investigated under this contract to the USAF. For this call, TRL definitions for hardware and software are from Section 2.5 of the Department of Defense Technology Readiness Assessment Guidance publication that can be found at:

http://www.acq.osd.mil/chieftechnologist/publications/docs/TRA2011.pdf

2.3 All candidates must be capable of conducting a demonstration and evaluation that does not exceed 24 months from the time of award.

3.0 TECHNICAL

3.1 BACKGROUND

The core technical effort of this program shall be conducted through the performance of individual contracts.

3.1.1 Individual contracts will be issued though a 2-step evaluation of responses to the BAA calls.

3.1.2 Offeror may submit white papers for 1 or more topics. Each white paper shall be confined to individual topics.

3.1.3 Government Furnished Property (GFP) is not anticipated. Any GFP shall be accounted for and maintained by the contractor.

3.1.4 Necessary special purpose materials, equipment, and associated hardware/software neither Contractor owned nor available as GFP or base support shall be procured and maintained by the contractor upon Government approval.

3.2 OBJECTIVES

3.2.1 Data generated under this program shall be

transitioned/transferred, as applicable, to pertinent organizations. The contractor shall collect and report contract results in a responsible manner to assure customer confidence in the data.

3.2.2 This program shall support the following key technical areas:

http://www.acq.osd.mil/chieftechnologist/publications/docs/TRA2011.pdf

3.2.2.1 Advanced technology demonstrations focusing on providing resilient, reliable, and secure power for Air Force installations.

The Air Force uses a risk management approach to evaluate the resiliency, reliability, and security of energy. Example technologies include distributed power generation, energy storage, smart controller technologies for autonomous load switching, data center improvements, microgrid development, forecasting and other microgrid optimization technologies, and the incorporation of various technologies into an integrated solution.

3.2.2.2 Advanced technology demonstrations for manned aviation systems and Unmanned Aerial Systems (UAS) which focus on fuel efficiency, fuel flexibility, modeling and simulation for efficiency improvements, and drag reduction while potentially increasing offensive and defensive capability. Fuel efficiencies can be obtained in a number of ways, examples include but are not limited to: lightweight materials substitution for non-structural components, changes in Training or Tactics, Techniques and Procedures (TTP), advanced battery/fuel cell improvements, component reconfiguration, propulsion system improvements, software modifications, and external aerodynamic modifications.

3.2.2.3 Advanced ground support energy technology

demonstrations for aerospace ground equipment and vehicles that increase energy efficiencies and capabilities, reduce energy costs, or minimize logistics burdens to enhance operational agility.

3.2.2.4 Advanced expeditionary energy technology demonstrations supporting operations in deployed environments that minimize the logistical burden associated with the shipment of equipment and fuel. Industry continues to advance the development of energy technologies for civilian applications as part of either disaster response or for geographically remote self-sufficiency.

These mature technologies could be modified to meet the Air Force’s expeditionary requirements. Example technologies include alternative energy generation with a high power-to-weight ratio, intrinsically safe high-energy density energy storage, efficient gray-water and black-water treatment systems, and other technologies supporting a net-zero deployed base

3.2.3 Specific issues of interest within these key technical areas include:

3.2.3.1 Energy Technology Validation and Risk Reduction

3.2.3.1.1 Demonstrate and validate new or underutilized

Energy Conservation Measures (ECMs) or sustainable Distributed Energy Resources (DERs) that would not otherwise be included in Energy Savings Performance Contracts (ESPCs) or Power Purchase Agreements (PPAs).

Demonstrations should target the technology performance validation, cost validation, and risk reduction required for inclusion in ESPCs or PPAs. Example technologies of interest include scalable renewable energy generation, building envelope improvements, and Heating, Ventilation, and Air Conditioning improvements.

3.2.3.2 Open-Source Microgrid Controllers

3.2.3.2.1 Demonstrate and validate open-source microgrid

controllers focused on scalability and replicability.

Technologies should focus on and account for cost-effectiveness on a MWh basis, renewable penetration on a percentage basis, power quality, resiliency during utility outages, and cybersecurity. Example technologies of interest include modular systems that emphasize compatibility and minimize required operator interaction.

3.2.3.3 Aerodynamic Drag Improvements to Achieve Fuel Savings

3.2.3.3.1 Demonstrate and evaluate aerodynamic

improvements in military aircraft through application of cost-effective drag reducing concepts and devices with the goal of reducing airframe drag to realize 5% or more in fuel savings for aircraft that are the largest USAF fuel consumers.

3.2.3.4 Turbine Blade Refurbishment Techniques to Achieve

Increased Fuel Efficiencies

3.2.3.4.1 Demonstrate and evaluate aerodynamic

improvements in military aircraft through the use of innovative, cost-effective turbine engine blade refurbishment techniques. Techniques could include protective coatings, the use of advanced scanners to determine blade dimensional data, and advanced machining techniques with the goal to realize 5% or more in fuel savings for aircraft that are the largest USAF fuel consumers.

3.2.3.5 Passive Aircraft Operational Energy (OE) Flight Parameters Measurement Technology

3.2.3.5.1 Demonstrate and validate non-invasive methods to

passively capture OE related flight data (engine N1, N2, EGT, EPR, airspeed, altitude, takeoff fuel, landing fuel, onload, offload etc.) focused on enhancing analysis for the purpose of identifying flight process and profile improvements. Technology should be stand alone, not requiring connection to existing aircraft systems and not to interfere with aircrew activity.

3.2.3.6 Energy Efficient Deployable Flightline Light Carts

3.2.3.6.1 This program shall demonstrate and evaluate an

aircraft deployable, 4-wheel flightline light cart that optimizes efficiency in worldwide military environments with operational battlefield fuel and renewable energy while also reducing maintenance and sustainment costs. Light cart will be used in multiple flightline applications such as: elevated above-wing engine maintenance on large transport aircraft and localized ground-level flightline illumination.

Demonstration unit should have lumen rating that is equal to or better than similar Air Force systems.

3.2.3.7 Advanced Variable Speed Military Generator

3.2.3.7.1 This program shall demonstrate and evaluate a

variable speed military size generator (e.g. 60kW) optimizing operational fuel/energy efficiency. Test systems shall track loads and automatically adjust engine speed to accommodate 10% to 100% of rated capacity while maintaining frequency output. System design shall be compatible with world-wide climatic operational scenarios and applicable transportation methods and regulations.

Preference will be given to directly transferrable and scalable technologies and/or designs that can address energy optimization in all common military generator sizes.

4.0 MANAGEMENT OBJECTIVES

4.1 The primary management/administrative objective of this program is to allow the contractor maximum flexibility to innovatively manage program cost, schedule, performance, risks, subcontractors, and data requirements and to maintain clear government visibility into program cost, schedule, technical performance, and risk.

4.2 The contractor shall conduct biweekly meetings to keep the Air Force Program Manager (PM) informed regarding program status, manpower issues, and budget status. The budget shall be broken down into individual tasks performed during the monthly reporting period.

(Reference Contract Data Requirements List (CDRL) Data Items

A001, A002, A003, A004 (ONLY IF OVER $4M), A005, A006,

A007, A008, A009, A010, A011, A012, A013, A014, A015, and A016)

5.0 SECURITY OBJECTIVES

5.1 On-site Tasks. All contractors shall participate in all activities associated with the disciplines of the organization’s Security Program (Information Security, Industrial Security, Operations Security (OPSEC), Personnel Security and Antiterrorism programs) following appropriate measures in each discipline during the performance of this contract. This requirement is part of an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information.

5.2 Off-site Tasks. Contractor shall participate in the organization’s

Operations Security (OPSEC) program, following appropriate OPSEC measures during the performance of this contract. OPSEC requirements are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information.

6.0 PROGRAM PROTECTION PLAN

6.1 Any additional designated critical program information (CPI) with a potential requirement for a program protection plan (PPP) generated as part of this contract will be addressed as needed.

2. Deliverable Items: The anticipated deliverable items may include the following Data Items:

A001 Scientific & Technical Reports (Final Report) DI-MISC-80711A/T A002 Funds & Man-Hour Expenditure Report DI-FNCL-80331A/T A003 Scientific & Technical Reports (Spend Plan) DI-MISC-80711A/T A004 Contract Funds Status Report DI-MGMT-81468/T A005 Status Report DI-MGMT-80368A/T A006 Presentation Material DI-ADMN-81373/T A007 Test Plan (Demonstration Test Plan) DI-NDTI-80566A/T A008 Test Plan (Flight & Taxi Test Plan) DI-NDTI-80566A/T A009 Scientific & Technical Reports (Ops Manual) DI-MISC-80711A/T A010 Computer Software Product (Source Code) DI-IPSC-81488/T A011 Software User Manual DI-IPSC-81443A/T A012 Interface Design Description DI-IPSC-81436A/T A013 Software Test Report DI-IPSC-81440A/T A014 Govt. Prop. Physical Inv. Count or Custodial Bal. Rpt. DI-MGMT-80441A/T A015 Material & Processing Digital Data Package (MPDDP) DI-MISC-82020/T

A016 Scientific & Technical Reports (Data Management Plan) DI-MISC-80711A/T

3. Schedule:

a. Overall Effort: The period of performance for the technical effort is anticipated to be twenty-four (24) months plus an additional three (3) months for preparation, review, revision, and submittal of the approved final technical report. The Government reserves the right to award shorter or longer efforts.

b. Data Items: See Section 2 above.

c. Software: All software deliverables should be clearly identified in the offeror’s white paper/proposal. Unlimited rights are desired for software to be delivered.

d. Hardware: All hardware deliverables should be clearly identified in the offeror’s white paper/proposal.

4. Other Requirements:

a. Program Security Classification: Unclassified

b. TEMPEST Requirements: This section will be governed by the statement listed in Section I (5) (c) of BAA FA8650-16-S-5001.

c. OPSEC:

On-site Tasks. All contractors shall participate in all activities associated with the disciplines of the organization’s Security Program (Information Security, Industrial Security, Operations Security (OPSEC), Personnel Security and Antiterrorism programs) following appropriate measures in each discipline during the performance of this contract. This requirement is part of an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information.

Off-site Tasks. Contractor shall participate in the organization’s Operations Security (OPSEC) program, following appropriate OPSEC measures during the performance of this contract. OPSEC requirements are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information.

d. Export Control: This section will be governed by the statement listed in Section I.5.e of BAA FA8650-16-S-5001.

e. Export Controlled Items: This section will be governed by the statement listed in Section I.5.f of BAA FA8650-16-S-5001.

f. Size Status: For purposes of this acquisition, the size standard is 1,500 employees, NAICS code 541712. This is an unrestricted acquisition; small and large businesses are encouraged to submit White Papers.

5. Other Information:

a. Government Furnished Property (GFP): Government Furnished Property (GFP) is not anticipated, but will be determined on a contract-by-contract basis.

b. Base Support / Network Access: Base Support & Network Access are not anticipated, but will be determined on a contract-by-contract basis.

c. Data Rights Desired: This section will be governed by the statement listed in Section I.6.d of BAA FA8650-16-S-5001.

Additionally, the Contractor may be required to obtain licenses that comply with the following terms and conditions, based on the Government’s needs:

1. The license shall not disclaim all warranties through use of an “as is” provision.

2. The license shall neither restrict the Government from using the product at various sites nor limit use of the product by various Government agencies or third parties performing work on behalf of the Air Force under the “Advanced Power Technology Office – Energy Innovation”. In performance of the “Advanced Power Technology Office – Energy Innovation”, Government personnel as well as Government contractors may use the software.

3. The license shall not limit the Government’s use of the software at other Government and Government contractor sites. The license shall authorize the Government to use the software at the following sites:

’To Be Determined on Individual Awards’.

4. The license shall not require automatic updates or give Licensor the authority to unilaterally replace the software.

5. The Licensee shall not be restricted from copying or embedding elements of accessible code into other applications (e.g., nesting code, derivative works).

The Contractor may obtain agreement from the Licensor to insert the clause below to its respective software licenses intended to be transferred to the Government:

“In the event that any of the provisions of the Software License are determined to be inconsistent with Federal law and/or do not otherwise satisfy the Government's needs, the parties to the Software License hereby agree that such provisions shall be null and void as they pertain to the Government. Specifically, the following sections are hereby deleted from the Software License, and/or amended as indicated below:

‘’To Be Determined on Individual Awards’.

If the Licensor will not agree to the terms and conditions cited herein and/or as contained in DFARS 227.72, the Contractor shall retain the current license on behalf of and for the benefit of the US Government if permissible under its license and such use will not subject the Government to the terms of the license.

The Contractor shall provide documentation to clearly correlate or map software license(s) to:

a) Contract Line Item Numbers (CLINS);

b) Contract Deliverables (CDRLS);

c) Paragraphs in the statement of work (SOW); and

d) Portions of any functional block diagrams and/or system architecture diagrams, so that it can be readily determined where certain commercial software corresponding to certain software license agreement(s) are physically located on the system to be delivered under the contract.

6. Points of Contact:

Address technical questions to:

Mr. Eric Griesenbrock 2179 12th Street Wright-Patterson AFB, OH 45433-7913 afrl.rxsc.apto@us.af.mil

Address contracting questions to:

M. Scott Beeler 2130 8th Street, Bldg. 45 Wright-Patterson AFB, OH 45433

(937) 713-9842 matthew.beeler@us.af.mil

7. Anticipated Funding for Call 002 is $10M (shared). Awards are anticipated to range from $1M to $8M.

This funding profile is an estimate only and not a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that due to unanticipated budget fluctuations funding in any or all areas may change with little or no notice.

8. White Paper Submission Information: This Call for White Papers will be governed by the “TWO-STEP” process described in Section IV.2.a thru g of the open-ended BAA FA8650-16-S-5001. White Papers shall be prepared and submitted in accordance with the instructions set forth in Section IV of the open-ended BAA FA8650-16-S-5001, which must be read in conjunction with this call for White Papers.

General: The FIRST STEP requests an unclassified white paper and a rough order of magnitude (ROM) cost. The white paper shall include a discussion of the nature, scope, TRL and MRL (Manufacturing Research Level) of the research and the offeror’s proposed technical approach. Also, include which topic area the white paper addresses, a clearly defined problem statement that the research will address, the technical performance objectives of the research, and the expected AF costs and benefits of implementing the results of the research. The Government will evaluate the white papers in accordance with the FIRST STEP evaluation criteria, set forth in Section V below. Based on this evaluation, the Government will determine which of them have the potential to best meet the Air Force’s needs.

Offerors will be notified of the disposition of their white paper. It is anticipated that Government review of the white papers submitted will take 45 working days.

Those offerors submitting white papers assessed as meeting Air Force needs will be mailto:afrl.rxsc.apto@us.af.mil mailto:matthew.beeler@us.af.mil asked to submit a technical and cost proposal. Those offerors not requested to submit a technical and cost proposal will be notified. An offeror submitting a proposal without first submitting a white paper will not be eligible for an award.

The cost of preparing white papers in response to this Solicitation 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.

Page Limitation: The White Paper shall be limited to 5 pages, prepared and submitted in Word format. Font shall be standard 10-point business font Arial.

Character spacing must be “normal,” not condensed in any manner. 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. All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein.

Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items. Pages shall be numbered starting with the cover page being Page 1. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc. The Government will not consider pages in excess of these limitations. Offerors should submit 1 original and 3 hard copies of the White Paper via mail to the Contracting POC, identified in the Overview Information. One (1) CD with the WORD version of your White Paper must be submitted with the hard copies of the White Paper, and must match the hard copy.

9. White Paper Review Information: The evaluation criteria applicable to the “TWO-STEP” process described in Section V of the open-ended BAA FA8650-16-S- 5001 will apply to this call for white papers.

For complete information regarding this call for white papers, refer to the initial opened-ended BAA FA8650-16-S-5001. It contains information applicable to all calls for white papers issued under the BAA. The initial open-ended BAA provides information on the overall program, white papers requirements, white papers submission, white papers review, etc.

10. Funding Restrictions: Not Anticipated.

11. Cost Sharing or Matching: Not anticipated.

12. Foreign Participation: Foreign participation eligibility will be determined for each award. However, if foreign nationals are proposed, submissions may be disqualified based on ITAR applicability.

13. Technical/Management Proposal Submission Information: If a contractor’s white paper is selected for proposal, the Technical/Management proposal requirements will be specified in the Request for Proposal (RFP) letter.

14. Associate Contractor Agreements (ACA): If a contractor’s white paper proposes an ACA, and the white paper is selected for proposal, ACA requirements will be specified in the Request for Proposal (RFP) letter.

15. Security Requirements - Information Regarding Non-US Citizens Assigned to this Project.

(a) Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology (IT) networks in connection with the work on this contract must be U.S. citizens. For the purpose of base and network access, possession of a permanent resident card (“Green Card”) does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

(b) For purposes of paragraph (a) above, if an IT network/system does not require AFRL to endorse a contractor’s application to said network/system in order to gain access, the organization operating the IT network/system is responsible for controlling access to its system. If an IT network/system requires an U.S. Government sponsor to endorse the application in order for access to the IT network/system; AFRL will only endorse the following types of applications; consistent with the requirements above:

(1) Contractor employees who are U.S. citizens performing work under this contract.

(2) Contractor employees who are non-U.S. citizens and who have been granted a waiver.

Any additional access restrictions established by the IT network/system owner apply.

16. It is recommended that all offerors review the White Paper / Proposal Reminders located in Section VII.7 of BAA FA8650-16-S-5001.