LRETD DRAFT BAA 24 Jun 10.pdf

Distribution A: Approved for public release, distribution unlimited Public Affairs Clearance number: 10260

ROAD AGENCY ANNOUNCEMENT

FOR THE AIR FORCE RESEARCH LABORATORY

THIS IS A DRAFT BAA. PROPOSALS ARE NOT

BEING REQUESTED AT THIS TIME.

SPACE AND MISSILE DIVISION

PROPULSION DIRECTORATE

RESEARCH AND DEVELOPMENT

BROAD AGENCY ANNOUNCEMENT

THIS IS A DRAFT BAA. PROPOSALS ARE NOT

BEING REQUESTED AT THIS TIME.

BAA-10-02-PKTA

24 June 2010

Issuing Office: Air Force Flight Test Center, Directorate of Contracting

Edwards AFB, CA

Table of Contents

I. PROGRAM DESCRIPTION

I A. TOPIC 1 – Green Advanced Spacecraft Propulsion (Green ASP)

1. Statement of Objective/Needs:

2. Scope:

3. Background:

4. Technical Requirements/Program Plan:

5. Deliverable Items:

6. Schedule:

7. Other Requirements:

8. Other Information:

I B. TOPIC 2 – Health Assessment and Recognition Tools (HART)

1. Statement of Objective/Needs:

1.1. Area 1: Turbopump Assembly (TPA) Application:

1.2. Area 2: Thrust Chamber Assembly (TCA) Application:

2. Scope:

3. Background:

4. Technical Requirements/Program Plan:

5. Deliverables

6. Schedule:

7. Other Requirements:

8. Other Information:

I C. TOPIC 3 – Propulsion Unit for CubeSats (PUC)

1. Statement of Objective/Needs:

2. Scope:

3. Background:

4. Technical Requirements/Program Plan:

5. Deliverable Items:

6. Schedule:

7. Other Requirements:

8. Other Information:

II. AWARD INFORMATION:

II A. TOPIC 1 – Green Advanced Spacecraft Propulsion (Green ASP)

1. Anticipated Funding:

2. Anticipated Number of Awards:

3. Anticipated Award Date:

II B. TOPIC 2 – Health Assessment and Recognition Tools (HART)

1. Anticipated Funding:

2. Anticipated Number of Awards:

3. Anticipated Award Date:

II C. TOPIC 3 – Propulsion Unit for CubeSats (PUC)

1. Anticipated Funding:

2. Anticipated Number of Awards:

3. Anticipated Award Date:

III. ELIGIBILITY INFORMATION:

IV. PROPOSAL/APPLICATION AND SUBMISSION INFORMATION:

V. PROPOSAL/APPLICATION REVIEW INFORMATION:

V A. TOPIC 1 – Green Advanced Spacecraft Propulsion (Green ASP)

V B. TOPIC 2 – Health Assessment and Recognition Tools (HART)

V C. TOPIC 3 – Propulsion Unit for CubeSats (PUC)

VI. AWARD ADMINISTRATION INFORMATION:

VII. AGENCY CONTACTS:

1. Technical Point of Contact:

2. Contracting Officer:

3. Contract Specialists:

VIII. OTHER INFORMATION:

Table of Tables

Table 1 - TOPIC 1 Sample Contract Requirements List (CDRL)

Table 2 - TOPIC 2 Sample Contract Requirements List (CDRL)

Table 3 - TOPIC 3 Sample Contract Requirements List (CDRL)

Table 4 - TOPIC 1 Planned Funding Profile

Table 5 - TOPIC 2 Planned Funding Profile

Table 6 - TOPIC 3 Planned Funding Profile

Table 7 - Sample Labor Mix Schedule (Hours)

Table 8 - Sample Cost Summary Format

BROAD AGENCY ANNOUNCEMENT

8 June 2010

NAICS CODE: 541712

FEDERAL AGENCY NAME: Air Force Research Laboratory, Propulsion Directorate (AFRL/RZ-

West)

BROAD AGENCY ANNOUNCEMENT TITLE: Liquid Rocket Engine Technology Development

(LRETD)

BROAD AGENCY ANNOUNCEMENT TYPE: This is the initial closed-ended Broad Agency

Announcement (BAA)

BROAD AGENCY ANNOUNCEMENT NUMBER: BAA-10-02-PKTA

PROPOSAL DUE DATE AND TIME: THIS IS A DRAFT BAA. PROPOSALS ARE NOT

BEING REQUESTED AT THIS TIME. Proposals for all topics will be due by TBD and delivered to

AFFTC/PKTA, 5 South Wolfe Avenue, Edwards AFB, CA 93524. Proposals received after this due date and time shall be governed by the provisions of FAR 52.215-1(c) (3). See Section IV, para. 3 for additional information. 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.

I. PROGRAM DESCRIPTION

The Air Force Research Laboratory, Propulsion Directorate at Edwards AFB, CA is soliciting technical, management and cost proposals on three (3) research and development efforts. Interested offerors are allowed to submit proposals on one (1), two (2), or all three (3) topics. Keep in mind, these are separate distinct topics that require separate proposals and will be evaluated individually. Each proposal must be clearly marked with the pertinent topic title. The three topics are as follows:

Topic 1 – Green Advanced Spacecraft Propulsion (Green ASP)

Topic 2 – Health Assessment and Recognition Tools (HART)

Topic 3 – Propulsion Unit for CubeSats (PUC)

I A. TOPIC 1 – Green Advanced Spacecraft Propulsion (Green ASP)

1. Statement of Objective/Needs:

AFRL’s object of this program is to develop a thruster that will accomodate increased temperature and oxidation product environments to deliver predictable performance. Associated life and delivered thrust scaling as well as degradation algorithms are sought to support predictability of performance.

AFRL is pursuing increased delivered energy density, decreased toxicity spacecraft chemical propulsion to support development and deployment of smaller logistical footprint, more easily deployable and mission capable spacecraft. AFRL has developed increased energy density, decreased toxicity monopropellant formulations relative to the current state of the art; however, the combustion environments are more demanding than state of the art propellants due to the increase in combustion temperature and oxidative product formation. Correspondingly, thruster component temperature and oxidation resistance requirements have increased relative to the state of the art as well. Thruster development to date, specific to AFRL developed advanced monopropellant formulations, has emphasized catalytic ignition. Development work has been focused upon a specific AFRL-developed monopropellant formulation applied to thruster design and support system (tanks, valves, regulators, control components, etc.) primarily for satellite missions. The desired conclusion of this program is a relevant demonstration of flight-like optimized components of relevant mission duty cycles that support a flight-weight propulsion system design with defined performance and lifetime attributes. To achieve this end, the program design will rely on a phased approach 1) to understand thruster component materials requirements defined by combustion environment, degradation behavior, etc., and initialize algorithms describing these, 2) to map out delivered performance in a basic thruster configuration and derive initial scaling and degradition algorithms therefrom, 3) to optimize light-weight thruster development, to test performance and to validate developed algorithms,

4) and to demonstrate program performance goals and design for a proto-flight propulsion unit with supporting data analysis.

2. Scope:

The Green ASP program is investigating the application of a specific advanced monopropellant for spacecraft propulsion to attain a technology readiness level six (6). AFRL is particularly interested in technologies and program approaches that will ensure program success while meeting or exceeding all goals. The program is intended to reduce transition risk by first completely understanding the components and environment so full application of modeling, quality assurance metrics, material investigations, etc. are needed in support of the thruster design.

2.1. The conclusion of this effort is expected to result in a complete propulsion system design meeting specific system-level requirements in a relevant environment.

3. Background:

3.1. Over the past years, related work has been performed and funded by AFRL/RZS in the Liquid

Engine Advanced Propellant – Demonstration Program (LEAP-DP), Advanced Monopropellant Risk Reduction (AMRR) effort and other smaller programs. It is anticipated that this knowledge would be applied to continued research, but past programs are not meant to be used as requirements or development plans for Green ASP.

3.2. Due to ITAR restrictions, information on LEAP-DP and related research will be made available to qualified offerors upon request.

4. Technical Requirements/Program Plan:

4.1. Phase 1 – Thruster component material development

4.1.1. The objective of this phase is to obtain sufficient understanding of the combustion environment for selected monopropellant formulations to support material temperature and oxidation resistance requirement derivation. Available historical kinetics data shall be used to initiate definition of the most materially demanding products of decomposition/ignition.

4.1.2. This phase shall include, but not be limited to, the following topics: factors controlling catalyst reactivity, component stability, decomposition, ignition, thermal influences, material compatibility, and developing Phase 1 exit criteria with corresponding Phase 2 entrance criteria.

4.1.3. The component material development phase is complete upon demonstration through validation of degradation algorithms capturing the impact of chemical and thermal mechanisms, substantiated quality assurance metrics and procedures, and thruster component definition as defined in the Phase 1 exit criteria.

4.2. Phase 2 – Basic thruster performance mapping with scaling and degradation algorithm development

4.2.1. The objective of this phase involves performance testing of the monopropellant thruster using various instrumentation and analytical techniques. The thrust chamber should be designed to facilitate repeated laboratory testing. Instrumentation approach shall include validation of delivery of accurate data.

4.2.2. The phase includes work to validate the algorithm models and behavior mechanisms derived in phase 1 in a realistic thruster chamber. The ignition methods defined in phase 1 will be demonstrated in the thruster environment. Also, performance trade space should be explored to create design guidelines to develop flight thruster designs and thruster system profiles. Phase 2 exit criteria and corresponding Phase 3 entrance criteria shall be developed.

4.2.3. This phase is complete when algorithm models from phase 1 have been validated and performance requirements such as lifetime and delivered density specific impulse are demonstrated for the preliminary thruster design as defined in the Phase 2 exit criteria.

4.3. Phase 3 – Flight like optimized light-weight thruster development, test performance and algorithm validation

4.3.1. The objective of this phase is to design and prove a flight like optimized light-weight monopropellant thruster demonstrating all thruster performance requirements, including thrust measurements and performance in a relevant environment.

4.3.2. The phase includes work to perform thruster firing tests to prove stability, repeatability, performance characterization, material compatibility, continued development and validation of degradation and scaling algorithms, and developing Phase 3 exit criteria and corresponding Phase 4 entrance criteria.

4.3.3. This phase is complete when the light-weight thruster design has proven all performance objectives and algorithm refinements as defined by the Phase 3 exit criteria.

4.4. Phase 4 – Goal demonstration and proto-flight propulsion unit design.

4.4.1. The objective of this phase is to demonstrate performance goals and provide a design for a proto-flight demonstration system for this monopropellant thruster. The program must prepare technical reviews for the demonstration testing and a system requirements review for the proto-flight propulsion system.

4.4.2. The phase includes work to substantiate the design of the proto-flight propulsion system, validation of algorithms developed and applied to design and support definition of interface requirements for a future space vehicle.

4.4.3. This phase is complete when the thruster demonstration in relevant environment meets or exceeds goals as defined by the Phase 4 exit criteria.

4.5. Goal achievement at minimum must consider all design factors such as technical innovation, technical approach, program risk, and management of those risks. The offeror is expected to execute a plan that provides an approach that will make significant advances toward achieving all goals, thus expanding potential future design spaces. Transition from one phase to another will only be authorized upon complete demonstration of mastery of the previous phase through approval by the government program office.

4.6. Risk assessment and quality assurance are critical to success as technologies introduced to the program are expected to enter at various Technology Readiness Levels (TRL). Proposals must identify the critical risks in the development and integration of these technologies into the propulsion system and develop the plan for key risk reduction experiments necessary to mitigate these risks.

The cost and schedule required for these activities shall be identified. All proposed technologies will need to be identified with their respective TRL and an appropriate risk mitigation plan.

4.7. Integrated High Payoff Rocket Propulsion Technology (IHPRPT) Relevance: Proposals solicited under this BAA shall show relevance to IHPRPT Goals by showing traceability of proposed technologies and how they will achieve goals. Although the program cannot develop all required technology (ies) to meet the goals, the proposal shall address how the company would use the proposed technology in combination with other technologies to meet the goals relevant to chemical monopropulsion.

5. Deliverables:

5.1. Data: Any contract awarded as a result of Topic 1 of BAA-10-02-PKTA shall be required to include appropriate data items. All program technical and financial progress shall be reported regularly with interim reports and other documentation as shown by the sample Contract Data Requirements List (CDRL), Table 1. The items below or similar items shall be incorporated into this topic contract award as applicable. The Data Item Descriptions (DID) are given as references only. All reports are to be divided into sections marked as proprietary and non-proprietary information, if applicable. The government has unlimited data rights for all technology that is developed and/or modified on this effort unless pre-identified. Offerors are encouraged to propose alternates, additions, or deletions to the standard items shown below for consideration and approval that would streamline and/or enhance the effectiveness of the effort. In addition, contractor’s format and report consolidation are highly encouraged and will be acceptable upon approval. Proposals must show a list of CDRL items included in the price of the proposal and where in the WBS they will be generated. Electronic submission of data items is required. See the Model Contract, Exhibits A and B for complete requirements.

Table 1 - TOPIC 1 Sample Contract Requirements List (CDRL)

CDRL Authority Description Frequency

A001 DI-ADMN-81373/T Presentation Material As Required

A002 DI-CMAN-80792A/T Validation Report One Time & Revisions

A003 DI-FNCL-80331A/T Funds and Man-Hours Expenditure Report Monthly

A004 DI-MGMT-80227/T

Contractor's Progress, Status and Management Report Monthly

A005 DI-SESS-81785/T System Engineering Management Plan (SEMP) One Time & Revisions

A006 DI-MGMT-81117/T Technical and Management Work Plan

Revisions

A007 DI-MGMT-81468/T Contract Funds Status Report (CFSR) Quarterly

A008 DI-NDTI-80566A/T Test Plan As Required

A009 DI-NDTI-80603A/T Test Procedure As Required

A010 DI-MISC-80169/T Photographic Coverage As Required

A011 DI-SESS-81001D/T Conceptual Design Drawings/Models As Required

B001 DI-MISC-80711A/T Scientific and Technical Reports: Final Report One Time & Revisions

B002 DI-MISC-80711A/T

Scientific and Technical Reports: Interim Tech Report As Required

B003 DI-MISC-80711A/T

Scientific and Technical Reports: Procedure Manual

One Time & Revisions

B004 DI-SESS-81002E/T

Developmental Design Drawings/Models and Associated Lists

5.2. Distribution of Information: All technical data generated or delivered under any contract resulting from this BAA is controlled by the International Traffic in Arms Regulation (ITAR), 22 CFR Sections 121 through 128, and will require the following distribution statement:

―This document contains technical data whose export is restricted by the ARMS EXPORT CONTROL ACT (Title 22, USC, Sec 2751 et seq) or the EXPORT ADMINISTRATION ACT of 1979, as amended, Title 50, USC, APP 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.‖

5.3. All data generated or delivered will also require the following two statements depending on the content of the information:

―Distribution Statement C – Distribution authorized to U.S. Government agencies and their contractors, Critical Technology (date of determination). Other requests for this document shall be referred to AFRL/RZS, 5 Pollux Dr, Edwards AFB CA 93524-7048.‖

OR

―Distribution Statement B – Distribution authorized to U.S. Government Agencies Only, Proprietary Information (date of determination). Other requests for this document shall be referred to AFRL/RZS, 5 Pollux Dr, Edwards AFB CA 93524-7048.‖

5.4. Hardware: The contractor may be required to deliver hardware in accordance with the requirements of the Statement of work. The desired hardware deliverable will be delivered upon completion of the technical effort.

6. Schedule:

The anticipated period of performance for Phase 1, 2, 3 and 4 is the following:

6.1. Phase 1: Nine months technical effort, Three months Final Scientific and Technical Reporting Cycle

6.2. Phase 2: Twelve months technical effort, Three months Final Scientific and Technical Reporting

Cycle

6.3. Phase 3: Fifteen months technical effort, Three months Final Scientific and Technical Reporting

6.4. Phase 4: Eighteen months technical effort, Three months Final Scientific and Technical Reporting

7. Other Requirements:

7.1. 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 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. On-line registration instructions can be accessed from the DISA CCR home page at http://www.ccr.gov.

8. Other Information:

8.1. Classified Material: The use of classified material is not anticipated for this contract. However, if an offeror proposes to use or generate classified material, the Technical POC shall be contacted for further guidance.

8.2. Government Furnished Property (GFP). It is possible that GFP may be involved or used in this effort; however, if GFP is required it must be indentified in the proposal and in the final awarded contract. If proposing GFP, identify the source, location of the property, who owns it (include point of contract with phone number), approval from the property owner, and how, when, and for how long it will be made available under the proposed effort. Address commonality with other programs. If contributions from other efforts are proposed, identify the specific efforts, the planned start and end dates, and the applicability to the current BAA. In addition, ensure all efforts are included on the proposed program schedule.

8.3. Base Support: If proposed, AFRL will provide, within current capabilities, the test facilities including test stand, power, test stand instrumentation, test stand integration management, test stand data acquisition systems, and test facility interface management as Government Furnished Equipment (GFE). This GFE will be provided by AFRL at no cost to the contract within current AFRL facilities capabilities (see AFMCFARS Clause 5352.245-9004). Hardware test end items must be delivered to the test site complete with all controls, safe guards, components and test instrumentation as identified by test Interface Control Document (ICD). Funding previously identified does not include any of the costs of the AFRL test facilities, consumables, testing, and data acquisition, which will be

GFE.

8.3.1. The AFRL Facilities Data Package may include specifications, capacities, pressures, electrical supplies, fluid supplies, instrumentation capabilities, performance, funding, schedule capabilities, etc. Due to ITAR requirements these AFRL test facilities data must be requested in writing from the

TPOC.

8.3.2. If AFRL test facilities are proposed for the integrated large scale test, the offerors are to provide engineering liaison, test support, hardware support, and hardware integration support for the test program. Liaison is defined, at minimum, to include contributing and direct involvement in test planning; test readiness reviews; hardware functional tests and servicing; instrumentation checkout and calibration, pre-test, test and post-test procedures; test monitoring; test data review and analysis; identify design modification and recommendations; and test reporting. If additional http://www.bpn.gov/orca http://www.ccr.gov/ instrumentation is required to validate the design and analysis tools, then it will be identified in the test planning to ensure traceability to the program goals. Test support is to be maintained and updated through the life of the effort. If another test facility is proposed other than AFRL, all its test requirements must be considered in the proposed program schedule and costs.

8.3.3. Spent hardware will be removed from the test site at completion of testing by the contractor.

8.3.4. NOTE: Offerors may identify alternate test facilities. However, any other test facility identified shall be considered a direct cost to the awarded contract.

8.4. JANNAF: Offerors shall include participation in the Joint Army Navy NASA Air Force (JANNAF) conferences, subcommittee meetings, and periodic workshops in order to present current results.

Participation in the JANNAF conferences, subcommittee meetings, panels, and workshops will serve as a mechanism to report current progress to the community. JANNAF participation will be defined by CDRL in each specific task where such participation is deemed necessary for that particular effort.

I B. TOPIC 2 – Health Assessment and Recognition Tools (HART)

The purpose of this topic is to solicit proposals for the development of innovative technologies in the field of liquid rocket engine health management. More specifically, the purpose of this topic is to develop sensors and sensor data algorithms that will enable oxygen-rich staged-combustion cycle reusable booster engines to achieve the Air Force operability goal for engine turnaround time.

Solutions of particular interest include those that reduce or eliminate time-consuming ground inspections and/or maintenance actions. This topic has two (2) areas of interest.

1.1. Area 1: Turbopump Assembly (TPA) Application:

Studies have shown that the largest fraction of a reusable rocket engine’s turnaround time is due to the routine inspections and maintenance performed on the TPA. In order to reach the Air Force goal for turnaround time for reusable rocket engines, time-intensive inspections and maintenance actions must be reduced and/or eliminated by use of new and novel sensor designs that can provide accurate and reliable data on the health status of the TPA. (For information on which data is desired for the HCB TPA, offerors may request the Hydrocarbon Boost IHPRPT Vision Engine (HIVE) Turnaround and Engine Health Management (EHMS) Report.)

1.2. Area 2: Thrust Chamber Assembly (TCA) Application:

Studies have shown that the second largest fraction of a reusable rocket engine’s turnaround time is due to the routine inspections and maintenance performed on the TCA and other combustion devices. In order to reach the Air Force goal for turnaround time for reusable rocket engines, time-intensive inspections and maintenance actions must be reduced and/or eliminated by use of new and novel sensor designs that can provide accurate and reliable data on the health status of the TCA. (For information on which data is desired for the HCB TCA, offerors may request the Hydrocarbon Boost IHPRPT Vision Engine (HIVE) Turnaround and Engine Health Management (EHMS) Report.)

1.3. Each submitted proposal should address only one of the areas of this topic. Separate proposals should be prepared for each area in the event that an offeror would like to propose work for both areas of this topic so that it is possible for a single company to receive two separate awards covering both areas. Separate proposals from a single offeror covering each area should not rely on the other to be awarded.

AFRL is particularly interested in technical concepts and program approaches that address the following concerns:

2.1. It is envisioned that addressing the following issues may be necessary:

2.1.1. Sensor survivability in high temperature and high pressure environment

2.1.2. Sensor material compatibility with liquid oxygen (LOX), gaseous oxygen (GOX), and/or kerosene

2.1.3. Sensor reliability traceable to Hydrocarbon Boost (HCB) goals

2.1.4. Sensor ability to be reused without the need for maintenance throughout the life of the engine

2.1.5. Sensor range modification

2.1.6. Sensor algorithm ability to provide meaningful data in real-time

2.2. It is desired, though not required that the sensor and algorithms developed during this effort will operate in passive mode during future Hydrocarbon Boost testing. For this to be possible, it is anticipated that an Associate Contractor Agreement and/or subject may be needed with the HCB contractor to ensure HART products are included in the design process (no later than component

PDR).

3.1. The Air Force Research Laboratory Propulsion Directorate (AFRL/RZ) is interested in advancing state-of-the-art and scientific knowledge in liquid propellant rocket engine technologies in support of Operationally Responsive Space Access (ORS). Technologies that enable the Hydrocarbon Boost Vision Engine (HIVE) to meet operability and maintainability goals while maintaining or exceeding IHPRPT performance and reliability goals are of particular interest.

The Hydrocarbon Boost Technology Demonstrator Program is a technology test bed for developing a 250,000 lbf Liquid Oxygen (LOX) / Kerosene ox-rich staged combustion cycle booster engine. The program is moving forward into component preliminary design.

This topic covers engine health management (EHM) technologies that enable operationally responsive space access liquid propellant rocket booster engines. Engine health management interests include hardware and corresponding algorithm development needed to determine the health status of liquid oxygen (LOX)/kerosene fueled booster engines in support of engine turnaround time requirements. Items of particular interest include sensors and sensor algorithms for reducing or eliminating inspections and/or maintenance actions related to turbopump assemblies (TPA) or thrust chamber assemblies (TCA).

3.2. Solutions should be applicable to the current AFRL Hydrocarbon Boost Technology Demonstrator Engine, though not necessarily uniquely specific to the engine design or operating parameters.

3.3. Due to ITAR restrictions, information on the Hydrocarbon Boost Technology Demonstrator design will be made available to qualified offerors upon request.

Multiple awards are anticipated from this solicitation. To preserve competition throughout this effort and develop the most technological options for future reusable booster engine procurements, efforts are being solicited as a basic contract with a series of contract options. Exercise of these options is envisioned to occur at key milestones. Management tasks should be planned for the basic effort and within each option.

4.1. Phase 1: The conceptual design effort should contain as a minimum: 1) analytical and experimental critical function and/or characteristic proof-of-concept, 2) conceptual design, 3) conceptual design review (CoDR), 4) and final report. The effort will culminate in a review of the sensor and algorithm requirements, justifications, development plans, and conceptual design. The Government may exercise options at this point based on the realism of the risk assessment of the design, quality and thoroughness of the design, the perceived value to the offeror and the Government, and programmatic (cost, schedule and reporting) performance to date.

4.2. Phase 2: The validation effort should be planned and priced as an optional task. This optional task should include as a minimum: 1) mitigation of development risks, 2) configuration control and design process management, 3) Preliminary Design Review (PDR), 5) procurement of items for fabrication, modifications, and testing as necessary, 6) CDR, 7) hardware fabrication/assembly, 8) sensor/algorithm validation in a laboratory environment, and 9) final report.

5.1. Data: Any contract awarded as a result of Topic 2 of BAA-10-02-PKTA shall be required to include appropriate data items. All program technical and financial progress shall be reported regularly with interim reports and other documentation as shown by the sample Contract Data Requirements List (CDRL), Table 2. The items below or similar items shall be incorporated into this BAA contract award as applicable. The Data Item Descriptions (DID) are given as references only. All reports are to be divided into sections marked as proprietary and non-proprietary information, if applicable. The Government has unlimited data rights for all technology that is developed and/or modified on this effort unless pre-identified. Offerors are encouraged to propose alternates to the standard items shown below for consideration and approval. In addition, contractor’s format and report consolidation are highly encouraged and will be acceptable upon approval. Alternate or additional data items that would streamline and/or enhance the effectiveness of the effort are solicited. Proposals must show a list of CDRL items included in the price of the proposal. Electronic submission of data items is required.

Table 2 - TOPIC 2 Sample Contract Requirements List (CDRL)

A001 DI-MGMT-81334B/T Contract Work Breakdown Structure (CWBS) One Time & Revisions

A002 DI-MGMT-81468/T Contract Funds Status Report (CFSR) Quarterly

A003 DI-MGMT-81117/T

Technical and Management Work Plan: Quarterly Management Assessment

As Required

A004 DI-MGMT-80227/T

Contract’s Progress, Status and Management Report

Bi-Monthly

A005 DI-MGMT-81650 Integrated Master Schedule Bi-Monthly

A006 DI-ADMN-81373/T Presentation Material As Required

A007 DI-MISC-80738/T

Magnetic Tape Cartridges, Video Data, and Voice Records

As Required

A008 DI-MISC-80169/T Photo Coverage As Required

A009 DI-DRPR-80651 Engineering Drawings/Models As Required

A010 DI-ADMN-81250A/T Conference Minutes As Required

A011 DI-MGMT-81453/T Data Accession List (DAL) As Required

A012 DI-NDTI-80603/T Test Procedure As Required

B001 DI-MISC-80711A/T Scientific and Technical Report: Interim Report Annually & Revisions

B002 DI-MISC-80711A/T Scientific and Technical Report: Final Report

5.2. Distribution of Information: All technical data generated or delivered under any contract resulting

121 through 128, and will require the following distribution statement:

―This document contains technical data whose export is restricted by the ARMS EXPORT CONTROL ACT (Title 22, USC, Sec 2751 et seq) or the EXPORT ADMINISTRATION ACT of 1979, as amended, Title 50, USC, APP 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.‖

All data generated or delivered will also require one of the following two statements depending on the content of the information:

―Distribution Statement C – Distribution authorized to U.S. Government agencies and their contractors, Critical Technology (date of determination). Other requests for this document shall be referred to AFRL/RZS, 5 Pollux Dr, Edwards AFB CA 93524-7048.‖

OR

―Distribution Statement B – Distribution authorized to U.S. Government Agencies Only, Proprietary Information (date of determination). Other requests for this document shall be referred to AFRL/RZS, 5 Pollux Dr, Edwards AFB CA 93524-7048.‖

5.3. Hardware: Desired residual hardware will be identified during contract performance and delivered to AFRL/RZSE upon the completion of the technical effort. It is anticipated that at a minimum the sensor components and any other critical items will be delivered.

The anticipated periods of performance for Phases 1 and 2 are as follows:

6.1. Phase 1: Fifteen months technical effort, Three months Final Scientific and Technical Reporting

6.2. Phase 2: Thirty months technical effort, Three months Final Scientific and Technical Reporting Cycle

7.1. 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 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. On-line registration instructions can be accessed from the DISA CCR home page at http://www.ccr.gov.

8.1. Classified Material: The use of classified material is not anticipated for this contract. However, if contract. If proposing GFP, identify the source, location of the property, who owns it (include point of contract with phone number), approval from the property owner, and how, when, and for how long it will be made available under the proposed effort. Address commonality with other programs. If contributions from other efforts are proposed, identify the specific efforts, the planned start and end dates, and the applicability to the current BAA. In addition, ensure all efforts are included on the proposed program schedule.

8.3. Base Support: If proposed, AFRL will provide, within current capabilities, the test facilities including acquisition systems, and test facility interface management as Government Furnished Equipment (GFE). This GFE will be provided by AFRL at no cost to the contract within current AFRL facilities capabilities (see AFMCFARS Clause 5352.245-9004). Hardware test end items must be delivered to the test site complete with all controls, safe guards, components and test instrumentation as identified by test Interface Control Document (ICD). Funding previously identified does not include any of the costs of the AFRL test facilities, consumables, testing, and data acquisition, which will be

8.3.1. The AFRL Facilities Data Package may include specifications, capacities, pressures, electrical

8.3.2. If AFRL test facilities are proposed for the integrated large scale test, the offerors are to provide program. Liaison is defined, at minimum, to include contributing and direct involvement in test planning; test readiness reviews; hardware functional tests and servicing; instrumentation checkout and calibration, pre-test, test and post-test procedures; test monitoring; test data review and analysis; identify design modification and recommendations; and test reporting. If additional instrumentation is required to validate the design and analysis tools, then it will be identified in the test planning to ensure traceability to the program goals. Test support is to be maintained and updated through the life of the effort. If another test facility is proposed other than AFRL, all its test

8.3.3. Spent hardware will be removed from the test site at completion of testing by the contractor.

8.3.4. NOTE: Offerors may identify alternate test facilities. However, any other test facility identified shall be considered a direct cost to the awarded contract.

8.4. JANNAF: Offerors shall include participation in the Joint Army Navy NASA Air Force (JANNAF) conferences, subcommittee meetings, and periodic workshops in order to present current results.

Participation in the JANNAF conferences, subcommittee meetings, panels, and workshops will serve as a mechanism to report current progress to the community. JANNAF participation will be defined by CDRL in each specific task where such participation is deemed necessary for that particular effort.

I C. TOPIC 3 – Propulsion Unit for CubeSats (PUC)

Air Force Research Laboratory at Edwards AFB is interested in developing a propulsion module for precision maneuvering of very small spacecraft. Spacecraft typified by the emerging ―cubesat‖ standard may provide a new paradigm for responsive spacecraft. Spacecraft with stowed volumes of between 1,000 cm and 3,000 cm massing approximately 3 kg for a variety of missions are advantageous for a variety of Air Force missions. One significant drawback of present cubesat technology is the lack of capable primary propulsion. Recent analysis performed at AFRL has determined that it is possible to increase total impulse capability dramatically over current state-of-the-art while remaining within a 1,000 cm envelope. Technologies of interest include both low and high thrust propulsion technologies.

AFRL/RZS is investigating application of many types of spacecraft propulsion in relations to the size and scale of cubesat missions and desires to advance appropriate technologies to a technology readiness level six (6). The propulsion capabilities of the systems of interest will likely be used for both the generation of large orbital changes (e.g. orbit raising or lowering, circularization, etc.) and small impulse bits (e.g. orbital rendezvous, precision formation flying, etc.). Propulsion systems of most interest to the Air Force are those that retain maximum mission flexibility with the maximum impulse and capability for large-scale orbital maneuvers.

2.1. At the conclusion of each effort, a proven propulsion system design meeting the performance requirements below and with a defined interface within a 1U structure should be delivered to AFRL.

3.1 AFRL is familiar with work being done on cubesat-size propulsion with NRO, AFRL/RV and several university-based projects. AFRL/RZS has not funded cubesat-centric projects before.

4.1. Development work will focus on developing the critical technologies required to provide maximum propulsion capability within a 1,000 cm volume (1U) for a spacecraft with a total volume of 3,000 cm (3U). Propulsion capability should include a minimum delta-V of 100 m/s for the 3U spacecraft.

Propulsive attitude control also is of interest to maximize payload. In all cases, precision impulse bits as low as 500 µNs may be necessary.

4.2. The required systems not only include the generation of thrust, but also support systems such as tanks, valves, regulators, control components, etc. Development will also need to involve all aspects of the thruster such as modelling of propellant acceleration, material science of components, supporting diagnostic for materials and plumes, propulsion system development, and control of thruster and propulsion systems through a single simple interface.

4.3. Phase 1: The first stage is development of system concept to prove the propulsion performance

(thrust levels, total impulse, lifetime, etc. as defined in the proposal) of the technology and tractability to packaging of the proposed system into a 1,000 cm cube. This phase is intended to be a proof-of-concept before entrance into a complete system build and the Government may exercise options at this point based on the realism of the risk assessment of the design, quality and thoroughness of the design, the perceived value to the offeror and the Government, and programmatic (cost, schedule and reporting) performance to date.

4.4. Phase 2: The second stage is the development of a complete demonstration unit and should be planned and priced as an optional task pursuant to Government approval following a successful phase 1.

4.5. Spacecraft power is assumed to be less than 25 W with only a 50% duty cycle available for propulsion purposes.

4.6. Goal achievement at minimum must consider all design factors such as component miniaturization, structural integrity, physical constraints of the defined cubesat standards, and component/system appropriateness for spaceflight. The offeror is expected to execute a plan that provides an approach that would design a self-contained propulsion system, develop and validate components of that system, and then prove functionality of that propulsion system in a relevant environment.

4.7. With regards to cubesat-class design specifications defined in the spacecraft community, proposals must address the mechanical and electrical constraints, but do not need to adhere to limitations on pressure vessels or stored chemical energy.

4.8. Risk assessment and quality assurance are critical to success as technologies introduced to the program are expected to enter at various Technology Readiness Levels (TRL). Proposals must identify the critical risks in the development and integration of these technologies into the propulsion system and develop the plan for key risk reduction experiments necessary to mitigate these risks.

The cost and schedule required for these activities shall be identified. All proposed technologies will need to be identified with their respective TRL and an appropriate risk mitigation plan.

5.1. Data: Any contract awarded as a result of Topic 3 of BAA-10-02-PKTA shall be required to include appropriate data items. All program technical and financial progress shall be reported regularly with interim reports and other documentation as shown by the sample Contract Data Requirements List (CDRL), Table 3. The items below or similar items shall be incorporated into this topic contract award as applicable. The Data Item Descriptions (DID) are given as references only. All reports are to be divided into sections marked as proprietary and non-proprietary information, if applicable. The government has unlimited data rights for all technology that is developed and/or modified on this effort unless pre-identified. Offerors are encouraged to propose alternates, additions, or deletions to the standard items shown below for consideration and approval that would streamline and/or enhance the effectiveness of the effort. In addition, contractor’s format and report consolidation are highly encouraged and will be acceptable upon approval. Proposals must show a list of CDRL items included in the price of the proposal and where in the WBS they will be generated. Electronic submission of data items is required. See the Model Contract, Exhibits A and B for complete

Table 3 - TOPIC 3 Sample Contract Requirements List (CDRL)

A001 DI-ADMN-81373/T Presentation Material As Required

A002 DI-CMAN-80792A/T Validation Report One Time & Revisions

A003 DI-FNCL-80331A/T Funds and Man-Hours Expenditure Report Monthly

A004 DI-MGMT-80227/T

Contractor's Progress, Status and Management Report Monthly

A005 DI-SESS-81785/T System Engineering Management Plan (SEMP) One Time & Revisions

A006 DI-MGMT-81117/T Technical and Management Work Plan One Time & Revisions

A007 DI-MGMT-81468/T Contract Funds Status Report (CFSR) Quarterly

A008 DI-NDTI-80566A/T Test Plan As Required

A009 DI-NDTI-80603A/T Test Procedure As Required

A010 DI-MISC-80169/T Photographic Coverage As Required

A011 DI-SESS-81001D/T Conceptual Design Drawings/Models As Required

B001 DI-MISC-80711A/T Scientific and Technical Reports: Final Report One Time & Revisions

B002 DI-MISC-80711A/T

Scientific and Technical Reports: Interim Tech Report As Required

B003 DI-MISC-80711A/T

Scientific and Technical Reports: Procedure Manual

One Time & Revisions

B004 DI-SESS-81002E/T

Developmental Design Drawings/Models and Associated Lists

5.2. Distribution of Information: All technical data generated or delivered under any contract resulting

121 through 128, and will require the following distribution statement:

―This document contains technical data whose export is restricted by the ARMS EXPORT CONTROL ACT (Title 22, USC, Sec 2751 et seq) or the EXPORT ADMINISTRATION ACT of 1979, as amended, Title 50, USC, APP 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.‖

5.3. All data generated or delivered will also require the following two statements depending on the content of the information:

―Distribution Statement C – Distribution authorized to U.S. Government agencies and their contractors, Critical Technology (date of determination). Other requests for this document shall be referred to AFRL/RZS, 5 Pollux Dr, Edwards AFB CA 93524-7048.‖

OR

―Distribution Statement B – Distribution authorized to U.S. Government Agencies Only, Proprietary Information (date of determination). Other requests for this document shall be referred to AFRL/RZS, 5 Pollux Dr, Edwards AFB CA 93524-7048.‖

5.4. Hardware: The contractor may be required to deliver hardware in accordance with the requirements of the Statement of work. The desired hardware deliverable will be delivered upon completion of the technical effort.

There is no anticipated period of performance for completion of a proven system. Offerors must define their development schedule within their proposals considering the appropriateness to their package and AFRL’s anticipated funding schedule in this BAA.

7.1. 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 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. On-line registration instructions can be accessed from the DISA CCR home page at http://www.ccr.gov.

8.1. Classified Material: The use of classified material is not anticipated for this contract. However, if contract. If proposing GFP, identify the source, location of the property, who owns it (include point of contract with phone number), approval from the property owner, and how, when, and for how long it will be made available under the proposed effort. Address commonality with other programs.

If contributions from other efforts are proposed, identify the specific efforts, the planned start and end dates, and the applicability to the current BAA. In addition, ensure all efforts are included on the proposed program schedule.

8.3. Base Support: If proposed, AFRL will provide, within current capabilities, the test facilities including acquisition systems, and test facility interface management as Government Furnished Equipment (GFE). This GFE will be provided by AFRL at no cost to the contract within current AFRL facilities capabilities (see AFMCFARS Clause 5352.245-9004). Hardware test end items must be delivered to the test site complete with all controls, safe guards, components and test instrumentation as identified by test Interface Control Document (ICD). Funding previously identified does not include any of the costs of the AFRL test facilities, consumables, testing, and data acquisition, which will be

8.4. The AFRL Facilities Data Package may include specifications, capacities, pressures, electrical

8.5. If AFRL test facilities are proposed for the integrated large scale test, the offerors are to provide program. Liaison is defined, at minimum, to include contributing and direct involvement in test planning; test readiness reviews; hardware functional tests and servicing; instrumentation checkout and calibration, pre-test, test and post-test procedures; test monitoring; test data review and analysis; identify design modification and recommendations; and test reporting. If additional instrumentation is required to validate the design and analysis tools, then it will be identified in the test planning to ensure traceability to the program goals. Test support is to be maintained and updated through the life of the effort. If another test facility is proposed other than AFRL, all its test

8.6. Spent hardware will be removed from the test site at completion of testing by the contractor.

8.7. NOTE: Offerors may identify alternate test facilities. However, any other test facility identified shall be considered a direct cost to the awarded contract.

8.8. JANNAF: Offerors shall include participation in the Joint Army Navy NASA Air Force (JANNAF) conferences, subcommittee meetings, and periodic workshops in order to present current results.

Participation in the JANNAF conferences, subcommittee meetings, panels, and workshops will serve as a mechanism to report current progress to the community. JANNAF participation will be defined by CDRL in each specific task where such participation is deemed necessary for that particular effort.

II. AWARD INFORMATION:

II A. TOPIC 1 – Green Advanced Spacecraft Propulsion (Green ASP)

1. Anticipated Funding:

Anticipated funding for this topic (not per contract or award) is four million two hundred thousand dollars ($4,200,000). The funding schedule is divided over six years:

Table 4 - TOPIC 1 Planned Funding Profile

Fiscal Year -- ($K)…