BAACALL0013final.doc

Attached REPS&CERTS

BROAD AGENCY ANNOUNCEMENT

BAA-VS-07-03

Air Force Research Laboratory/Space Vehicles Directorate

PROPOSAL CALL ANNOUNCEMENT (CALL) 0013

BROAD AGENCY ANNOUNCEMENT TITLE: Space Components Technology Open 5 Year Broad Agency Announcement

BROAD AGENCY ANNOUNCEMENT NUMBER: BAA-VS-07-03

PROPOSAL CALL ANNOUCEMENT (CALL) TITLE: Topic Area #3, entitled Advanced Space Power Technologies, CALL #0013 entitled: Photovoltaic Cells and Modules for Near Space and Space Applications

PROPOSAL CALL ANNOUNCEMENT (CALL) NUMBER: 0013

TECHNICAL POINT OF CONTACT: The technical point of contact for this CALL is Technical point of contract for Subparagraph C of Topic 3:

Alex Howard, AFRL/RVSV, (505) 853-1889, Fax NONE, Email: alex.howard@kirtland.af.mil CONTRACTING POINTS OF CONTACT: The contracting points of contact for this CALL are:

Contracting Specialist/ Contracting Officer:

Sally Walton, Det 8 AFRL/RVKV, Kirtland AFB, NM, Phone 505-846-7201, Fax NONE, Email: sally.walton@kirtland.af.mil or Jean Barnes, Det 8 AFRL/RVKV, Kirtland AFB, NM, Phone 505-846-4695, Fax NONE, Email: jean.barnes@kirtland.af.mil

REQUIREMENT DESCRIPTION:

The Air Force Research Laboratory is soliciting proposals in Space Components Technology under subparagraph C of the Space Components Technology Area, TOPIC 3, Advanced Space Power Technologies of the Broad Agency Announcement VS-07-03 posted on 02 November 2006. See the following for detailed information;

Subparagraph C of Topic 3, Advanced Space Powers Technologies.

AFRL is soliciting proposals in subparagraph C, Topic 3, Advance Space Power Technologies, specifically for Photovoltaic Cells and Photovoltaic Modules for Near Space and Space Solar Power Applications for the development of low-cost (approximately $100/W), lightweight, flexible, and manufacturable thin-film (e.g. CIGS, a-SI, -Si) solar cells. The development effort should be a phased approach with options to achieve a technology readiness level (TRL) of 6 (definitions of TRL should be agreed upon with AFRL) and conclude with practical cell efficiencies of approximately 20% and capability to produce modules with an efficiency of 15% or greater. Additionally, the effort should conclude with the capability to produce at least 1 MegaWatt per year of modules at the specified efficiency. The cells and modules should be designed to operate in a space based Air Mass Zero (AM0) operational environment and should address ultraviolet, electron and proton tolerance, efficient stowage, moisture permeability, emissivity, mechanical and thermal stability, and radiation resistant capability for adequate end-of-life performance.

Base: Design Feasibility: Demonstrate materials grown that can be fabricated to produce a solar cell, optimized to the AM0 spectrum, at efficiencies of 20% or greater with reproducibility. A clear path to a manufacturable, 20% or greater solar cell must be demonstrated.

Option 1: Demonstrate a large area, >20cm2, solar cell with efficiencies produced in the base effort. Based on the results from the base effort, design and develop module level architecture, cell interconnect architecture, and encapsulation methodology. Develop the solar cell form factors and electrical configuration, and the coating and/or encapsulation methods for modules. Establish engineering confidence tests. Evaluate test performance data and utilize this information to determine final design architectures.

Option 2: Demonstrate a photovoltaic module with efficiency of >15%. Develop the solar cell form factors and electrical configuration, and the coating and/or encapsulation methods for modules.

ANTICIPATED FUNDING (Topic 3, Subparagraph C): Governments Cost-Share of anticipated funding for this CALL (not per contract or award) is: FY 08-09: $875 Thousand dollars, FY10-FY11: $500 Thousand dollars per FY. This funding profile is an estimate only and will not be a contractual obligation for funding. All funding is subject to change due to government discretion and availability.

PERIOD OF PERFORMANCE (Topic 3, Subparagraph C): The anticipated period of performance for individual awards resulting from this CALL is between 12 to 24 months in duration and 12 months per option. The period of performance is to be proposed in the format “includes XX months for the technical effort and 3 months for Final Report preparation.”

PROPOSAL DUE DATE AND TIME: The due date for proposals submitted in response to this CALL is no later than 12:00 p.m. MDT on 21 APRIL 2008. Proposals for any other technology area identified in the baseline BAA will not be accepted at this time unless a CALL for proposals in that specific area is open. Proposals received after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3).

CALL AMENDMENTS: Offerors should monitor FedBizOps/EPS http://www.fbo.gov and/or Grants.gov/FIND http://www.grants.gov for any additional notices to this CALL that may permit extensions to the proposal submission date or otherwise modify this announcement.

ANTICIPATED TYPE OF CONTRACTS/INSTRUMENTS: The Air Force reserves the right to award the instrument best suited to the nature of research proposed. Accordingly, the Government may award any appropriate contract type under the Federal Acquisition Regulation or Other Transaction (OT) for Prototype, grant, cooperative agreement, or OT for Research. Specific instructions for assistance awards are in paragraph 7 of the BAA. It is anticipated that awards under this BAA will generally be cost plus fixed fee, completion form contracts, which require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.

ANTICIPATED NUMBER OF AWARDS: The Air Force anticipates possibly awarding one or more contracts and or DoDGARS type instruments. However, the Air Force reserves the right to make multiple awards or no awards pursuant to this CALL.

ANTICIPATED AWARD DATE: NLT 02 June 2008 INTENT TO PROPOSE: Potential offerors are requested to advise the contracting point of contact (by e-mail) if they intend to submit a proposal in response to this CALL. Such notification is merely a courtesy and is not a commitment by the offeror to submit a proposal.

DELIVERABLES ITEMS:

The intent of this project is described in the Requirement Description above. Offerors should propose data, hardware, and/or software deliverables consistent with tracking progress, verifying performance, and otherwise establishing the objectives of the project. Monthly technical and financial Status Reports and a Final Technical Report in accordance with PRS Pamphlet 61-201, Preparation of Final Report, are required data items.

OTHER RELEVANT INFORMATION:

1. Program security classification for this call is UNCLASSIFIED; however classified processing may be required.

2. ITAR/Export Control: Research areas may involve technology that is subject to U.S. Export Control Laws. Therefore, only offerors who are certified by the Defense Logistics Information Service (DLIS) may submit proposals. For questions, contact DLIS on-line at http://www.dlis.dla.mil/jcp or at DLIS, US/Canada Joint Certification Center, Federal Center, 74 North Washington, Battle Creek MI 49017-4312, (800) 352-3572. It is envisioned that the developed item may trigger ITAR and Export Control restrictions. Offerors should explain how ITAR and Export Control restrictions will be met in the context of their development, manufacturing, and marketing strategy. Status Reports and the Final Technical Report are assumed to be under ITAR restrictions (DD Form 2345 required).

3. Government furnished property, equipment, or facilities needed for this requirement should be specified in the proposal.

4. Aerospace Corporation is prohibited from submitting a proposal.

5. Foreign owned firms are advised to contact the Contracting Officer or the Program Manager to determine if there are no restrictions to receiving awards.

6. Other: Specialized information or requirements which are believed to be pertinent to the requirement shall be provided by the offeror in written form and incorporated into the proposal.

7. Item Identification and Valuation: Any contract award resulting from this Call may include the clause at DFARS 252.211-7003, Item Identification and Valuation, (Apr 2005). See baseline BAA for additional details.

APPLICABILITY OF BASELINE BAA: All requirements of BAA-VS-07-03 apply unless specifically amended and addressed in this CALL. For complete information regarding BAA-VS-07-03, refer to the initial opened-ended BAA as amended. It contains information applicable to all CALLS issued under the BAA and provides information on the overall program, proposal preparation and submission requirements, proposal review and evaluation criteria, award administration, agency contacts, etc. Direct questions to the points of contact identified above.

NOTICE FOR PROPOSAL INSTRUCTIONS: The website referenced in the Baseline BAA http://www.vs.afrl.af.mil/PK has moved. In order to access contracting information the new website is http://www.kirtland.af.mil/library/factsheets/factsheet.asp?id=8124. Information for Cost Proposal Instructions, Broad Agency Announcements, Wide Area Workflow and other Additional Information is located here.

2nd NOTICE FOR PROPOSAL INSTRUCTIONS: Until notified otherwise, the attached REPS&CERTS dated 14 JAN 2008, are attached and will be required with all proposal submissions.

AIR FORCE RESEARCH LABORATORY

DIRECTED ENERGY AND SPACE VEHICLES DIRECTORATES

Broad Agency Announcement Number _____________ (Specify Call number if applicable and revise if for other than BAA)

REPRESENTATIONS AND CERTIFICATIONS

(Current as of 14 Jan 08) I. NOTICE: The following solicitation provisions pertinent to this section are hereby incorporated in full text:

A. FEDERAL ACQUISITION REGULATION SOLICITATION PROVISIONS IN FULL TEXT

52.204-08 ANNUAL REPRESENTATIONS AND CERTIFICATIONS (JAN 2006)

(a)

(1) The North American Industry Classification System (NAICS) code for this acquisition is 541712.

(2) The small business size standard is 1,000 employees for Space Vehicles & Guided Missiles or 500 employees for other research and development.

(3) The small business size standard for a concern which submits an offer in its own name, other than on a construction or service contract, but which proposes to furnish a product which it did not itself manufacture, is 500 employees.

(b)

(1) If the clause at 52.204-7, Central Contractor Registration, is included in this solicitation, paragraph (c) of this provision applies.

(2) If the clause at 52.204-7 is not included in this solicitation, and the offeror is currently registered in CCR, and has completed the ORCA electronically, the offeror may choose to use paragraph (c) of this provision instead of completing the corresponding individual representations and certification in the solicitation. The offeror shall indicate which option applies by checking one of the following boxes:

[ ] (i) Paragraph (c) applies.

[ ] (ii) Paragraph (c) does not apply and the offeror has completed the individual representations and certifications in the solicitation.

(c) The offeror has completed the annual representations and certifications electronically via the Online Representations and Certifications Application (ORCA) website at http://orca.bpn.gov. After reviewing the ORCA database information, the offeror verifies by submission of the offer that the representations and certifications currently posted electronically have been entered or updated within the last 12 months, are current, accurate, complete, and applicable to this solicitation (including the business size standard applicable to the NAICS code referenced for this solicitation), as of the date of this offer and are incorporated in this offer by reference (see FAR 4.1201); except for the changes identified below [offeror to insert changes, identifying change by clause number, title, date]. These amended representation(s) and/or certification(s) are also incorporated in this offer and are current, accurate, and complete as of the date of this offer.

Any changes provided by the offeror are applicable to this solicitation only, and do not result in an update to the representations and certifications posted on ORCA.

B. DEFENSE FAR SUPP SOLICITATION PROVISIONS IN FULL TEXT

252.227-7017 IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR DISCLOSURE RESTRICTIONS (JUN 1995)

(a) The terms used in this provision are defined in following clause or clauses contained in this solicitation--

(1) If a successful offeror will be required to deliver technical data, the Rights in Technical Data--Noncommercial Items clause, or, if this solicitation contemplates a contract under the Small Business Innovative Research Program, the Rights in Noncommercial Technical Data and Computer Software--Small Business Innovative Research (SBIR) Program clause.

(2) If a successful offeror will not be required to deliver technical data, the Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation clause, or, if this solicitation contemplates a contract under the Small Business Innovative Research Program, the Rights in Noncommercial Technical Data and Computer Software--Small Business Innovative Research (SBIR) Program clause.

(b) The identification and assertion requirements in this provision apply only to technical data, including computer software documentation, or computer software to be delivered with other than unlimited rights. For contracts to be awarded under the Small Business Innovative Research Program, the notification and identification requirements do not apply to technical data or computer software that will be generated under the resulting contract. Notification and identification is not required for restrictions based solely on copyright.

(c) Offers submitted in response to this solicitation shall identify, to the extent known at the time an offer is submitted to the Government, the technical data or computer software that the Offeror, its subcontractors or suppliers, or potential subcontractors or suppliers, assert should be furnished to the Government with restrictions on use, release, or disclosure.

(d) The Offeror's assertions, including the assertions of its subcontractors or suppliers or potential subcontractors or suppliers shall be submitted as an attachment to its offer in the following format, dated and signed by an official authorized to contractually obligate the Offeror:

Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data or Computer Software.

The Offeror asserts for itself, or the persons identified below, that the Government's rights to use, release, or disclose the following technical data or computer software should be restricted:

Technical Data or

Computer Software

Asserted

Name of Person to be Furnished

Basis for

Rights

Asserting

With Restrictions* Assertion** Category*** Restrictions****

*For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process. For computer software or computer software documentation identify the software or documentation.

**Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain. The Government's rights in computer software documentation generally may not be restricted. For computer software, development refers to the software. Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished at private expense, or for computer software documentation, enter the specific basis for asserting restrictions.

***Enter asserted rights category (e.g., government purpose license rights from a prior contract, rights in SBIR data generated under another contract, limited, restricted, or government purpose rights under this or a prior contract, or specially negotiated licenses).

****Corporation, individual, or other person, as appropriate.

*****Enter "none" when all data or software will be submitted without restrictions.

Date

Printed Name and Title

Signature

(End of identification and assertion)

(e) An offeror's failure to submit, complete, or sign the notification and identification required by paragraph (d) of this provision with its offer may render the offer ineligible for award.

(f) If the Offeror is awarded a contract, the assertions identified in paragraph (d) of this provision shall be listed in an attachment to that contract. Upon request by the Contracting Officer, the Offeror shall provide sufficient information to enable the Contracting Officer to evaluate any listed assertion.

252.227-7028 TECHNICAL DATA OR COMPUTER SOFTWARE PREVIOUSLY DELIVERED TO THE GOVERNMENT (JAN 2006)

The Offeror shall attach to its offer an identification of all documents or other media incorporating technical data or computer software it intends to deliver under this contract with other than unlimited rights that are identical or substantially similar to documents or other media that the Offeror has produced for, delivered to, or is obligated to deliver to the government under any contract or subcontract. The attachment shall identify--

(a) The contract number under which the data or software were produced;

(b) The contract number under which, and the name and address of the organization to whom, the data or software were most recently delivered or will be delivered; and

(c) Any limitations on the Government's rights to use or disclose the data or software, including, when applicable, identification of the earliest date the limitations expire. (End of Provision)

C. OTHER SOLICITATION PROVISIONS IN FULL TEXT

K003 CERTIFICATE OF SIGNATORY AUTHORITY (AUG 2005)

I, __________________________________ (Name), certify that I am the ____________________________________________ (Position Title) of the Corporation named as Contractor herein, that _____________________________________ (Name), who signed this contract on behalf of the Contractor, was then _____________________________ (Position Title) of said Corporation; that said contract was duly signed for and on behalf of the said Corporation by authority of its governing body aqnd is within the scope of its corporate powers.

(SEAL)

_____________________________________ (Signature)

____________________________________ (Typed or printed Name and Title of Signatory)

NOTE: The name and title of the person signing the contract shall be typed or printed below the signature. If the contract is signed in a capacity other than individual, partner, owner or a president, vice-president, secretary or treasurer of a company or corporation, satisfactory evidence of the authority of the person signing to bind the principal must be furnished.

PRS K002 ADMINISTRATIVE ACCESS TO PROPRIETARY INFORMATION (OCT 2007)

(a) The Air Force Research Laboratory's Directed Energy (RD) and Space Vehicles (RV) Directorates have contracted for various business and staff support services, some of which require contractors (e.g., CC&G, LLC) to obtain administrative access to proprietary information submitted by other contractors. Administrative access is defined as "handling or having physical control over information for the sole purpose of accomplishing the administrative functions specified in this contract or order, which do not require the review, reading, or comprehension of the content of the information on the part of non-technical professionals assigned to accomplish the specified administrative tasks."

(b) The required administrative access will be granted to non-technical professionals. Examples of the administrative tasks performed include:

(1) Assembling and organizaing information for R&D case files;

(2) Accessing library files for use by government personnel in the RD and RV Directorates; and

(3) Handling and administration of Small Business Innovation Research proposals, contracts, contract funding and queries.

(c) Offerors shall either complete paragraph (d) below or provide written objection to administrative access. Any objection to administrative access:

(1) Shall be provided in writing to the contracting officer within 10 days of RFP (or PRDA, BAA, etc., as appropriate) issuance; and

(2) Shall include a detailed statement of the basis for the objection.

(d) I consent to administrative access, as defined above, by RD and RV business and staff support services contractors to any proprietary information submitted under this solicitation or delivered under any resulting contract.

___Signature

___Name of Authorized Company Official

PAGE