EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

PRE-EMD CALL FOR IMPROVEMENT (CFI)

CFI# F04701-96-R-0008

The EELV Pre-EMD CFI consists of the files listed in the following table. *.DOC files are in MS Word 6.0. *.PPT files are in MS Powerpoint 4.0. *.PDF files are in Acrobat Portable Document File format.

Contents	Description
CFI.DOC	Call For Improvement Basis of Award and Instructions
Section 1	EELV Program Statement of Objectives (SOO)
Section 2	Pre-EMD Basis of Award and Evaluation Standards
Section 3	Proposal Preparation Instructions
SDCE.DOC	Annex 1, Software Development Capability Evaluation Information
TEMPLATE.PPT	Annex 2, Proposal Templates
RVWDEFN.DOC	Annex 3, Design Review Definitions
DD1707.PPT	Information to Offerors or Quoters (Section A cover sheet)
SF33.DOC	Solicitation, Offer, and Award (Section A)
MODELK.DOC	Annex 4, Pre-EMD Model Contract (Sections B-J)
REPCERT.DOC	Annex 5, Representations and Certifications (Section K)
SPD.DOC	Annex 6, System Performance Document
CDRL.DOC	Annex 7, Contract Data Requirements List (Exhibit A)
DD254.DOC	Annex 8, DD Form 254 - Contract Security Classification Specification
EELVCFI.PDF	All of the above files combined into Adobe .PDF format

This page intentionally left blank.

CFI Section 1 - EELV Program Statement Of Objectives

1.0 EELV Program Objective. The objective of the EELV program is to design and develop a spacelift system, evolved from current launch vehicle systems or major subsystems thereof, in accordance with the EELV System Performance Document (SPD) requirements. This spacelift system will reduce costs over current systems while preserving or improving reliability, maintainability, and operability.

2.0 Pre-EMD Module Objectives. Specific objectives of this Module are as follows:

a) Develop the EELV system design (flight/ground hardware and software) to a Downselect Design Review (DDR) level, as a minimum (refer to CFI Annex 3). Conduct appropriate analyses, tests and demonstrations to show compliance with the SPD requirements. Develop an Operations and Support (O&S) concept based on the HQ Air Force Space Command approved O&S concept. Reduce program risks to levels sufficient to establish readiness to proceed into the EMD Module.

b) Demonstrate integration of the manufacturing and quality functions into the design and development process to significantly reduce or eliminate the Material Review Board process in Production.

c) Design and develop the EELV system to achieve at least a 25% (with an objective of 50%) reduction from the $20.6B (FY95$) recurring costs of existing launch systems within the EMD cost target of $1.4B (FY95$) at the 50% confidence level.

d) Provide real-time reliable and user-friendly electronic access to contractor EELV-related data.

e) Conduct combined DT&E/OT&E activities.

f) Provide analyses and data in support of the Air ForceÕs Environmental Impact Analysis Process. Integrate environmental, safety, and health factors into the EELV system design.

g) Complete and coordinate facility design as necessary to support required construction start dates upon commencement of the EMD Module.

h) Provide analyses and data to support the Air Force's request for an explosive siting approval.

i) Fully tailor a Range Safety Requirements document consistent with the maturity of the system design.

j) Participate in a Software Development Capability Evaluation (refer to CFI Annex 1).

k) Work toward establishing firm contractor commitments (Not To Exceed prices (NTEs)) for the price of planned initial production lots (to meet FY02-05 launches) for inclusion in the EMD proposal.

l) Provide insight into execution of the commercial management plan which shows synergy with Government requirements.

m) Support the Government's planning to move the program office to the EMD contractor's facility at the beginning of the EMD Module.

3.0 EMD Module Objectives. Specific objectives of this Module are as follows:

a) Conduct a Tailored Critical Design Review (TCDR), if not conducted in Pre-EMD (refer to CFI Annex 3). Complete EELV system, subsystem and component production design.

b) Complete all facilities construction and activation of all launch sites.

c) Conduct two system test flights.

d) Complete combined DT&E/IOT&E and support dedicated IOT&E.

e) Complete the EELV system design and development which achieves at least a 25% (with an objective of 50%) reduction from the $20.6B (FY95$) recurring costs of existing launch systems within the EMD cost target of $1.4B (FY95$) at the 50% confidence level.

f) Verify adequate process control and factory sizing to significantly reduce or eliminate the Material Review Board process in Production.

g) Establish the manufacturing infrastructure for initial production to support FY02-05 launch requirements.

h) Finalize an O&S transitional approach. Develop and implement an operations and maintenance infrastructure to support flight and ground systems hardware, software, facilities, and personnel resources.

i) Complete the tailored Range Safety Requirements document within 60 days after EMD award.

j) Provide insight into execution of the commercial management plan which shows synergy with Government requirements.

CFI Section 2 - Pre-EMD Basis of Award and Evaluation Standards

(1) Pursuant to FAR 52.252-1, "SOLICITATION PROVISIONS INCORPORATED BY REFERENCE," the following provisions are incorporated herein by reference.

I. FEDERAL ACQUISITION REGULATION (1991 EDITION) (48 CFR CHAPTER 1) SOLICITATION PROVISIONS: NONE ARE APPLICABLE.

II. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT (1991 EDITION) (48 CFR CHAPTER 2) CLAUSES: NONE ARE APPLICABLE.

2.1 Basis for Contract Award

The Government intends to award two Firm Fixed-Priced (FFP) contracts for the Pre-EMD Module for up to $60M each. However, the Government reserves the right to award only one contract, or to award no contract. The Government will award no more than one contract per prime contractor. For purposes of this CFI, a prime contractor means an individual, partnership, corporation, or association.

Proposals will be evaluated as a competitively negotiated procurement in accordance with FAR 15.6 and DOD, USAF, and AFMC supplements thereto. AFFARS Appendix AA, and AFMC supplements thereto, will be used as guidance in the evaluation. The basis of contract award will be "best value" to the Government. "Best value" is defined as the most advantageous offers, price and other factors considered, providing the best mix of utility, technical quality, business aspects, risks, and price for a given application. All offers, however, must be within the price limitation of $60M. The "best value" determination will be made by the Source Selection Authority (SSA) after an integrated assessment of the offers based on the elements described herein.

2.2 Evaluation Criteria. The Government will evaluate the Offeror's proposal against the criteria depicted in Table 2.2, as well as General Considerations.

Table 2.2

Evaluation Criteria Matrix

AREA 1: AFFORDABILITY

LCCE Recurring (Production & O&S)

LCCE Non-recurring (EMD & Facilities)

Performance Risk

L/M/H

Most Probable Cost	$	$
Offeror's Estimate	$	$
Ranking Within Area	1st	2nd

Table 2.2 (cont'd)

Evaluation Criteria Matrix

AREA 2: USER REQUIREMENTS

Performance

Reliability

Standardization

Performance Risk

L/M/H

Proposal Risk	L/M/H	L/M/H	L/M/H
Proposal Rating	B/G/Y/R	B/G/Y/R	B/G/Y/R
Ranking Within Area	1st	2nd	2nd

AREA 3: PROGRAM EXECUTION

Program Executability (Pre-EMD & EMD)

Pre-EMD Management

Producibility/ Manufacturing

Performance Risk

L/M/H

Proposal Risk	L/M/H	L/M/H	L/M/H
Proposal Rating	B/G/Y/R	B/G/Y/R	B/G/Y/R
Ranking Within Area	1st	2nd	2nd

AREA 4: COMMERCIAL LAUNCH CONSIDERATIONS

Proposal Risk	L/M/H
Proposal Rating	B/G/Y/R

2.3 Areas, Factors, and General Considerations. Among the areas depicted in Table 2.2, the Affordability area is first in importance. The User Requirements area and the Program Execution areas are equal and second in importance. The Commercial Launch Considerations area is fourth in importance. General Considerations (paragraph 2.5) are last in importance. Ranking of the factors within each area is depicted in Table 2.2. Within General Considerations, Pre-EMD price is first in importance, acceptance of terms and conditions is second, and the extent to which the Offeror identifies and commits to small and small disadvantaged business contracts is third. All evaluation areas and factors, when combined, are significantly more important than Pre-EMD price. However, Pre-EMD price is a significant evaluation consideration.

2.4 Ratings. As depicted in Table 2.2, a performance risk rating will be given for the Affordability, User Requirements, and Program Execution areas, and a proposal rating as well as a proposal risk rating will be given for the factors within the User Requirements and Program Execution areas and also for the Commercial Launch Considerations area. For the Affordability area, performance risk and Most Probable Cost (MPC) are equal in importance, and each alone is more important than the Offeror's estimate. For the User Requirements and Program Execution areas, the performance risk, proposal risk, and proposal rating are equal in importance (1/3 each). For the Commercial Launch Considerations area, proposal risk and proposal rating are equal in importance (1/2 each). The ratings are defined in accordance with AFFARS Appendix AA as supplemented by the following information.

2.4.1 Performance Risk. For each area except Commercial Launch Considerations, the Government will assess the Offeror's (including subcontractors, associates, and teaming arrangements) ability to successfully perform as proposed, based on the Offeror's present and past performance record. In assessing performance risk, the Government will use both data provided by the Offeror and obtained from other sources, such as Contractor Performance Assessment Reports (CPARs), preaward surveys, and LCCV Module performance, if applicable. The assessment will be reported as low, moderate, or high.

2.4.2 Proposal Risk. For each factor within the User Requirements and Program Execution areas, and for the Commercial Launch Considerations area, the Government will assess the risk associated with the Offeror's proposal. The assessment of proposal risk will consider cost, schedule, and technical risk; risk mitigation measures; technical design sufficiency; analysis and simulation tools; application of specifications and standards; environmental, safety, and health considerations; requirements allocation and traceability; and design compatibility with the functional baseline. Sources of information for the assessment of proposal risk include LCCV CDRL items, the Software Development Capability Evaluation (SDCE), preaward surveys, the Offeror's Pre-EMD proposal, and other Government insight and data obtained during the LCCV Module. The assessment will be reported as low, moderate, or high.

2.4.3 Proposal Rating. For each factor within the User Requirements and Program Execution areas, and for the Commercial Launch Considerations area, a color rating will be assigned that depicts how well the Offeror's proposed design concept or approach meets the evaluation standards prescribed for that factor or area. The color ratings will be reported as blue, green, yellow, or red as defined in AFFARS Appendix AA.

2.4.4 Most Probable Cost. Within the Affordability area, the Government will assess the Most Probable Cost (MPC) at the 50% Confidence Level (CL). MPC considers those elements defined in CFI reference document LCCE70%.PDF, found on the EELV Electronic Bulletin Board (EBB) (refer to CFI paragraph 3.1.10 for instructions on accessing the EBB). In calculating MPC, the Government will evaluate the reasonableness, realism, and completeness of the Offeror's estimates.

2.4.4.1 Realism. The Government will evaluate realism by assessing the compatibility of proposed costs with proposed scope and effort.

2.4.4.2 Reasonableness. The Government will evaluate reasonableness through cost or price analysis techniques as described in FAR Subpart 15.6 and FAR Subpart 15.8.

2.4.4.3 Completeness. The Government will evaluate completeness by assessing the level of detail provided in cost data and documentation, and assessing the traceability of estimates.

2.5 General Considerations. The following general considerations are listed in order of importance:

1. Pre-EMD price.

2. The Offeror's acceptance of contractual terms and conditions.

3. The extent to which the Offeror identifies and commits to small and small disadvantaged business contracts.

2.5.1 Pre-EMD Price. For the Pre-EMD price, the Government will assess the realism, reasonableness, and completeness as defined in paragraphs 2.4.4.1 - 2.4.4.3. The Government will also assess the MPC of the instant contract price. The Pre-EMD price MPC will consider Government Furnished Property (GFP), base support, and technical risks or uncertainties.

2.6 Evaluation Standards. The evaluation standards for each area and factor are provided below. Note: A reference to a specific template(s) within the standards does not imply that the template(s) will be the sole source of information to answer the standard.

2.6.1 Area 1: Affordability. The Government will consider the Offeror's LCCE (50% CL) and the MPC against the recurring cost reduction threshold of 25% (with an objective of 50%) from $20.6B (FY95$) and the EMD cost target of $1.4B (FY95$). The Offeror's LCCE (50% CL), the Government's MPC, and the Government's assessment of Performance Risk comprise the Affordability component of the SSA's integrated assessment. (Template No. 17)

2.6.2 Area 2: User Requirements

2.6.2.1 Factor 1: Performance

STANDARD 1: MASS TO ORBIT. The system design has the ability to deliver the Government portion of LCCV SPD Annex A, Table 1b, National Mission Model (NMM) reference missions to required orbit(s). This standard is met if:

a) The EELV system is capable, with a 99% assurance, of delivering the required mass to the delivery orbit of the Government portion of the reference missions cited in the NMM). (Template No. 9)

b) Launch vehicle dry weight growth margins are commensurate with the maturity of the hardware and the phase of design.

STANDARD 2: PERFORMANCE MARGIN. The system design provides some level of margin over the payload weights provided in the NMM. This standard is met if the system design provides, with a 99% assurance, for some specified level of margin over the payload weights provided in the NMM. (Template No. 9)

STANDARD 3: DELIVERY ACCURACY. The LV system will be capable of providing orbital parameter accuracies within the 3 sigma values specified in Table 1, Orbital Parameter Accuracies, of the LCCV SPD. This standard is met if: (Template No. 10)

a) The orbital parameter accuracies at the final orbit injection point for each payload mission are within the 3 sigma values specified in Table 1 of the LCCV SPD.

b) During park orbit or transfer orbit coasts, the LV is capable of orienting the upper stage/payload to any desired attitude and holding attitude to within 6o (3 sigma).

c) During park orbit or transfer orbit coasts, the LV is capable of providing a commanded roll rate, in either direction, of up to 2.0 degrees per second.

d) Prior to separation, the LV is capable of pointing the upper stage/payload to any desired attitude and either minimizing all rotation rates (3-axis stabilized missions) or providing a spin about the longitudinal axis (spin-stabilized missions) with attitude errors, rotation rates, spin rates, and spin axis orientation accuracies as specified in Section 3.2.1.2.2 of the LCCV SPD.

STANDARD 4: SCHEDULE DEPENDABILITY. The LV system (ground and launch vehicle segments) shall provide the highest practical probability of launching within

-3 to +10 calendar days of the scheduled launch time. Attributable delays include EELV equipment, processing, and weather related delays. This standard is met if:

a) The Offeror defines the probability of launching within the -3 to +10 day window. (Template No. 12)

b) The Offeror has used an appropriate analysis or simulation methodology, with justifiable inputs, in establishing the probability of on-time launch. The methodology takes into consideration outside influences such as weather conditions, daylight restrictions and electromagnetic radiation, and component/equipment failures during launch processing.

STANDARD 5: LAUNCH RATE CAPACITY AND RESILIENCE. The EELV system has the flexibility to efficiently operate over a range of potential processing rates and provides the basic launch rate capacity to support the Government portion of the NMM requirements. This standard is met if:

a) The system has sufficient throughput to support the range of Government requirements as specified in the Government portion of the NMM (LCCV SPD Annex A, Table 1b), and provides additional launch rate capacity for resilience. (Template No. 11)

b) The launch rates are achievable taking into account weather delays, launch range conflicts with other spacelift systems, and other typical launch delays such as processing task timeline variations, ground support system downtimes, and unscheduled vehicle maintenance activities.

c) The Offeror's maintainability and maintenance concepts emphasize rapid fault detection and isolation, and are commensurate with launch rate and schedule dependability requirements.

STANDARD 6: LAUNCH RESPONSIVENESS. To ensure scheduled launch timeliness and to accommodate unplanned launches, the LV shall be capable of rapidly and repeatedly responding to requests for launches. This standard is met if:

a) The LV system is capable of supporting an unscheduled DoD launch in less time than the current processing timelines of 45 days for MLV and 180 for HLV. (Template No. 12)

b) The response capability is based on a timeline analysis which includes processing the vehicle, mating the launch vehicle with the payload, and final processing for launch. (Template No. 12)

STANDARD 7: CRISIS REPLENISHMENT (SURGE). The EELV system shall include a capability to surge above the scheduled number of missions in the NMM. This standard is met if the Offeror defines and substantiates the number of extra missions and the associated time to launch these missions in response to a crisis situation. (Template No. 12)

STANDARD 8: PAYLOAD FLIGHT ENVIRONMENT. The EELV system provides a suitable flight environment for the Government payloads of the NMM. This standard is met if:

a) The acoustic environment within the fairing is commensurate with the levels acceptable by the Government payloads of the NMM, as delineated in LCCV SPD Annex C.

b) The maximum shock spectrum at the payload interface is compatible with the levels acceptable by the Government payloads of the NMM, as delineated in LCCV SPD Annex C.

2.6.2.2 Factor 2: Reliability

STANDARD: VEHICLE Design Reliability. The Offeror's concept meets LCCV SPD vehicle design reliability requirements. This standard is met if:

a) Design reliability for each LV, including hardware, software, and firmware, from launch commit through CCAM is at least 0.98 (at a 50% confidence level) for the LV. (Template No. 14)

a. The methodology, models, and types of input/output data used for the estimation of design reliability, are described in sufficient detail, along with rationale, to establish the credibility of the approach.

c) The LV is designed to maintain pogo stability regardless of payload configuration.

2.6.2.3 Factor 3: Standardization

STANDARD 1: LAUNCH PAD. At each launch site, each EELV launch pad is capable of launching all vehicle configurations required for the NMM missions to be launched from that site. (Template No. 15)

STANDARD 2: SYSTEM. The system maximizes, to the extent practicable, standardization in launch vehicles, infrastructure, equipment, processes, and operations procedures, and the Offeror provides sound rationale for any non-standard approaches. (Template No. 15)

2.6.3 Area 3: Program Execution

2.6.3.1 Factor 1: Program Executability (Pre-EMD and EMD)

STANDARD 1: PROGRAM INTEGRATION. Plans for the development, integration, test and evaluation, production, and activation of the proposed system concept are comprehensive and executable within program cost and schedule parameters. This standard is met if:

a) The program schedule depicts a complete view of the key activities and events leading to full flight rates, depicts the critical path, and shows logical phasing of key program events, tests, and demonstrations that will satisfy the program cost, schedule, and performance requirements.

b) Critical development, test, and integration activities are identified and described in sufficient detail that logically supports the proposed efforts.

c) The proposed program activities are realistic in scope and consistent with the Offeror's LCCE.

d) The Offeror's approach complies with the Department of Defense Policy on the Use of Former Soviet Union Propulsion in Space Launch Vehicles (available as a CFI reference document) and the "Manufactured in the U.S." requirement (CFI Annex 4 SCR H.5).

STANDARD 2: EELV TRANSITION. Plans to transition from current ELV operations to a fully capable EELV system are comprehensive and executable within program cost and schedule parameters. This standard is met if:

a) The Offeror's approach outlines a logical sequence of events/undertakings which leads to the transition and, as a minimum, fully supports the launch of the Government portion of the NMM.

b) The Offeror's approach minimizes the impact to the operation of current systems. Where any dual use of facilities is proposed, the Offeror provides sound rationale and justification.

c) A phased approach to activation of required facilities is provided. The approach supports both system test flights and forecasted operational launch requirements.

STANDARD 3: DEVELOPMENT, TEST, AND LAUNCH INFRASTRUCTURE. Plans for the development and/or use of infrastructure required to support development, test, and launch of the proposed vehicle family are comprehensive and executable within program parameters. This standard is met if:

a) Existing contractor and Government resources and/or plans to acquire additionally-needed capabilities to fully support the development program needs are described and are consistent with the proposed concept and execution approach.

b) An understanding of available Government test and launch site infrastructure/capabilities is demonstrated, and a plan to use these capabilities is presented.

c) Planning to complete and coordinate facility design necessary to support required construction start dates upon commencement of the EMD Module is presented.

d) Planning to complete facility construction within the EMD Module is presented.

e) Base infrastructure improvements to accommodate the proposed concept are identified and defined.

STANDARD 4: INTEGRATED LOGISTICS SUPPORT (ILS). An ILS program has been defined that will ensure a disciplined, iterative, and effective approach to the management and technical activities necessary to accomplish operations and support for EELV. The standard is met if:

a) All logistics support considerations are integrated into system equipment design.

b) The Offeror's operations and support concept supports readiness objectives (e.g., timeliness, responsiveness) and is consistent with the AFSPC operations and support concept.

STANDARD 5: PROGRAM RISK AND MITIGATION. A plan for managing and mitigating significant internal and external program risks is provided. This standard is met if:

a) The plan includes, but is not limited to, planning, organizing and implementing a risk management program.

b) Significant internal and external program risks are identified and prioritized.

c) The supporting rationale for the selection and prioritization of these risks is consistent with concept design and maturity, proposed technologies, and other program considerations.

d) Risks associated with meeting the threshold requirements of the Pre-EMD SPD contained in the model contract are addressed.

e) The Offeror describes the activities, and associated resource requirements and schedules, to effectively mitigate the identified risks.

2.6.3.2 Factor 2: Pre-EMD Management

STANDARD 1: INTEGRATED TASK AND MANAGEMENT PLAN (ITAMP). The ITAMP reflects an Integrated Product Development (IPD) approach and is a single plan for the entire Pre-EMD effort, including EELV efforts of associate and/or major subcontractor. This standard is met if:

a) The ITAMP reflects an IPD approach, containing appropriate accomplishments and criteria for each event, consistent with the Offeror's overall concept.

b) The ITAMP contains all activities necessary to support ITAMP tasking required to successfully complete the Pre-EMD Module.

c) The ITAMP adequately describes the work effort which satisfies, and is clearly traceable to, the SOO and Pre-EMD SPD contained in the model contract, and the Offeror's WBS.

d) Proposed availability dates for EELV program information are adequate to effectively execute the proposed Pre-EMD program and support Government agency requirements.

e) The offeror clearly identifies lines of control and presents a clear understanding of the IPT structure necessary to effectively execute the Pre-EMD program. Additionally, the offeror presents an approach to effectively integrate individual IPTs to ensure adequate communication and issue resolution.

STANDARD 2: INTEGRATED MASTER SCHEDULE (IMS). The IMS includes schedules necessary to achieve each event and significant accomplishment identified in the ITAMP, and is aligned with the ITAMP. This standard is met if:

a) Events and significant accomplishments are shown which are traceable and consistent with the ITAMP, and are sufficient to support, track, and manage the Pre-EMD Module.

b) Detailed, feasible, and executable time spans for the significant activities are provided.

c) The Offeror highlights the Pre-EMD critical path.

STANDARD 3: SOFTWARE DEVELOPMENT APPROACH. The Offeror's software development processes, standards, policies, methodologies, tools and facilities provide a disciplined, systematic and managed approach to software development across the EELV contractor team. This standard is met if:

a) The Software Development Capability Evaluation (SDCE) questionnaire responses define processes, standards, policies, methodologies, tools, technologies, and facilities that the Offeror can use effectively in developing EELV software that satisfies performance, quality and sustainment requirements.

b) The software development activities specified in the ITAMP are sufficient to begin developing EELV software that satisfies schedule, performance, quality and sustainment requirements.

2.6.3.3 Factor 3: Producibility/Manufacturing

STANDARD 1: REDUCTION OR ELIMINATION OF MRB PROCESS. The proposed approach to system design and development, coupled with the implementation of process controls, will significantly reduce or eliminate the need for a Material Review Board (MRB) process and reduce costs. This standard is met if:

a) The Offeror presents a manufacturing approach which addresses concurrent engineering, especially the approach used to show how manufacturing considerations influence the design.

b) The Offeror identifies key manufacturing processes and any alternatives, including rationale which shows how the proposed manufacturing and quality processes will reduce costs.

c) The Offeror provides a sound approach to control variability which will produce compliant hardware.

d) The Offeror describes any demonstrations necessary to validate manufacturing improvements that will lead to a lower LCCE.

STANDARD 2: MANUFACTURING CAPACITY. The Offeror's approach provides adequate and balanced manufacturing capacity, facilities, and material handling capability. This standard is met if: (Template No. 16)

a) The Offeror provides known C_pk values, and a plan to determine unknown C_pk values, for critical manufacturing processes.

b) The Offeror provides an estimate of factory sizing which considers build schedules, processes to mitigate identified potential bottlenecks, critical process capabilities, and process yields.

c) The Offeror discusses projected plant/test infrastructure requirements and presents a plan to acquire new, or modify existing, capabilities as required.

STANDARD 3: TOTAL COST OF QUALITY. The standard is met if the Offeror identifies appropriate actions that will be conducted during Pre-EMD to provide a comprehensive approach, that will be in place at the start of EMD, for reporting and reducing the Total Cost of Quality. (Template No. 16)

2.6.4 Area 4: Commercial Launch Considerations

STANDARD: The Offeror's commercial management plan shows synergy with Goverment requirements and describes how they will manage and finance EELV commercially. This standard is met if:

a) The Offeror's approach capitalizes on the EELV system developed for the Government to capture commercial payloads. As a minimum, the approach includes when commercial launches will begin, projected annual launch rates for forecasted commercial launches, and corporate commitment and resources available.

b) The Offeror's approach includes a process to identify and satisfy commercial customer requirements.

c) The Offeror's approach addresses and resolves constraints in achieving their commercial program. As a minimum, the Offeror addresses any infrastructure, launch, manning, manufacturing, capacity, and environmental constraints.

d) The Offeror identifies the potential benefits to the Government resulting from anticipated commercial launches.

This page intentionally left blank.

CFI Section 3 - Proposal Preparation Instructions

(1) Pursuant to FAR 52.252-1, "SOLICITATION PROVISIONS INCORPORATED BY REFERENCE," the following provisions are incorporated herein by reference.

I. FEDERAL ACQUISITION REGULATION (1991 EDITION) (48 CFR CHAPTER 1) SOLICITATION PROVISIONS:

PARAGRAPH	TITLE
52.211-6	LISTING OF OTHER THAN NEW MATERIAL, RESIDUAL INVENTORY, AND FORMER GOVERNMENT SURPLUS PROPERTY (MAY 1995) (FAC 90-32)
52.215-5	SOLICITATION DEFINITIONS (JUL 1987)
52.215-7	UNNECESSARILY ELABORATE PROPOSALS OR QUOTATIONS (APR 1984)
52.215-8	AMENDMENTS TO SOLICITATIONS (DEC 1989)
52.215-9	SUBMISSION OF OFFERS (DEC 1989)
52.215-10	LATE SUBMISSIONS, MODIFICATIONS, AND WITHDRAWALS OF PROPOSALS (AUG 1996) (FAC 90-39)
52.215-12	RESTRICTION ON DISCLOSURE AND USE OF DATA (APR 1984)
52.215-13	PREPARATION OF OFFERS (APR 1984)
52.215-14	EXPLANATION TO PROSPECTIVE OFFERORS (APR 1984)
52.215-15	FAILURE TO SUBMIT OFFER (JUL 1995)
52.215-16	CONTRACT AWARD (OCT 1995) ALTERNATE II (OCT 1995)(FAC 90-31)
52.215-30	FACILITIES CAPITAL COST OF MONEY (SEP 1987)
52.215-41	REQUIREMENT FOR COST OR PRICING DATA OR INFORMATION OTHER THAN COST OR PRICING DATA (OCT 1995), ALTERNATE IV (OCT 1995) (FAC 90-32)
52.216-1	TYPE OF CONTRACT (APR 1984) (In the blank space insert "Firm-Fixed Price")
52.222-24	PREAWARD ON-SITE EQUAL OPPORTUNITY COMPLIANCE REVIEW (APR 1984)
52.232-13	NOTICE OF PROGRESS PAYMENTS (APR 1984)
52.252-1	SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (JUN 1988)

II. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT (1991 EDITION) (48 CFR CHAPTER 2) SOLICITATION PROVISIONS:

PARAGRAPH	TITLE
252.204-7001	COMMERCIAL AND GOVERNMENT ENTITY (CAGE) CODE REPORTING (DEC 1991)
252.209-7002	DISCLOSURE OF OWNERSHIP OR CONTROL BY A FOREIGN GOVERNMENT (SEP 1994)
252.227-7017	IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR DISCLOSURE RESTRICTIONS (JUN 1995) (DAC 91-8)
252.227-7028	TECHNICAL DATA OR COMPUTER SOFTWARE PREVIOUSLY DELIVERED TO THE GOVERNMENT (JUN 1995)

(2) THE FOLLOWING PROVISIONS OF THE FAR ARE APPLICABLE TO THIS SOLICITATION:

52.233-2 SERVICE OF PROTEST (OCT 1995)

(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the General Accounting Office (GAO) shall be served on the Contracting Officer (SMC/MVK, 2420 Vela Way, Suite 1467-A2, Los Angeles AFB, CA 90245-4659) by obtaining written and dated acknowledgment of receipt from the Contracting Officer, Joyce Mullenbach.

(b) A copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.

52.252-5 AUTHORIZED DEVIATIONS IN PROVISIONS (APR 1984)

(a) The use in this solicitation of any Federal Acquisition Regulation (48 CFR Chapter 1) provision with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the provision.

(b) The use in this solicitation of any DoD FAR Supplement (48 CFR Chapter 2) provision with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation.

(3) THE FOLLOWING PROVISIONS OF THE DOD FAR SUPPLEMENT ARE APPLICABLE TO THIS SOLICITATION:

252.211-7002 AVAILABILITY FOR EXAMINATION OF SPECIFICATIONS, STANDARDS, PLANS, DRAWINGS, DATA ITEM DESCRIPTIONS, AND OTHER PERTINENT DOCUMENTS (DEC 1991)

The specifications, standards, instructions, plans, drawings, data item descriptions, and other pertinent documents cited in this solicitation are not for distribution but may be examined at the following location:

Space and Missile Systems Center/MV 2420 Vela Way, Suite 1467-A2 Los Angeles AFB, CA 90245-4659

(4) THE FOLLOWING PROVISIONS OF THE AIR FORCE FAR SUPPLEMENT ARE APPLICABLE TO THIS SOLICITATION:

5352.215-9000 FACILITY CLEARANCE (MAY 1996) - AF FAR SUPPLEMENT

The offeror must possess, or acquire prior to award of a contract, a facility clearance equal to

the highest classification stated on the Contract Security Classification Specification (DD Form

254) attached to this solicitation as Annex 8.

(5) THE FOLLOWING PROVISIONS OF THE AIR FORCE MATERIEL COMMAND FAR SUPPLEMENT ARE APPLICABLE TO THIS SOLICITATION:

5352.215-9009 SUBMISSION OF CERTIFIED COST AND PRICING DATA (OCT 1994) --AFMC FAR SUPPLEMENT

(a) It is anticipated that pricing of this action will be based on adequate price competition; therefore, the Offeror is not required to submit certified cost or pricing data. However, if after receipt of proposals it is determined that adequate price competition does not exist, certified cost or pricing data (see FAR 15.804-4) will be required. Use of a Standard Form 1411 for the submission of the offer and any supporting data is required only if certification is required.

(b) If it is determined that adequate price competition does not exist, the Offeror shall provide current, complete and accurate cost or pricing data within 30 calendar days after receipt of the Contracting Officer's request.

5352.215-9014 ACQUISITION OMBUDSMAN (JUL 1992) --AFMC FAR SUPPLEMENT

An Ombudsman has been appointed to hear concerns from the Offeror and potential Offerors during the proposal development phase of this acquisition. The purpose of the Ombudsman is not to diminish the authority of the program director or contracting officer, but to communicate Contractor concerns, issues, disagreements, and recommendations to the appropriate Government personnel. When requested, the Ombudsman will maintain strict confidentiality as to the source of the concerns. The Ombudsman does not participate in the evaluation of proposals or in the source selection process. Interested parties are invited to call Mr. Leslie L. Bordelon at (310) 363-3818. The Ombudsman should only be contacted with issues or problems that have been previously brought to the attention of the contracting officer and could not be satisfactorily resolved at that level.

(6) THE FOLLOWING ADDITIONAL PROVISIONS ARE APPLICABLE TO THIS SOLICITATION:

EVALUATION BY NON-GOVERNMENT PERSONNEL

Offerors are advised that personnel from The Aerospace Corporation; Tecolote Research, Inc. (TRI); and bd Systems may assist the Government during the evaluation of proposals. These persons shall be authorized access to only those portions of the proposal data and discussions that are necessary to enable them to provide advice on specialized matters or on particular issues. They shall be expressly prohibited from scoring, ranking or recommending the selection of a source.

CALL FOR IMPROVEMENT

The term "Call for Improvement (CFI)", has the same force and effect as the term "Solicitation" as defined in FAR Provision 52.215-5.

NON-Low Cost Concept Validation (LCCV) Offeror requirements

In addition to submitting a proposal in accordance with the instructions in the EELV Pre-EMD CFI, Offerors who are not participants in the Government's EELV LCCV Module must satisfy the requirements of the LCCV contract at a maturity level commensurate with the LCCV contractors by submitting data equivalent to the deliverables required by the LCCV Contract. These items include authenticatable A-level specifications and other tailored Preliminary Design Review-equivalent documentation. This documentation will be used by the Government in assessing the Non-LCCV Offeror's Pre-EMD proposal risk, as defined in CFI paragraph 2.4.2. These requirements are outlined in file NONLCCV.DOC which can be found on the EELV Electronic Bulletin Board (EBB). Detailed instructions for preparation and submission of this required information can be found in the LCCV Request for Proposal, and all amendments thereto, which is located on the EELV Electronic Bulletin Board (EBB). Refer to CFI paragraph 3.1.10 for information on accessing the EBB. Non-LCCV offerors must submit this information no later than 10 calendar days prior to the Pre-EMD proposal due date to the following address:

SMC/MVK

2420 Vela Way, Suite 1467-A2

Los Angeles AFB, CA 90245-4659

Attn: Joyce Mullenbach

Submit the required information in the following medium: 1 paper copy and 4 electronic copies on CD-ROMs. The electronic copies shall contain the required information in Adobe Acrobat Portable Document File (PDF) format, with the exception of the Life Cycle Cost Estimate, which shall be submitted as specified in the LCCV RFP as supplemented by information in file LCCE70%.PDF, available on the EBB.

3.1 General Information

3.1.1 Funding Profile

3.1.1.1 Pre-EMD Module. The funding profile below covers the basic effort (CLIN 0001) and related data (CLIN 0002) for the EELV Pre-EMD Module. The Government intends to award two incrementally-funded Firm Fixed Priced contracts; total value of each contract will not exceed $60 million (TY$).

FY97 FY98

$28M $32M

3.1.1.2 EMD Module. For planning purposes, total EMD contract funding projected through FY06 is approximately $1.6B (TY$), or approximately $1.4B (FY95$). This amount, which is subject to change, reflects total contract funding available, to include but not limited to the basic contract, potential award fee pools, and potential incentives.

3.1.2 Oral Presentations. Each Offeror is invited to conduct an oral presentation on 30 Sep 96. The Offeror must contact the Procuring Contracting Officer (PCO), Joyce Mullenbach, (310) 336-4578, no later than 23 Sep 96 to schedule a presentation time. The presentation will be a maximum of 45 minutes. Offerors should, as a minimum, provide an overview of the Offeror's proposal content and layout. The presentations will not be evaluated. Offerors should coordinate audiovisual equipment necessary for their presentation in advance. Provide one electronic copy of the presentation material in Adobe Portable Document File format. The Offeror will be limited to five company/team representatives. The presentations will take place in Los Angeles, CA, Aerospace Complex, bldg A-2, room 1226.

3.1.3 Proposal Brevity. The preparation instructions are intended to elicit brief, specific responses to the CFI; however, stating the Offeror understands and complies with this effort or paraphrasing the statements of the CFI is inadequate. Phrases such as: "Standard procedures will be employed" and "well known techniques will be used" are also inadequate.

3.1.4 Requirements Resolution. If the Offeror believes the requirements in these instructions contain an error, omission, or are unsound, the Offeror shall immediately contact the PCO in writing with supporting rationale. The PCO's fax number is (310) 336-4198.

3.1.5 Classified Proposals. The Government anticipates proposals will not require the inclusion of classified material. PCO approval is required prior to submission of any classified information. If it is necessary to include classified material (no higher than Secret), the classified portions of the individual proposal parts shall be submitted under a separate cover. Classified information generated for this proposal shall be submitted (hardcopy only) in accordance with Executive Order (EO) 12958, Classified National Security Information, for new classification, declassification, and marking. DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), is currently being revised to reflect EO 12958 requirements. Existing classified documents shall not be remarked. Classified portions shall be counted against the total page count for the respective file, if applicable.

3.1.6 Alternate Proposals. The Government will not accept alternate proposals.

3.1.7 Unrealistic Proposals. Unrealistically low proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the Offeror does not understand the requirement or the Offeror has made an unrealistic proposal.

3.1.8 Reference Information. The EELV Electronic Bulletin Board (EBB) and the EELV technical library are resources for obtaining program information. The following reference material is available to assist the Offerors in preparing their proposals. Offerors may access these documents at any time via the EELV EBB.

-- EELV technical library listing

-- FSU policy letter

-- Operations and Support Concept (dated 26 Jul 96)

-- Integrated Task And Management Plan (ITAMP) instructions

-- Work Breakdown Structure (WBS) instructions

-- Life Cycle Cost Estimate (LCCE) at the 70% confidence level instructions (updated)

-- National Industrial Security Program Operating Manual (NISPOM)

-- LCCV objectives

-- LCCV Request For Proposal and amendments thereto

-- Non-LCCV Offeror requirements

-- Commonly used EELV Acronyms

-- Action item releases

3.1.9 EELV Home Page. The home page contains the CFI and any amendments thereto and general program information. The program office Point Of Contact (POC) for the home page is Lt Rob Morris, (310) 336-4592. The address for the EELV home page is http://www.laafb.af.mil/SMC/MV/eelvhome.htm.

3.1.10 Electronic Bulletin Board. The Government will continue to use the EELV EBB for information designated as For Official Use Only, contractor proprietary information, the CFI and any amendments thereto, and reference information the Offeror may require to prepare its proposal. The program office POC for the EBB is Lt Rob Morris, (310) 336-4592. Potential Offerors may contact Lt Morris to establish an account on the EBB.

3.1.11 EELV Technical Library. The EELV technical library also contains program reference information, mostly in paper format. An index of library information can be found on the EBB. The library is located at Space and Missile Systems Center, Los Angeles AFB, Aerospace complex, in Bldg. A-2, rm 1255. The process for accessing the library is outlined in EELV library letter dated 13 Nov 95 which can be found on the EBB. The POC for the technical library is Lt Lee Bosch, (310) 336-4475.

3.1.12 Proposal Testing. The Offeror is encouraged to test the proposals on the Government's hardware configuration during the period 11-12 Sep 96. Each Offeror will have up to two hours available for any testing required. Starting on 4 Sep 96, contact Ms Joyce Mullenbach, Contracting Officer, (310) 336-4578, to schedule a time. On 19 Sep 96, a one hour retest period is available for each Offeror, if necessary. Contact Ms Mullenbach by 12 Sep 96 to schedule a retest time.

3.2 Proposal Delivery Information

3.2.1 Response Date. Submit proposals in response to this CFI by 1500 Pacific Daylight Savings Time, 30 Sep 96. Proposals received after this time shall be treated in accordance with the restrictions of FAR 52.215-10. Address the proposal as follows:

SMC/MV

ATTN: Ms Joyce Mullenbach

Procuring Contracting Officer

2420 Vela Way, Ste 1467-A2

Los Angeles AFB CA 90245-4659

3.2.2 Price Limitation. Submit a Pre-EMD Module proposal not to exceed $60 million firm fixed price. The Pre-EMD contract-funded effort described in the Pre-EMD Integrated Task And Management Plan (ITAMP) must correspond to the proposed firm fixed price. Costs incurred by the contractor in pursuit of any parallel activities are not required for contract completion and are not a part of the contract price (except to the extent that IR&D costs may be allocated per FAR Part 31), and are not allowable direct costs to the Pre-EMD contract or any resultant follow-on contracts. Parallel activities shall be depicted in the ITAMP in accordance with the instructions provided in paragraph 3.7.6.2.1.4.

3.2.3 Transmittal Letter. Include a hardcopy transmittal letter to forward the proposal to the EELV System Program Office. This letter, not to exceed two pages, will be used adminstratively and will not be evaluated. The transmittal letter shall include a statement that the proposal will remain valid for no less than 120 calendar days from the date the proposal is due. The transmittal letter shall also include a statement that the electronic media by which the offer is transmitted to the Government contains no "virus" or self-replicating programs that have the ability to maliciously or non-maliciously destroy data or deny services, and that the media, in its entirety, has been cleaned with an "anti-virus" software program designed to detect and delete virus programs. The Offeror shall also provide the anti-virus program name and version number.

3.2.4 Proposal Submission

3.2.4.1 Electronic copies. Submit four duplicate copies of the proposal, each on CD-ROM, each containing the information outlined in paragraphs 3.4 - 3.6. Refer to paragraphs 3.2.1, 3.7.2.2, and 3.7.9 for additional proposal files which are required to be submitted either before or after the proposal submittal on 30 Sep 96. These files, if submitted, shall be on an MS Windows-compatible diskette(s) or a CD-ROM.

3.2.4.2 Paper copy. Submit one paper copy of the complete proposal, including the proposed model contract (including SF 33, SF 1448, and DD Form 254), representations and certifications, and GFP/Base Support permission slips, with all required signatures. This copy must be clearly marked as the original. Submit this copy in the following order: SF 1448, SF 33, followed by files as shown in paragraphs 3.4, 3.5, and 3.6. Provide this paper copy in the minimum number of standard three-ring binders necessary to hold the files as one collection of files. Any extra paper copies will not be accepted. A paper copy of files provided before or after the proposal submittal date (RISKACT2.PDF, or SDCEANSR.PDF) shall be provided with the submission of those files.

3.3 Specific Instructions for Electronic Proposal Preparation. To enable the Government to successfully view the proposals electronically, the Offeror shall submit portions of the proposal files in the Adobe Portable Document File (PDF) format, as shown in paragraphs 3.4, 3.5, and 3.6. The Offeror shall generate "thumbnails" within each PDF file. The Offeror has the option of generating "bookmarks" within each PDF file as well. The minimum requirement for hypertext links is a table of contents linked to each file provided in the proposal. Additional hypertext links within the proposal are at the Offeror's discretion. The use of bookmarks or additional hypertext links will not influence the evaluation. The PDF file has a built in security function. The Offeror shall set all security options in each PDF file to "allowed".

3.3.1 Font and Page Setup. Text font shall be Times New Roman, 12 point vertical character height, black and single space. Hypertext links shall be the same font size but may be any color. Kern modification or other techniques to reduce character size or spacing are prohibited. All text within illustrations and tables shall be Arial, legible, and at least 8 points in height. Figure titles shall be at least 10 points in height. These restrictions do not apply to the forms provided by the Government in this CFI (SF 33, DD Forms 254 and 1423-1). The page limitation is based on 8.5x11 paper size with 1" margins on all sides and page set up 100%.

3.3.2 Other Requirements. The Offeror shall not embed sound or video files into the proposal files. Minimize the use of scanned images and keep embedded graphics as simple as possible. No foldouts are allowed.

3.3.3 Proposal Format and Structure. Each CD-ROM shall include proposal files in the root directory as well as in two separate file directories, as outlined in paragraphs 3.4 - 3.6. Each file directory shall contain a cover page (DIR*CVR.PDF, where * is 1 or 2 based on the file directory). Additionally, the Offeror shall provide a list of acronyms (ACRONYM.PDF) in File Directory 1. The Offeror shall note the file extension of each file to determine the proper format (i.e., FILE.DOC is a Word file). Note: The following two required proposal files are not listed in either directory since they have different submittal dates than the proposal: RISKACT2.PDF (update of late risk reduction activities) and SDCEANSR.PDF (SDCE response).

3.3.4 Page limitations. Any page count limitations are shown in paragraphs 3.5 and 3.6. Refer to paragraph 3.7.2.2 for the page count limit for late risk reduction activities information. Proposal templates, and any listings of figures, title pages, or indexes will not apply against the page count.

3.4 CD-ROM Root Directory. Provide three files in the root directory of the CD-ROM. The first is a PDF file (TBLCONT.PDF) that serves as a table of contents for the proposal information. The Offeror shall provide the capability to "jump" from this file using hypertext links to all other files found on the CD-ROM. The second file (PROPINFO.PDF) shall contain information to assist the Government evaluators in navigating through the proposal files. For example, the Offeror should explain any hypertext links above the Government's minimum requirements in this file. The third file is a "tab delimited" ASCII file (KTRINFO.TXT) containing the following information with a tab between each entry. For blank entries, put in an extra tab. Submit the file in the following exact order:

INFORMATION REQUIRED	SAMPLE INPUTS
Name of Offeror	XYZ Inc
Name of Official Point of contact (POC) for all correspondence	Ms. Jane Smith
Title of POC	President
POC Phone Number	310-555-1234x6666
E-Mail Address (if available)	contractor.com
Address Line 1	123 West St
Address Line 2	Suite 500
Address Line 3	Mail Stop 422
Address Line 4	blank
City	Any town
State	Any state
Zip Code	11111-1111
Title of Proposal	EELV Pre-EMD Module
Classification of Proposal	Unclassified
Proposal Synopsis	Limit to 25 words or less

SAMPLE FILE: XYZ Inc[tab]Ms. Jane Smith[tab]President[tab]310-555-1234x6666 [tab]contractor.com [tab]123 West St[tab]Suite 500[tab]Mail Stop 422[tab][tab]Any town[tab]Any state [tab]11111-1111[tab]EELV Pre-EMD Module[tab]Unclassified[tab]Limit to 25 words or less.

3.5 File Directory 1 - Proposal Information. This directory shall include the following files. Specific instructions for these files can be found in the referenced CFI paragraph.

File Name	File contents	CFI Reference	Page limits
DIR1CVR.PDF	Cover page for this file directory	3.3.3	N/A
ACRONYM.PDF	List of acronyms for entire proposal	3.3.3	N/A
	GENERAL INFORMATION
TEMPLATE.PDF	Templates	2.6, 3.7.1, 3.7.4, 3.7.5, 3.7.6.1	Per instructions provided with templates
OFFRINFO.PDF	System concept overview and additional Offeror information	3.7.1	10 pg
RISKACT1.PDF	Late risk reduction activities information	3.7.2.1	2 pg per activity
PASTPERF.DOC	Relevant past performance information	3.7.3	16 pg
	AFFORDABILITY AREA
LCCE.XLS	LCCE at point estimate level, 50% CL and 70% CL	3.7.4	None
LCCERATL.PDF	LCCE update narrative of changes (if applicable)	3.7.4	10 pg
	USER REQUIREMENTS AREA
USERREQT.PDF	User Requirements Area information	3.7.5	20 pg
	PROGRAM EXECUTION AREA
PRGMEXEC.PDF	EELV development plan	3.7.6.1	40 pg
ITAMP.PDF	Pre-EMD ITAMP	3.7.6.2.1	None
IMS.PDF	IMS	3.7.6.2.2	None
WBS.PDF	WBS	3.7.6.2.3	None
ITAMPRCM.PDF	ITAMP Requirements Correlation Matrix	3.7.6.2.4	None
	COMMERCIAL LAUNCH CONSIDERATIONS AREA
COMMERCL.PDF	Commercial Launch Considerations	3.7.7	10 pg
	GENERAL CONSIDERATIONS
PRCESUMM.PDF	Price and Labor Summary and supporting information	3.7.8.1	None
TASKLOAD.PDF	Price Realism Information	3.7.8.2	None
SUB_MATL.PDF	Subcontracts and Material Cost	3.7.8.3	None
GFPINFO.PDF	Government Furnished Property (GFP) Cost Information	3.7.8.4	None
BASESPT.PDF	Base Support Cost Information	3.7.8.5	None

3.6 File Directory 2: Model Contract, Attachments, and Supporting Documentation. This directory shall include the following files. Specific instructions for these files can be found in paragraph 3.8. Signatures are not required within the electronic files listed below. Instead, state somewhere in each applicable file that the original paper copy has been signed.

File Name	File contents	CFI Reference	Page limits
DIR2CVR.PDF	Cover page for this file directory	3.3.3	N/A
SF1448.PDF	Proposal Cover Sheet (Cost or Pricing Data Not Required)	Section 3, paragraph (1)	N/A
SF33.DOC	Solicitation, Offer, and Award (Section A)	3.8.1	N/A
MODELK.DOC	Model Contract (Sections B-J) with the following Attachments:	3.8.1	N/A
ATTACH1.DOC	Attach 1 - System Performance Document (SPD)	3.8.2.1	N/A
ATTACH2.DOC	Attach 2 - Work Breakdown Structure (WBS) Dictionary and Tree	3.8.2.2	None
ATTACH3.DOC	Attach 3 - Statement of Objectives	3.8.2.3	N/A
ATTACH4.DOC	Attach 4 - Subcontracting Plan	3.8.2.4	None
ATTACH5.DOC	Attach 5 - Rights In Technical Data - Noncommercial Items	3.8.2.5	None
ATTACH6.DOC	Attach 6 - Government Furnished Property (GFP)	3.8.2.6	None
ATTACH7.DOC	Attach 7 - Base Support	3.8.2.7	None
ATTACH8.DOC	Attach 8 - Contract Security Classification Spec (DD Form 254)	3.8.2.8	N/A
ATTACH9.DOC	Attach 9 - Design Review Definitions	3.8.2.9	N/A
EXHIBITA.DOC	Exhibit A - Contract Data Requirements List	3.8.2.10	None
	Supporting Documentation
APPEND1.PDF	Appendix 1 - Representations And Certifications	3.8.3.1	None
APPEND2.PDF	Appendix 2 - Exceptions	3.8.3.2	None
APPEND3.PDF	Appendix 3 - Authorized Representative	3.8.3.3	None
APPEND4.PDF	Appendix 4 - AMIS Letter	3.8.3.4	None
APPEND5.PDF	Appendix 5 - Location Information	3.8.3.5	None
APPEND6.PDF	Appendix 6 - GFP Written Permission Slips*	3.8.3.6	None
APPEND7.PDF	Appendix 7 - Base Support Permission Slips*	3.8.3.7	None
APPEND8.PDF	Appendix 8 - Approved DOD Test Program Subcontracting Plan*	3.8.3.8	None

* Provide these files if they are available electronically or can easily be digitized using a scanner. As a minimum, the Offeror shall provide this information in the paper copy.

3.7 Specific Instructions for Proposal Information

3.7.1 System Concept Overview and Additional Offeror Information. Complete templates #1 - #8 found in CFI Annex 2 and provide them as part of TEMPLATE.PDF. Additionally, provide a file (OFFRINFO.PDF) limited to ten pages which provides a system concept overview and additional information related to the Offeror's approach. The system concept overview is limited to five pages and shall also identify any concept or performance parameter changes since PDR. The remainder of the ten pages is left to the Offeror's discretion to highlight

significant features of the Offeror's approach. The Government will evaluate this information against all areas.

3.7.2 Late Risk Reduction Activities

3.7.2.1 Initial Submittal. These instructions apply to those tests or demonstrations identified by the Offeror and pre-approved by the EELV contracting officer prior to CFI release. Include a description of each test or demonstration and the associated objectives. Limit this file (RISKACT1.PDF) to two pages, to include text and illustrations, for each test or demonstration. (Total page count for this file will be based on the number of tests or demonstrations pre-approved by the contracting officer.)

3.7.2.2 Update. No later than 21 days after proposal submittal, provide an update to this information in a file titled RISKACT2.PDF which states the results of these activities and how the results impact or mitigate specific program risks. None of the information contained in the original file RISKACT1.PDF shall be changed. Limit file RISKACT2.PDF to two additional pages, to include text and illustrations, for each pre-approved test or demonstration (for a total of up to 4 pages for each test or demonstration). (Total page count for this file will be based on the number of tests or demonstrations pre-approved by the contracting officer.) Submittal of RISKACT2.PDF is subject to the late proposals clause (FAR 52.215-10). Submit this file on a CD-ROM or 3.5" MS Windows-compatible diskette to the address in paragraph 3.2.1.

3.7.3 Relevant Past Performance

3.7.3.1 Submit information relevant in demonstrating the Offeror's ability to perform the proposed effort. This file (PASTPERF.DOC) is limited to 16 pages. There is no limit on the number of contracts included in this file. This file shall include relevant Government contract and commercial efforts outside of the EELV program and any new teaming/subcontracting relationships. This shall include information relevant to all evaluation areas. This information may include data on efforts performed by other divisions, corporate management, and critical subcontractors or associates, if such resources will be brought to bear or significantly influence the performance of the proposed effort. For all prior efforts, including subcontractors and associates, provide the following information:

a. Company/Division name

b. Program title

c. Contracting agency/company

d. Contract number

e. A brief description of the contract effort, indicating development and/or production

f. Type of contract

g. Period of performance

h. Original contract $ value and current contract $ value

i. Original completion date and current completion date

j. Name, address and telephone number of current (or last if contract is completed) Government Program Director/Manager, Administrative Contracting Officer (ACO), and Procuring Contracting Officer (PCO), or for commercial contracts, the company program manager or point of contact

k. All applicable award fee ratings and percentages

3.7.3.2 Explain what aspects of the prior efforts are deemed relevant to the proposed effort. The Offeror is also permitted, but not required, to submit information on significant achievements or explain past problems it considers relevant to the proposed effort. Categorize the relevant past/present performance information into the specific evaluation areas (Affordability, User Requirements, or Program Execution) used to evaluate the proposal.

3.7.3.3 Any related experience, special tools, or additional resources making the Offeror uniquely qualified to perform the total effort shall be described.

3.7.4 Affordability Area. Complete template #17 provided in CFI Annex 2 and provide as part of file TEMPLATE.PDF. The Offeror's LCCE submitted during the LCCV Module (CDRL A001) will be considered the Offeror's LCCE for the Pre-EMD proposal. This LCCE will have been submitted at the point estimate level (with confidence level of the point estimate identified), the 50% Confidence Level (CL), and the 70% CL. The Offeror shall ensure its LCCE is consistent with the Operations and Support concept provided as a CFI reference document. The Offeror has the option of updating its LCCV Module LCCE with this proposal. If the Offeror chooses to do so, the Offeror shall submit the spreadsheets containing the LCCE at the point estimate level, the 50% CL, and the 70% CL (unlimited number of spreadsheets) accompanied by no more than 10 pages of narrative explaining the changes from the previously-submitted LCCE (LCCERATL.PDF). The LCCE at the point estimate level, 50% CL, and 70% CL shall be a stand-alone estimate and shall be provided as file LCCE.XLS. Complete instructions for preparing the LCCE can be found in file LCCE70%.PDF on the EELV EBB.

3.7.5 User Requirements Area. For the Performance, Reliability, and Standardization factors, complete templates #9 - #15 provided in CFI Annex 2. The templates are based on the LCCV System Performance Document. Provide the completed templates as part of file TEMPLATE.PDF. In addition, provide up to 20 pages (USERREQT.PDF) specifically addressing the evaluation standards in CFI Section 2 and any other information that serves to supplement the templates.

3.7.6 Program Execution Area

3.7.6.1 Program Executability and Producibility/Manufacturing Factors

Complete template #16 provided in CFI Annex 2 and provide the completed template as part of file TEMPLATE.PDF. Provide an EELV development plan for the Pre-EMD and EMD Modules which includes the following information. Limit this file (PRGMEXEC.PDF) to 40 pages. Refer to the Program Executability Factor and Producibility/Manufacturing Factor evaluation standards in CFI Section 2 for additional specific information required.

3.7.6.1.1 Describe the approach for completion of development; integration; test and evaluation; transition from current systems; activation of the proposed system; transition to, and initiation of, the production program; and integrated logistics support. Describe planned development, test, activation, and manufacturing planning activities. Address the consistency of this plan with the Offeror's LCCE. Provide an EELV program roadmap (schedule) which presents a complete view of the key events and significant accomplishments leading to full production capability and supports the following program milestone events. Highlight the development program critical path.

Downselect Design Review NLT 1 Mar 98

EMD Award NLT 1 Jun 98

Tailored CDR NLT 11 Dec 98*

First System Test Flight (MLV) (CCAS) Between 1 Oct 00 and 30 Jun 01

MLV First Operational Flight (CCAS) 1Q/FY02**

Second System Test Flight (HLV) (CCAS) 3Q/FY03

EMD Contract Completion One year after completion of the second system test flight***

* Approach must demonstrate the ability to complete a full system TCDR by this date. However, the Offeror may propose, with supporting rationale, an alternate date later than 11 Dec 98 for Government consideration

** Minimum of six months between first system test flight and first operational flight

*** The program office's intent is to complete EMD as shown. The Offeror may propose an alternative date through FY06 for contract completion.

3.7.6.1.2. Provide a plan for managing and mitigating program risks. Address significant risk items, including those identified by the Government under separate cover (if any) and any other program risks (at the discretion of the Offeror).

3.7.6.1.3 Identify SPD (CFI Annex 6) threshold requirements that cannot currently be met. Include mitigation plans for significant risk items.

3.7.6.2 Pre-EMD Management Factor

3.7.6.2.1 ITAMP. Submit an ITAMP (ITAMP.PDF). A complete description of the ITAMP can be found on the EELV EBB. The ITAMP describes in detail the activities to be accomplished during the Pre-EMD Module, including contractually-funded tasks, parallel activities, and associate and/or major subcontractor activities. The Offeror's proposed ITAMP will not be put on contract. Instead, the ITAMP will be a planning document by which the Offeror executes the program and the Government obtains the necessary insight into the Offeror's activities.

3.7.6.2.1.1 Introductory Information. Provide an overview of the ITAMP, including the ITAMP layout, explanations of activity numbering, and other similar information that will assist the Government in evaluating the ITAMP.

3.7.6.2.1.2 Key Activities. The ITAMP as a minimum shall contain sections for Events, Tasks, Significant Accomplishments (SA), and Accomplishment Criteria (AC). The Government will formally attend one Event. This event will be either a Downselect Design Review (DDR) or a Tailored Critical Design Review (TCDR), as the Offeror elects. Both of these reviews are defined in CFI Annex 3. ITAMP Tasks shall be directly traceable to the Statement of Objectives (SOO), Work Breakdown Structure (WBS) and Integrated Master Schedule (IMS). CDRL items or other program information to be made available or formally submitted to the Government shall be noted within the appropriate Task description, with the availability dates specified.

3.7.6.2.1.3 Pre-EMD Organization. Within the ITAMP, provide an overview of the Offeror's Pre-EMD organization. Include a discussion on the composition, authority, and responsibility of the Integrated Product Teams (IPTs) as well as the process for cross-IPT communication.

3.7.6.2.1.4 Parallel Activities. Parallel Activities are tasks or projects funded by Independent Research & Development (IR&D) or corporate investment that mitigate program risk, but are not required for contract completion. Costs incurred by the Contractor in pursuit of parallel activities (reference Pre-EMD ITAMP sections) during the Pre-EMD period of performance are not a part of the contract price (except to the extent that IR&D costs may be allocated per FAR Part 31), and are not allowable direct costs to the Pre-EMD contract or any resultant follow-on contracts. The Offeror shall identify and concisely describe any parallel activities that mitigate EELV program risk. The description shall include major schedule milestones, describe the scope of the effort, and provide a clear discussion of how the effort mitigates EELV program risk. Specify in the ITAMP that the cost for these activities are not directly chargeable against the Pre-EMD contract or any resultant follow-on contract.

3.7.6.2.1.5 Contractor Activities to Support Pre-EMD Objectives. The following key activities directly support the Pre-EMD objectives and shall also be included in the Offeror's ITAMP:

Refine internal and external interface definitions and establish interface management processes.

Plan for establishing a Total Cost Of Quality (TCOQ) tracking system. TCOQ is defined as those costs related to prevention, appraisal, and failures (internal and external).

Verify detailed design of proposed production processes using process capability/ process proofing results.

Develop combined DT&E/OT&E and dedicated IOT&E plans to support the Air Force Operational Test and Evaluation Center (AFOTEC) Operational Assessment(s).

Participate in and support the following working groups: payload integration, standard interface, test planning, operations and support, and range.

Secure all necessary construction, use, and environmental permits.

Identify and specify required range infrastructure modifications and improvements.

Implement programs for environmental protection, environmental compliance, system safety, human health, hazardous materials management (NAS 411 para. 4.3 and 5.2), and pollution prevention.

Establish a method to determine payload environments during flight.

Support "what-if" exercises.

3.7.6.2.2 Integrated Master Schedule (IMS). Provide an IMS (IMS.PDF) for the Pre-EMD Module, constructed to align with the ITAMP, that shows the calendar schedule necessary to achieve each event and SA described in the ITAMP. Highlight the critical path in red. Provide a legend for the scheduling symbology used. For scheduling purposes, the Offeror may consider the end of contract as an event.

3.7.6.2.3 Work Breakdown Structure (WBS). Provide a WBS (WBS.PDF), updated as necessary from the LCCV Module, to include a WBS dictionary and tree. Complete instructions for the WBS can be found on the EELV EBB.

3.7.6.2.4 ITAMP Requirements Correlation Matrix (RCM). Provide an RCM (ITAMPRCM.PDF) which shows direct traceability from the SOO, SPD, and WBS to the ITAMP tasks.

3.7.7 Commercial Launch Considerations Area. Provide a commercial management plan for ensuring commercial launch needs are met. Refer to the Commercial Launch Considerations Area evaluation standards in CFI Section 2 for additional specific information required for this plan. This file (COMMERCL.PDF) is limited to 10 pages.

3.7.8 General Considerations - Pre-EMD Price. Provide the following information.

3.7.8.1 Price and Labor Summary (PRCESUMM.PDF). Submit the total proposed price by major cost elements using the format shown below:

Description CLIN 0001

Direct Labor Hours:

Prime Contractor *

Subcontractors *

Interdivisional *

Total Direct Labor Hours *

Cost Element ($):

Direct Labor *

Labor Overhead *

Material *

Material Overhead *

Subcontracts *

Interdivisional *

Other Direct Costs *

Subtotal *

G&A *

Total Costs *

Facilities Capital Cost of Money (FCCOM) *

Profit *

Total Firm Fixed Price *

* To be inserted by Offeror

Submit funding requirements summarized by Government fiscal year, supported by projections of expenditures and commitments. The Offeror is to plan funding requirements in accordance with the dollar amounts specified in para 3.1.1.1. Introductory paragraphs/narratives which summarize the content of the Pre-EMD price information may be provided, as well as ground rules, assumptions, and any other relevant information used in developing the Offeror's proposed price.

3.7.8.2 Price Realism Information (TASKLOAD.PDF). For each WBS level 3 ITAMP task, provide (1) a bar chart of the total proposed direct labor hours by labor category and (2) a table summarizing (but separately identifying) contractor, subcontractor, and interdivisional transfer hours, with both the chart and the table summarized quarterly. For each WBS level 3 ITAMP task, provide, in general terms, the estimating rationale (cost estimating relationships, historical experience, etc.). All hours shall agree with the hours reflected on the price and labor summary information (reference previous paragraph). The Offeror shall only include Pre-EMD contract-funded tasks. Do not reflect any dollar amounts in this file.

3.7.8.3 Subcontracts/Material (SUB_MATL.PDF). Summarize the proposed subcontracts and interdivisional transfers greater than $1 million showing the supplier, a description of the item or service, and the price included in the prime's proposal to the Government for each. Provide an aggregated subtotal of all remaining subcontracts under $1 million. (Submittal of subcontractor proposals is not required.) Provide a listing of the ten most costly major material items, based on their extended value, indicating the nomenclature, unit price, quantity, and extended value.

3.7.8.4 Government Furnished Property (GFP) Cost Information (GFPINFO.PDF). Each Offeror shall provide the estimated rental value of GFP it proposes to use for the contract. The rental value of each item of Government production and research property (defined in FAR 45.201) shall be calculated in accordance with FAR 52.245-9. The rental value of other categories of GFP shall be calculated in accordance with FAR 52.245-9 to the maximum extent practicable; however, other equitable valuation methods may be used as appropriate. If no GFP is required, so state. Identify commercial alternatives (including cost and schedule impact) for each item listed in Attachment 6 of the model contract, in the event the Government cannot provide the item.

3.7.8.5 Base Support Cost Information (BASESPT.PDF). Furnish the estimated cost/rental value of each item of base support that the Offeror proposes to use for this contract, including copies of any written estimates from the base. Identify commercial alternatives (including cost and schedule impacts) for each item in Attachment 7 of the model contract should the requested support be unavailable or "permission slips" be unobtainable.

3.7.9 Software Development Capability Evaluation (SDCE) Questionnaire Response. The Offeror shall complete the SDCE questionnaire previously provided and submit the response as file SDCEANSR.PDF by 6 Sep 96 to the address specified in paragraph 3.2.1. Refer to the SDCE questionnaire instructions for specific page limit information.

3.8 Specific Instructions for Pre-EMD Contract and Documentation.

3.8.1 Model Contract. Refer to file MODELK.DOC in CFI Annex 4, which is a complete copy of the Pre-EMD model contract, and SF33.DOC provided with the CFI. Submit a completed model contract based on these files. Sequentially number the pages of the model contract through Section J starting with page one and reflect this numbering in Block 11 of the SF33. The following contract numbers shall be used by the Offerors and shown in the footers of the model contract and attachments:

Alliant Techsystems, Inc.: Contract Number F04701-97-C-0001

Boeing Defense and Space Group: Contract Number F04701-97-C-0002

Lockheed Martin Astronautics: Contract Number F04701-97-C-0003

McDonnell Douglas Aerospace: Contract Number F04701-97-C-0005

All other Offerors: CFI# F04701-96-R-0008

3.8.2 Attachments to Model Contract. The following are attachments to the Model Contract.

3.8.2.1 Attachment 1 - System Performance Document (SPD). Provide the Pre-EMD SPD (provided as Annex 6 of the CFI as file SPD.DOC) as ATTACH1.DOC. The Offeror is not required to submit the classified SPD annex. A copy of the classified SPD annex can be requested through the EELV Contracting Officer.

3.8.2.2 Attachment 2 - Work Breakdown Structure (WBS) Dictionary and Tree. Submit this information as ATTACH2.DOC. This file shall be a duplicate of file WBS.PDF provided in File Directory 1 in accordance with the instructions in paragraph 3.7.6.2.3.

3.8.2.3 Attachment 3 - Statement of Objectives. Provide the Statement of Objectives as ATTACH3.DOC. The EMD objectives shall be noted as being for reference only.

3.8.2.4 Attachment 4 - Small Business and Small Disadvantaged Business Subcontracting Plan. Submit a Subcontracting Plan (ATTACH4.DOC) which meets the requirements of Contract Clauses FAR 52.219-9, DFARs 252.219-7003, and 252.219-7005. If the Offeror is already operating under an approved company-wide plan as part of the DOD Test Program for Negotiation of Comprehensive Small Business Subcontracting Plans, then no plan is required to be attached. Instead, state "Reserved" on the Attachment 4 cover sheet and submit a copy of the approved plan as Appendix 8.

3.8.2.5 Attachment 5 - Rights in Technical Data - Noncommercial Items. This attachment (ATTACH5.DOC) refers to mandatory DFARs clauses 252.227-7013, Rights in Technical Data - Noncommercial Items, and 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, the purpose of which is to indicate the Government's specific rights to all data delivered under this contract. All data which the Offeror proposes to deliver with other than unlimited rights, and the rights with which it proposes to tender the data (e.g., Government purpose rights, limited rights, special license rights, and/or notice of copyrights), must be listed in this attachment. The attachment shall include the following information: 1) Technical data to be furnished with restrictions, 2) Basis for assertion, 3) Asserted rights category, and 4) Name of person asserting restrictions. Separate the submitted information into table 5a for the technical data, and a table 5b for software items or documentation.

3.8.2.6 Attachment 6 - Government Furnished Property (GFP). Submit to the Government a list of any GFP, Special Tooling and/or Test Equipment currently on hand or needed in performance of the Pre-EMD Module effort at the prime or subcontract level as file ATTACH6.DOC. The GFP listing shall be segregated as follows: ATCH 6A - Special Tooling and Test Equipment, and ATCH 6B - Government Furnished Property (Other). If no GFP is required, so state and place "Reserved" on the Attachment 6 cover sheet. In accordance with FAR Part 45, Attachment 6 shall contain the following information:

ATCH 6A, Special Tooling and Test Equipment (ST and STE): 1) name, identification number and nomenclature, 2) acquisition cost, 3) age (if known), 4) quantity required, 5) dates required, 6) contract number under which the ST and STE are currently accountable, and 7) current location.

ATCH 6B, Government Furnished Property (Other): 1) name, item's national stock number and nomenclature, 2) acquisition cost, 3) age (if known), 4) quantity required, 5) dates required, 6) contract number under which the GFP is currently accountable, and 7) current location.

It is the Offeror's responsibility to arrange for the use of Government test facilities and propellants. The cost to arrange for test facilities and propellants will be considered within the total proposed Pre-EMD Price. Government test facilities and propellants are not considered Base Support or GFP on the Pre-EMD contract and therefore shall not be included in Attachments 6 and 7. Government test facilities and propellants are to be costed by the Offeror and included in the Offeror's proposed ITAMP as part of its Pre-EMD proposal.

3.8.2.7 Attachment 7 - Base Support. Submit to the Government a list of all base support that is needed in performance of the Pre-EMD effort at the prime or subcontract level as ATTACH7.DOC. In accordance with FAR Part 45, show 1) service/property required, 2) where performed/located, and 3) dates required. If no base support is required, so state and place "Reserved" on the Attachment 7 cover sheet. Contractor-specific range support, for purposes of the Pre-EMD Module, is not considered base support and therefore shall not be included in Attachment 7. The contractor-specific range support activity is to be costed by the Offeror and included in the Offeror's proposed ITAMP as part of its Pre-EMD proposal.

3.8.2.8 Attachment 8 - Contract Security Classification Specification (DD Form 254). The Offeror shall complete the TBDs and identify any proposed changes to the DD Form 254 (provided in Annex 8 as file DD254.DOC) as ATTACH8.DOC.

3.8.2.9 Attachment 9 - Design Reviews Definitions. Provide the design review definitions (provided as Annex 3 of the CFI as file RVWDEFN.DOC) as ATTACH9.DOC.

3.8.2.10 Exhibit A - Contract Data Requirements List (CDRL). Exhibit A (EXHIBITA.DOC) shall contain the Government's data requirements provided in CFI Annex 7.

3.8.3 Supporting Documentation. Provide the following appendices in support of the Model Contract.

3.8.3.1 Appendix 1 - Representations and Certifications. Complete the representations and certifications provided in CFI Annex 5 as file REPCERT.DOC and provide as APPEND1.PDF.

3.8.3.2 Appendix 2 - Exceptions. Identify any exceptions taken to the terms and conditions of the CFI and Model Contract and submit as APPEND2.PDF. The Offeror is asked to add, as appropriate, at the end of each exception a statement substantially as follows: This offer (is) (is not) contingent upon acceptance of the exception.

3.8.3.3 Appendix 3 - Authorized Representative. Provide the name, title, and telephone number and FAX number of the company/division point of contact and alternate regarding source selection decisions as file APPEND3.PDF.

3.8.3.4 Appendix 4 - Acquisition Management Information System (AMIS) Letter. Provide a letter as file APPEND4.PDF stating that Air Force administrative procedures to accommodate the AMIS (e.g., the use of Accounting Classification Reference Numbers (ACRNs) in the contract) are acceptable and will not invalidate the proposal.

3.8.3.5 Appendix 5 - Location Information. Provide name, street address, mailing address, zip code, county, size of business (large or small), and labor surplus area designation of all facilities performing over $1.0 million of effort on the contract as file APPEND5.PDF. Indicate if facility is a division, affiliate, subcontractor or associate. If more than one place of performance is listed, indicate the percentage of work to be performed at each.

3.8.3.6 Appendix 6 - GFP Written Permission Slips. Provide written permission of the Contracting Officer or other person with authority to permit transfer of the property or its use on a non-interference basis. If this information is available electronically, provide as file APPEND6.PDF.

3.8.3.7 Appendix 7 - Base Support Permission Slips. Provide written permission/ authorization from the Base Commander having cognizance of the service/property. If "permission slips" are not obtained in time for inclusion with Offeror's proposal, then include proof of a good faith effort to obtain approval for use of the base support. If this information is available electronically, provide as file APPEND7.PDF. Otherwise, submit only a paper copy.

3.8.3.8 Appendix 8 - Approved DOD Test Program Subcontracting Plan. Per the Attachment 4 instructions in para 3.8.2.4, provide the Offeror's company's subcontracting plan if approved under the DOD test program. If this information is available electronically, provide as file APPEND8.PDF. Otherwise, submit only a paper copy.

This page intentionally left blank.