a. Point of Contact. The Procuring Contracting Officer (PCO) is the point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at the address located in Section A of the model contract/RFP.

b. Debriefings. Successful/unsuccessful Offerors may request debriefings by providing a written request to the PCO. Debriefings shall be conducted upon their request within 10 days after award of contract.

c. Discrepancies. If an Offeror believes that the requirements in these instructions or the instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale.

d. ABL Reference Library. For your use, ABL established a library containing over 700 reference documents located within the Phillips Laboratory technical library. For privacy there are two sound-proof cubicles in the room, each containing a table and three chairs. A dedicated librarian is present to retrieve and sign out documents to authorized contractors. Document use is restricted to this room. A listing of ABL reference documents is maintained in the Phillips Library's STILAS data base. The data base contains a summary of pertinent information about each document. Users are encouraged to review the data base prior to arranging their visits and select needed documents. Remote access to the ABL STILAS data base and issuance of a password can be processed when requesting visit authorization. Mail or FAX visit requests to SMC/TMS. Each request must state the purpose, duration, and be limited to visitors with SECRET security clearances or higher. When received, we certify the request and forward it to our librarian. The librarian contacts requesters and coordinates the date and time of visit. We process all requests upon receipt and you should receive contact from the librarian within one day after she receives your processed request. Please refer questions to Ms Bobbie Blount at (505) 846-9671. All visits are by appointment only.

1.2 Proposal Organization

The Offeror shall prepare the proposal for the Airborne Laser Program Definition and Risk Reduction (PDRR) effort in accordance with these Proposal Preparation Instructions (PPI) and with the structure set forth in Table L-2 (1) below. A complete proposal consists of seven (7) volumes and the attachments, all of which shall adhere to the page limit and number of copies requirements specified in Table L-2 (1). In addition to paper format, the unclassified proposal shall be delivered on ISO 9660 format CD-ROM (five copies). Volume IV Cost shall be delivered on separate CD-ROMs (five copies). Classified volumes shall also be delivered on separate CD-ROMs (five copies). The files on all CD-ROMs shall be of three types. Type #1 is the entire proposal (includes all text, pictures, and diagrams); type #2 is text or spreadsheet only; and type #3 includes pictures and diagrams only. The type #1 files shall allow the Government read-only access to this information, and include built-in viewing software (such as Adobe Acrobat) for on-screen viewing or printing. Type #2 files shall be delivered in Microsoft Word version 6.0c format or Microsoft Excel, Release 5.0c with no password protection or encryption such that the Government may copy the files and modify the text or spreadsheet for inclusion in their own documents. The type #2 file for the Integrated Master Schedule shall be Microsoft Project 4.0 compatible. Type #3 files shall be delivered in any format that may be easily inserted into Microsoft Powerpoint version 4.0c presentations, such as windows bitmaps (.bmp), tagged image formats (.tif), computer graphics metafiles (.cgm), etc. All files on the CD-ROM shall be arranged according to a logical hierarchy that may be easily indexed.

• Three additional copies of the entire proposal shall be submitted to the cognizant Government Contract Administration Office and one additional copy shall be submitted to the cognizant Defense Contract Audit Agency office.
• Alternative pricing of CLIN 0003 and CLIN 0008 (Fixed Price Subject to Escalation or Firm Fixed Price (whichever is not chosen as the preferred baseline)) shall be inlcuded but shall not count against the 100 page limit. Alternative pricing data shall not exceed 5 pages.
  

Be sure to advise the Administrative Contracting Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the proposal is "For Official Use Only" and "Source Selection Information--See FAR 3.104". Offerors are cautioned that submission of more data than required by the cost proposal instructions, Public Law, and FAR may hinder the evaluation of the Cost Proposal.

1.3 Proposal Format

a. This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The Offeror shall be compliant with the requirements as stated in the Technical Requirements Document (TRD), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the RFP may result in an unfavorable proposal evaluation.

b. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated capabilities, assessments, costs, etc.. The proposal should not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale as to how the Offeror intends to meet these requirements.

c. The proposal acceptance period is specified in Section A of the model contract/RFP. The Offeror shall make a clear statement that the proposal is valid through this date. In compliance with FAR Subpart 4.8 (Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, extra copies of such unsuccessful proposals will be destroyed by the Government.

1.3.1 Binding and labeling. Each volume of the proposal should be separately bound in a three-ring loose leaf binder which shall permit the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked with the volume number, title, classification, copy number, RFP identification and the Offeror's name. The same identifying data should be placed on the spine of each binder. Unclassified document binders shall have a color other than red. Be sure to identify appropriate markings such as the legend at FAR 52.215-12, Restriction on Disclosure and Use of Data.

1.3.2 Page Format Restrictions and Limitations

a. A page is defined as each face of a sheet containing information. Two pages may be printed on one sheet. Sheets shall be 8 1/2" x 11". Foldouts shall be 11" x 17" and each face shall be considered two pages. Text shall be 12 point with one and one-half line spacing. Text in figures and tables shall be no smaller than 8 point. Text shall be no smaller than 10 point with single spacing for Volume IV and 12 point with single spacing for the UBOE. Page borders shall be at least 1" wide on all sides. Page numbering, classification markings, and proprietary markings are the only information allowed within the border area. Each page shall be counted except the following:

Front and Back Covers
Table of Contents
List of Tables and Figures
Divider Tabs
Glossaries

b. Page limitations shall be treated as maximums. Page limitations will be determined from the printed copies (not the electronic submittals). If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and will be returned to the Offeror as soon as practical. Page limitations shall be placed on responses to clarification requests (CRs) and deficiency reports (DRs). The specified page limits for CR and DR responses will be identified in the letters forwarding the CRs and DRs to the Offerors. When both sides of a sheet display printed material, it shall be counted as 2 pages.

1.3.3 Indexing. Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

1.3.4 Glossary of Abbreviations and Acronyms. Each volume shall contain a glossary of all abbreviations and acronyms used, with a definition for each. Glossaries do not count against the page limitations for their respective volumes.

2.0 TECHNICAL DESIGN DATA PACKAGE

Instead of a traditional formal technical proposal, data from the Concept Design effort will be used. This technical data package is comprised of Concept Design data relevant to the CoDR1 design and the CoDR1 data package which is the core of the Offeror's technical proposal and should include key supporting rationale for the proposed technical approach. This includes, but is not limited to, PDRR and Engineering and Manufacturing Development (EMD) Technical Baseline Measures (TBMs) and glossary/rationale, CoDR1 briefing package, specifications, key trade studies documentation, design/interface documentation, drawings, scale models, etc. The Cost Performance TBMs should be updated and submitted in the Cost Volume of the Offeror's proposal.

3.0 VOLUME I - EXECUTIVE SUMMARY

The executive summary shall provide source selection executives and evaluators with the key elements and unique features of the proposed program. In addition, it shall serve as the reference document for understanding proposal format and locating elements of proposal information. A concise narrative summary of the entire proposal and a highlight of any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation criteria. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

4.0 VOLUME II TECHNICAL DESIGN DATA PACKAGE UPDATE

This volume shall contain required updates to the CoDR1 technical data package, including TBMs and rationale, which are a result of ongoing Concept Design design trades/evolution between CoDR1 and the proposal submittal. Do not resubmit data or information which was originally provided as part of the CoDR1 technical data package.

5.0 VOLUME III SYSTEM MANAGEMENT APPROACH

This volume shall describe the Offeror's approach to accomplish PDRR Phase I and Phase II (see Ref Doc ABL SAMP). PDRR Phase I consists of the preliminary/detailed design, fabrication, ground integration testing and initial flight test activities, and includes an Authority to Proceed (ATP) decision point after the flight-weighted laser module test and PDR. Exit criteria are contained in the ABL SAMP. At the end of PDRR Phase I, a second ATP decision point will authorize continuing into PDRR Phase II. Exit criteria to proceed into Phase II are also contained in the ABL SAMP.

The PDRR Phase II effort completes PDRR flight testing and finalizes the ABL EMD configuration, ensuring a smooth transition from the PDRR to EMD phase. Phase II will also include purchase of long lead hardware, to include payments for the EMD 747-400 aircraft, necessary to perform the EMD phase in a timely and cost efficient manner. Phase II PDRR transition effort takes the ABL design to an EMD CDR level of maturity. Starting from the PDRR design configuration, the preliminary and detailed EMD design are accomplished, incorporating PDRR lessons learned, approved adjunct mission requirements, and the approved survivability, including self-defense suite, design. Technology improvements are incorporated, and EMD test targets will be obtained. The EMD software design, coding and test are accomplished. EMD Build-to-Packages are assembled in preparation for producing the "production representative" EMD ABL weapon system. The detailed design of ABL support/test equipment and Logistics Support Analysis are finalized.

5.1 System Management Approach Volume Organization

The System Management Approach Volume shall consist of the following three sections and six attachments:

Section A - Integrated Task and Management Plan (ITAMP)

Section B - Risk Assessment

Section C - Key Processes

Atch 1 - Contract Work Breakdown Structure and Dictionary

Atch 2 - Compliance and Reference Documents

Atch 3 - Airborne Laser PDRR and EMD System Specifications

Atch 4 - Data Requirements

Atch 5 - Software Development Plan and Software Development Capability Evaluation Documentation

Atch 6 - Target Option

5.1.2 Document Relationships. The SOO, included as Attachment 1 to this RFP, provides the Government's overall program objectives and the Offeror's required support to achieve those objectives. The Offeror shall use the SOO, together with other applicable portions of this RFP, as a basis for preparing a response to this RFP. The ITAMP is an event-driven plan which describes the Offeror's proposed approach for fulfilling the objectives and requirements of this RFP. The specific tasks defined in the ITAMP shall be structured according to the Contract Work Breakdown Structure (CWBS) and traceable to the SOO. Figure L-2(1) is a generic overview of the relationship between key documents referred to throughout the remainder of the Section. This figure is not intended to represent a preferred format for the Offeror's presentation of the ITAMP Volume, but rather is for illustrative purposes only. The ITAMP will be included as Attachment 1 to the contract. Instructions for preparing the ITAMP are detailed in Paragraph 5.2.

FIGURE L-2(1) DOCUMENT RELATIONS

5.1.3 RFP Response. Your response to this RFP will be evaluated against the criteria defined in Section M, Evaluation Factors for Award. Using the instructions provided in Paragraph 5.2 (below), provide the actual methodology you would use for accomplishing the Government's objectives for this procurement.

5.1.4 Requirements. All requirements, derived from the SOO and specified in the Technical Requirements Document, are mandatory. In your response to specific requirements of the RFP, do not merely reiterate the SOO or reformulate the TRD requirements. If a requirement cannot be met, your proposal must identify the exception and explain why the exception is being taken.

5.2 Section A - Integrated Task and Management Plan (ITAMP)

Volume III -Section A (ITAMP) shall contain, as a minimum, the information specified below. Offeror format for the ITAMP Volume is encouraged, but must include a single separable section that lists titles of Events, Significant Accomplishments, and Tasks. This separable section will not count against the ITAMP page count.
a. ITAMP Summary
b. Table of Contents
c. Events, Significant Accomplishments, and Accomplishment Criteria
d. Task Descriptions

5.2.1 ITAMP Summary. Provide an overview of the technical/management approach detailed in your ITAMP.

5.2.2 ITAMP Elements. Figure L-2(2) shows the relationship between several of the elements of the ITAMP. The figure is referenced in the descriptive paragraphs below.

FIGURE L-2(2) RELATIONSHIP BETWEEN ITAMP ELEMENTS

5.2.2.1 Events. An Event is the initiation or conclusion of a significant program activity, which is itself composed of one or more Tasks. A significant Event may support one or more elements of a higher level Event - e.g., a significant subsystem design milestone may represent an Event which is but one contributing part of an overall system design Event. Events often represent decision points in the design, development and test cycle which generally must be successfully concluded prior to continuation of sequential activities. The Offeror shall establish the major contract Events and identify the significant accomplishments that must be achieved to satisfy those major contract Events. The Offeror is strongly encouraged to identify incremental reviews and milestones as deemed necessary.

5.2.2.2 Significant Accomplishments. The successful completion of a Task, or sequence of interrelated Tasks, can be noted as one or more Significant Accomplishments. Note from Figure L-2(2) that not all tasks culminate in a Significant Accomplishment; also, it is possible to associate more than one Significant Accomplishment with a single task completion or ending Event. Generally, however, Significant Accomplishments, representing the completion of one or more Tasks, can be related to specific Events and must be achieved prior to the completion of that Event. Within each event, significant accomplishments are normally grouped by Integrated Product Team (IPT) to ensure the ITAMP correctly addresses the interrelationships among functional disciplines. Significant Accomplishments are activities with measurable results based upon previously established criteria. The ITAMP shall contain a comprehensive list, with concise, but detailed descriptions, of all anticipated Significant Accomplishments, Accomplishment Criteria, and the relationship of both to the Offeror's proposed Task and Event list. Where applicable, the ITAMP will describe the data preparation and submittal requirements associated with accomplishments and events. These data reporting requirements will be referenced to the information contained in Volume III, Attachment 4, Data Requirements.

5.2.2.3 Accomplishment Criteria. Accomplishment Criteria are objective measures pertaining to the successful achievement of a Significant Accomplishment. Accomplishment Criteria represent firm measurable objectives established in advance of the proposed Accomplishment and may be related to one or more of the program Technical Baseline Measures (TBMs). Subjective assessments of progress, as in "task 50% complete" or "90% of goal achieved," are not acceptable Accomplishment Criteria. Accomplishments and Accomplishment Criteria shall provide a mechanism for planning Tasks and unequivocally evaluating their successful completion.

5.2.2.4 Task Descriptions. This section shall provide a comprehensive, sequential list of the tasks the Offeror proposes as required to successfully address the objectives and requirements of the ABL SOO and the ABL PDRR and EMD System Specifications. This section should also include a summarization of the major program events and show critical program interdependencies. Inter-relationships and dependencies between the most significant high cost or high risk tasks must be clearly shown. Tasks will be defined to a sufficient level to demonstrate the Offeror understands the objectives and requirements and will meet them. Tasks in areas of high cost or risk should have more detail. The narrative in the task description should provide insight into how the activity is to be accomplished. The ITAMP is not a vehicle for providing the rationale behind the task selection and definition. Rationale leading to the Offeror's decision to pursue a particular course of action is provided in the technical design data package discussed in para 2.0 and, if required, in the technical design data package update discussed in para 4.0. Where required for completeness, tasks shall be referenced to the appropriate proposal section containing the rationale for the approach.

5.2.3 Recommended Events/Significant Accomplishments/Criteria. The following are Government recommended Events/Significant Accomplishments, with the required USAF Acquisition Strategy Panel (ASP) Authority To Proceed (ATP) Exit Criteria (See Ref Doc ABL SAMP) marked as either ATP-1/ATP-2. The Offeror is strongly encouraged to identify additional events / significant accomplishments based on his proposal approach. The Offeror may propose / structure their ITAMP Events / Significant Accomplishments / Accomplishment Criteria to most efficiently execute their proposed program, but as a minimum must meet the ATP-1/ATP-2 Exit Criteria requirements. All other ATP-1 Exit Criteria must be completed prior to PDR, and the ATP-2 Exit Criteria must be completed in FY01 prior to the start of PDRR phase II.

a. Flight-weighted Laser Module (FLM) Demonstration (ATP-1): The Offeror shall demonstrate, at full power, a single laser module of his modular laser design which substantially meets the requirements derived from the PDRR TRD with all critical components flight weighted (i.e., oxygen generator, nozzles, cavity, heat exchanger core, and diffuser/ejector or a representative operational section). The operational conditions will be representative of the PDRR ABL. The power, beam quality, chemical efficiency, and thermal management shall be scalable and traceable to the performance of an EMD ABL laser module through analysis with anchored models. The test performance criteria will include: behavior of flight-weighted materials, chemical efficiency, cavity medium quality including flow characterization (by interferometry, etc.), cavity mirror thermal distortion (also by interferometry), output beam irradiance profile, efficiency of the Thermal Management System (TMS), pressure recovery performance of the Pressure Recovery System (PRS), and power and beam quality out of the FLM. This demonstration must occur prior to completing PDR.

b. Flight-weighted Illuminator Demonstration (ATP-1). The Offeror shall demonstrate the technology to support scaling and flight-weighting of the flight-weighted illuminator laser(s) necessary for precision tracking and/or atmospheric compensation that is (are) fully scalable/traceable to the PDRR and EMD ABL illuminator laser(s).

c. Deformable Mirror/Optical Coating Demonstration. The Offeror shall demonstrate the technology necessary for ABL PDRR deformable mirrors (DMs) and DM optical coatings and show their scalability and traceability to the EMD designs. The demonstration may be conducted with a subscale DM, but must include the PDRR DM faceplate, actuator, and optical coating designs and materials and must address such issues as coating adherence and performance after repeated actuator cycling. This demonstration must occur by CDR.

d. Active Tracking Ground Demonstration (ATP-1). The Government, with Offeror participation, will demonstrate the ability to actively track boosting missiles from the ground in a scaled experiment at White Sands Missile Range.

e. Beam Control Lab Demonstration (ATP-1). The Offeror shall demonstrate the ABL beam control system's architecture and function using, as a minimum, low power laboratory components with all beam control functions exercised and performances scalable and traceable to the derived PDRR and EMD beam control requirements.

f. ABL PDRR System Preliminary Design Review (PDR) (ATP-1). The Offeror shall complete PDR, including resolution of ABL supportability issues. The PDR may be structured as one or a series of incremental reviews which, taken together, demonstrate the Offeror's ABL PDRR design is sufficiently mature to warrant proceeding to detailed design.

g. ABL PDRR System Critical Design Review (ATP-2). The Offeror shall complete PDRR CDR, including a full scalability/traceability review. The CDR may be structured, analogously to the PDR, to demonstrate the Offeror's ABL PDRR design is acceptable to proceed to fabrication and ground verification.

h. Component Fabrication (ATP-2). The Offeror shall demonstrate all critical manufacturing processes and complete fabrication of at least one of each type of system component.

i. Aircraft Certification (ATP-2). The Offeror shall obtain an Experimental Flight Certification for the PDRR aircraft.

j. Aircraft Modifications (ATP-2). The Offeror shall complete modifications to the PDRR aircraft.

k. Local Loop Beam Control System (BCS) Demonstration (off-board). This test provides a complete off-board check of as many BCS control loops as possible in the absence of atmospheric and target effects. Initially, this test shall take place at low power using the PDRR BCS. Ultimately, this test shall take place under high power, using the ABL PDRR high energy laser (HEL) subsystem or FLM (para 5.2.3 a) and PDRR BCS hardware. Use of a non-ABL HEL and the PDRR BCS is acceptable, provided the equipment used has sufficient fidelity to the baseline PDRR designs. Successful completion of this test includes stable, closed loop operation of as many of the BCS alignment (translation, tilt and jitter) and wavefront control functions as possible--in the presence of representative ABL PDRR disturbance inputs, excluding atmospheric and target effects--for as least 5 seconds, with loop performances substantially meeting derived BCS specifications.

l. Integrated Beam Control System Demonstration (off-board). This test provides a complete off-board check of the integrated BCS control loops in the presence of all disturbance inputs, including simulated atmospheric and target effects. Initially, this test shall take place at low power using the PDRR BCS (ATP-2). Ultimately this test shall take place under high power, using the ABL PDRR HEL or FLM (para 5.2.3 a) and PDRR BCS hardware. Use of a non-ABL HEL and the PDRR BCS is acceptable, provided the equipment used has sufficient fidelity to the baseline PDRR designs. Successful completion of this test includes stable, closed loop operation of all BCS alignment (translation, tilt and jitter) and wavefront control functions--in the presence of representative ABL PDRR disturbance inputs--for at least 5 seconds, with loop performances substantially meeting derived BCS specifications.

m. Laser Module Scaling Demonstration (ATP-2). The Offeror shall demonstrate (either on- or off-board) laser scaling and multi-module operation using PDRR laser modules.

n. PDRR Aircraft System Test Readiness Review (STRR). The STRR shall be structured to demonstrate that the PDRR aircraft system is ready to proceed to flight test.

o. Facilities Handover. All facility modifications required to support air vehicle integration, such as the hangar and integration laboratories, are completed.

p. Integrated PDRR Surveillance Demonstrator (ATP-2). These tests will demonstrate the integrated surveillance system performance (target detection, target discrimination, target prioritization, and target data handoff to fire control).

q. Integrated Weapons Element Hot Test (Ground test, following integration with airframe). This test provides a complete on-board ground-based high power check of the ABL Weapons Element, using the baseline HEL and BCS subsystems. Successful completion of this test includes stable, closed loop operation of all the line of sight stabilization, alignment (translation, tilt and jitter), and wavefront control functions for a sufficient time to provide confidence in the PDRR system meeting its flight test objectives (at least ten (10) seconds), with the HEL output power and BCS loop performances substantially meeting derived segment specifications.

r. Integrated ABL PDRR System Hot Fire Tests (Airborne, instrumented target). This test series will provide beam stability and far field profiles under a variety of geometric (range and altitude) and atmospheric turbulence conditions to ensure that the system performance models are properly anchored to ensure scalability and traceability to the EMD system.

s. PDRR System Demonstration (Airborne, TBM or TBM-representative target). This test will serve as an end to end system demonstration of the ability to destroy a representative TBM or surrogate at ranges consistent with the PDRR TRD.

t. PDRR Phase II PDR. The Offeror shall complete Phase II PDR, including resolution of ABL supportability issues for EMD. The PDR may be structured as one or a series of incremental reviews which, taken together, demonstrate the Offeror's ABL EMD design is sufficiently mature to warrant proceeding to detailed design for EMD.

u. PDRR Phase II CDR. The Offeror shall complete Phase II CDR. The CDR may be structured, analogously to the Phase II PDR, to demonstrate the Offeror's production representative ABL EMD design is acceptable to proceed to fabrication and verification.

v. EMD Proposal Negotiated. The Offeror shall complete EMD proposal negotiations prior to completion of PDRR Phase II.

5.3 Section B - Risk Assessment

5.3.1 Contents. Section B should include a summary of the key risk areas of the entire program, a description of the risk management process, and a cross reference between risks and mitigating ITAMP tasks and other risk mitigation activities. When addressing risk be sure to include in your discussion:

Technical -Moderate and high risk areas of the system design, systems engineering approach, manufacturing, and key technical issues.

Management -Program schedule and program management including discussions on moderate and high risk areas.

5.3.1.1 Risk Management Process. Define the risk management processes, for both hardware and software, including integration into the overall systems engineering and IPT process. Describe the processes for identifying, prioritizing, mitigating and tracking risk for both hardware and software in the performance, cost, schedule and support areas. Describe your approach to incremental verification

5.3.2 Risk Definition

High (H)
Likely to cause significant, serious disruption of schedule, increase in cost, and/or degradation of performance even with special Contractor emphasis and close Government monitoring.

Moderate (M)
Can potentially cause some disruption of schedule, increase in cost, and/or degradation of performance. However, special Contractor emphasis and close Government monitoring will probably be able to overcome difficulties.

Low (L)
Has little potential to cause disruption of schedule, increase in cost, or degradation of performance. Normal Contractor effort and normal Government monitoring will probably be able to overcome difficulties.

5.4 Section C - Key Processes

The Offeror shall provide detailed descriptions of his proposed implementation of the processes and implementing plans which are basic to the execution of the ABL PDRR program. Below are the minimum required processes the Offeror shall describe. Other processes the Offeror believes are important may be described. All sections of the System Management Approach Volume shall be consistent with and shall reference these descriptions where appropriate.

a. Program Management. Describe the program management (cost, schedule, performance) processes, tools, and metrics used to monitor program progress. Specifically describe how the ITAMP, IMS, and critical path network will be integrated and updated/maintained. Describe how IPT Leads will have budget allocations at contract award, and how the contract budget baseline will be detail planned for at least the first six months of effort and the balance spread consistent with the Offeror's government-approved Integrated Management System and will be fully integrated for all team members within 60 days of contract award. Describe your Life Cycle Cost management approach and at what major milestones the LCC estimate will be updated and provided to the government. The Offeror shall describe their proactive subcontractor management processes, including identification of critical subcontractors, flowdown of requirements and streamlining procedures, and tracking subcontractor performance to ensure program technical and programmatic requirements are met.

b. Systems Engineering. Define the processes to ensure a disciplined, rigorous systems engineering/integration approach to develop balanced, integrated PDRR and EMD weapon systems in accordance with Integrated Product Development (IPD) principles. Define the makeup, roles, responsibilities, and authority (design and budget) of the Integrated Product Teams (IPTs). Describe the processes for ensuring cross-IPT integration and integration of specialty engineering disciplines into the IPTs. Describe the systems engineering/integration tools/system, including requirements traceability, interface control/management, the single, integrated (system, hardware, and software) metrics system, and error/loss budget. Describe the processes for demonstrating scalability and traceability to the EMD system. Describe the approach to hardware/software integration. Describe how quality will be integrated into the IPTs design process to ensure first-pass success and how traditional "quality by inspection" methodologies will be minimized. Describe the processes to be used for conducting an overall ABL electromagnetic environmental effects (EEE) program to address electromagnetic interference/compatibility, lightning protection, electrostatic discharge, and electrical overload. Describe the processes for integrating producibility/manufacturing throughout the IPT design/development process, including incorporating Lean Manufacturing processes, and the approach for balancing parts commonality/standardization, new technology, obsolescence, and performance/cost.

(1) Configuration/Data Management. Define the processes to be used in implementing a configuration management program, including identifying, documenting, and controlling the system/design requirements and design/test products. Define the system baseline as it evolves throughout the design/test process and how it will be integrated into the ITAMP/IPTs. Define the data management processes to be used by which program data will be collected, formatted, stored, updated and transmitted.

(2) Intelligence Support. Define the process for identifying ABL system intelligence support requirements to develop an Intelligence Support Plan (ISP) with the exception of costing the intelligence support needed. The ISP will outline required intelligence support requirements over the projected ABL life cycle. The ABL threat baseline will include the System Threat Assessment Report (STAR) and other threat definition data.

(3) Environmental, Safety, and Health. Define the programs to conduct all activities in accordance with applicable federal, state, and local Environmental, Safety, and Health (ESH) laws and regulations, Executive Orders, treaties, and policies. Define the program to comply with the National Aerospace Standard (NAS) - 411 or a comparable program. This Hazardous Material Management Program (HMMP) will insure environmental compliance and endeavor to minimize the use of all hazardous materials. The HMMP and the incorporated environmental life cycle cost analysis will also be used to develop pollution prevention alternatives to be evaluated by the IPTs. Describe the methods to comply with the Executive Order 12969 "Federal Acquisition and Community Right-To-Know." Ensure no use of Class I Ozone Depleting Substances (ODS) for the PDRR program, except for critical applications for which there are no technically or economically feasible alternate substances or processes. If Class II ODS are needed for the PDRR program, insure a plan to phase out their usage. The intent is to eliminate all uses of Class I and Class II ODS for the production phase. Define the processes to be used in implementing a comprehensive system safety program to identify the hazards of sub-systems / systems / ABL weapon system and to impose design requirements, operating procedures, test procedures, and management controls to prevent mishaps. Describe what tasks and activities will be used to implement the program throughout the entire life cycle of the system and how they will be integrated into the IPT design and test processes. Use MIL-STD-882C as guidance.

(4) Program Security and System Security Engineering (SSE). Define the processes used to implement the ABL Program Protection Plan (PPP), at the Contractor location, to protect sensitive and classified ABL System information, software, and hardware, including developing the Contractor annex to the PPP. Describe the process for the design, development, test and accreditation of trusted software/hardware.

(5) Affordability. Affordability is an integral component of the IPT system engineering process which must be scalable and traceable throughout the life cycle of the Airborne Laser program. Affordability is also a key element of the Government's intent to manage Cost As an Independent Variable (CAIV) as described in the new DoD 5000.2-R. The Offeror will ensure system affordability through prudent design decisions and business practices. The Offeror shall explain how the baseline system design meets the objectives in the SOO and requirements in the TRD, while ensuring system affordability over the life cycle of the program in an environment of rapidly evolving technologies and severely constrained budgets. Define the management process, tools, criteria, and metrics for achieving program affordability, specifically, how the DTC goals contained in the EMD System Specificationification will be flowed down to the lower level specifications and be tracked and managed at the IPT level. The Offeror-provided affordability criteria will be measured by a set of affordability metrics which will be tracked as design parameters in the PDRR contract. Examples of affordability metrics for consideration are encouraged in the areas of Design to Weight (DTW), Design to Cost/Life Cycle Cost (DTC/LCC) goals, Maintenance Man-Hours per Flight Hour (MMH/FH), unit flyaway cost, and other design to performance, operations, supportability, and unit cost parameters. The affordability management process shall optimize the affordability criteria by measuring progress, evaluating and selecting alternatives, and documenting data and decisions. Specific areas listed below will be addressed, and the Offeror is encouraged to include other affordability areas.

(a) System-wide cost optimization, including assessment of cost sensitivities and development of year by year funding needs, recurring costs, non-recurring costs, and life-cycle costs.

(b) Flexible approaches to system design, development, production, test, operations, and sustainment that minimize the cost of meeting requirements and accommodate requirement and budget perturbations.

(c) Use of existing asset/infrastructure, Commonality, Standardization, and Interoperability (CSI), hardware/software reuse, Non-Developmental Items (NDI), GFE, and GFP to reduce developmental, operational, and sustainment costs. Define a method of balancing the risk with the expected cost savings through the use of GFE and GFP.

(d) Cooperative opportunities with other Government and commercial programs to reduce overall cost to the Government.

(6) Reliability/Maintainability/Supportability (RM&S). Define the processes to be used for conducting an ABL PDRR system (hardware and software) reliability, maintainability, and supportability (RM&S) program, including how RM&S will be integrated into the system engineering and IPT design process. Data sources, modeling techniques, tools, processes (internal procedures, industry, or military standards) to be used shall be described. Define the process for identifying failure modes and their effects on system RM&S. Describe the logistics support analysis approach to develop supportable systems interoperable with the Air Force infrastructure including the use of the Contingency Action Team to define the deployment package. Define the approach for collecting and developing a Supportability database with the capability to sustain the system level reliability, maintainability and logistics performance parameters. Define the process for the practical use of GFE, GFP, GOTS, CFE, and COTS. Describe the maintenance concept and the maintenance and support planning processes. Define the specific aspects of the training program. Define the processes to be used for identifying system support design/cost drivers and high risk areas. Describe how reliability, maintainability, and supportability will be verified during verification/testing. For software life cycle development/support, an automated computer based software environment should be addressed. For high risk software support requirements, define a preliminary assessment of the supportability risks.

c. Software Engineering. Describe your technical and management approach for designing, developing, and integrating software to meet ABL system performance requirements, including facilities/tools, metrics, prototyping/simulation, software reuse, open systems architectures, software risk mitigation, and software development life cycle models. Describe how the tasks and processes referenced in the Software Development Plan (SDP), ITAMP and Software Development Capability Evaluation (SDCE) responses will be used to ensure integration / coordination across all IPTs.

d. Test and Evaluation. For both hardware and software, describe the role of testing in the developmental process. Define preliminary test objectives. For both hardware and software, define the methods to be used to verify component, subsystem and system performance and to project these results into ABL PDRR and EMD system effectiveness and suitability throughout the program life cycle. Define the approach for Government participation/insight into test plan development, test execution and reporting. Describe any test resources required during the ABL PDRR program and the source of these resources (i.e., CFE, GFE).

5.5 Attachments

5.5.1 PWBS and CWBS. The Government's Preliminary Work Breakdown Structure (PWBS), defined in Figure L-2(3) and in the following PWBS Dictionary, provides a notional structure that the Offeror shall map to the Offeror-developed Contract Work Breakdown Structure (CWBS).

The Offeror shall provide a tailored, expanded Work Breakdown structure (WBS) and dictionary that depicts the structure (CWBS) necessary to execute their planned program in the most efficient manner, consistent with their IPT structure, as an attachment to this volume. The program will be managed as an IPD effort and the CWBS should be organized and reflect management by Integrated Product Teams (IPTs). The CWBS and dictionary shall be provided to the level that adequately defines the Offeror's program and provides necessary visibility into moderate and high risk areas as defined in para 5.3.

5.5.1.1 ABL PDRR Preliminary Work Breakdown Structure (PWBS) Dictionary (Level 3)

Airborne Laser (ABL) PDRRProgram (00000). The ABL PDRR program will demonstrate all technologies required for acquiring, tracking, and killing Theater Ballistic Missiles (TBMs) in the boost phase. The ABL PDRR systemmust demonstrate all key technologies for an ABL EMD system including the aircraft with the integrated weapons system (hardware / software) and necessary supporting equipment to conduct testing. The ABL PDRR system will provide a limited operational capability, including the ability to deploy to a theater and communicate with the joint C2 theater architecture. During PDRR phase II, the EMD ABL will be designed to the CDR level.

System Program Management (10000). System Program Management includes all activities necessary to ensure the ABL PDRR program is properly executed. This includes developing and maintaining the organization; ensuring personnel are empowered with the necessary tools to accomplish their mission; and planning and replanning the Contractor effort as necessary to complete a successful ABL Demonstration and EMD ABL design in a cost effective, timely manner. Administrative security, to ensure information vital to national security is properly handled, is also included. Program control is responsible for budget execution and planning; contract funding; cost estimation (life cycle cost estimate updates); program schedules; cost, schedule, and performance analysis; and formulating and providing programming, planning, and financial guidance and policy. Contracting is responsible for administration and execution of the PDRRcontract, negotiation of contract changes, and ensuring contractual direction is properly transmitted to all functional activities.

Systems Engineering (20000). Systems engineering includes the partitioning of the PDRR and EMD system requirements into derived hardware and software requirements for the individual subsystems, balancing cost and risk to achieve a successful design, arbitrating interface issues and derived requirements imbalances between the subsystems, and specialty engineering tasks. Specialty engineering tasks are those items necessary to ensure a safe, supportable, high quality product (system safety, quality assurance, configuration control, data management, system security, and environmental engineering). Systems Engineering is the owner of the PDRR and EMD system specifications. Systems Engineering is responsible for threat analysis and survivability. Systems Engineering is responsible for scalability and traceability from the PDRR to EMD designs.

System Integration and Analysis (21000). System integration and analysis is responsible for ABL PDRRsystem integration and performance and the implementation of the IPD processes, including support to the EMD design effort.

Operations Analysis and Simulations (22000). Operations analysis and simulation is responsible for all analyses and simulations of the performance of the ABL PDRRand EMD systems. This includes individual engagement scenarios, m on n engagements, and adjunct missions.

Risk Management (23000). Risk management ensures a dynamic set of risk mitigation activities is supported. A balanced risk reduction program ensures that the overall probability of successfully completing the ABL PDRR program and obtaining a robust EMD design is increased.

Software Integration and Engineering (24000). Software Integration and Engineering is responsible for developing the SDP and for coordinating software processes across all IPTs. This also includes establishing open architecture computer resources for as much of the ABL PDRRsystem as feasible, the reuse of existing software, the design principles for reuse of developed software for both open and non-open systems, integration and test of the system as a releasable product, and management of the software maintenance activity. Incorporating scalability of software and associated resources from the ABL PDRRto EMD capabilities in conjunction with the EMD design activity is also accomplished.

Integrated Logistics Support (ILS) (25000). ILS is responsible for ensuring that supportability, reliability and maintainability are designed into the hardware and software of the ABL PDRR and EMD systems. ILS will collect the reliability, maintainability and logistics data to serve as a supportability database that integrates support considerations into the system design at the most cost effective approach for supporting the system. ILS also provides diagnostics and maintenance, equipment, and services, and all support equipment not provided by the test and evaluation activities. This function is also responsible for participating with the Government in developing a contingency action plan. This action plan will outline the training, software support, sparing, supplies, and technical support required in theater for the PDRR and EMD ABLs as well as how to prepare for deployment after the PDRR ABL demonstration.

Reliability and Maintainability (R&M) (26000). R&M is responsible for system level R&M engineering and planning.

Advanced Technology Studies (27000). Advanced Technology Studies management is responsible for working with the SPO and the PL / Lasers and Imaging Directorate and other Air Force Laboratories to explore technology improvements for the EMD ABL including the development of high risk, high payoff engineering solutions to provide design margin, RM&S, and robustness improvements in the outyears.

Air Vehicle (30000). The Air Vehicleincludes design, development, fabrication, and integration of the PDRR aircraft and all systems installed on the PDRR aircraft. The EMD Air Vehicle includes the EMD aircraft and all systems installed on the EMD aircraft.

Air Vehicle Integration and Functional Checkout (31000). Air vehicle integration and functional checkout integrates all of the hardware and software onto the aircraft and performs (a) checkouts of the individual subsystems as installed and (b) the entire system once installed on the ground. This also transitions to the Developmental Test & Evaluation (DT&E) function a PDRR ABL which is completely functional and operating as designed.

Aircraft (32000). Aircraft provides, modifies, and maintains an aircraft (hardware/software) to support the PDRRABL and provides the modification design for the EMD ABL to a CDR level.

Laser (33000). Laser encompasses generator, nozzle, cavity, resonator, pressure recovery, thermal management, fuels, fuel storage and delivery, instrumentation, controls, processors, software, diagnostics, support subsystems, and mechanical structures, in a lightweight efficient laser, required to produce photons for meeting the derived performance requirements. This also includes design, development, fabrication, integration and testing of a laser system for the PDRRABL, including specific support equipment and spares and parts, permitting the PDRR ABLto meet the timeline, lethal fluence vs. range, and supportability requirements in the PDRRABL System Specification. This further updates the design of the EMD ABL laser system as necessary to incorporate all lessons learned from the PDRRABL and successfully complete EMD CDR.

Beam Control (34000). Beam Control encompasses those optical components, sensors, instrumentation, controls, processors, software, diagnostics, support subsystems, and mechanical structures required to acquire and track theater ballistic missiles designated by the battle manager, accept (from the laser segment) and manage the HEL beam, align and stabilize the optical line of sight, transfer and point all laser beams, compensate the HEL for atmospheric disturbances, choose an aimpoint on the missile, and maintain a stable HEL beam on that aimpoint. This also designs, develops, fabricates, integrates and tests a beam control subsystem for the PDRRABL, including beam control specific peculiar support equipment and initial spares and repair parts, that permits the PDRR ABLto meet the timeline, lethal fluence vs. range, and supportability requirements in the PDRRABL System Specification. This further updates the design of the EMD ABL beam control subsystem as necessary to incorporate all lessons learned from the PDRRABL and successfully complete EMD CDR.

Fire Control (35000). Fire Control encompasses those optical components, sensors, processors, software, diagnostics, support subsystems, mechanical structures, controls and displays required to acquire and track hostile missiles designated by the battle manager, manage the target engagement timeline, control the delivery of lethal fluence and verify kill. Tasks include design, develop, fabricate, integrate and test a fire control subsystem of the PDRRABL, including fire control specific peculiar support equipment and initial spares and repair parts, that permits the PDRR ABL to meet the timeline, lethal fluence vs. range, and supportability requirements in the system specification. This further updates the design of the EMD ABL fire control subsystem as necessary to incorporate all lessons learned from the PDRRABL and successfully complete EMD CDR.

Battle Management Command, Control, Communications, Computers and Intelligence (36000). BMC4I encompasses those integrated functions and or the components that ensures the execution of the mission from initial mission planning, to finding the TBM target, to tasking, controlling, and monitoring the weapon element, to reporting through the theater air defense command and control architecture updates on mission status/feedback, to finally aircraft recovery. BMC4I involves doctrine, rules of engagement, organizational, intelligence, communications, situational awareness, computers, and personnel to provide command authorities at all levels timely and accurate data to plan, direct and control required mission activities.

System Test and Evaluation (40000). System test and evaluation includes all planning, instrumentation, execution, and data reporting from the integrated system test activity.

Development Test and Evaluation (41000). Development test and evaluation is responsible for the planning, preparation, and execution of all tests from the completion of functional checkout through the complete ABL lethality demonstration against a boosting target and planning for the same for the EMD phase.

Test and Evaluation Support (42000). Test and evaluation support is responsible for test support equipment and activities including any Contractor provided support vehicles, range support, targets, instrumentation or other special equipment. Test instrumentation includes obtaining instrumentation and instrumenting all targets including diagnostic and missile targets and planning for the same for the EMD phase.

Test Data Analysis and Reporting (43000). Test data analysis and reporting is responsible for collecting, reducing, analyzing, and reporting on all test data.

Ground Support (50000). Ground support is responsible for designing, developing, and maintaining a ground support facility to meet all Air Vehicle requirements. This includes facilities necessary to integrate, test, secure, supply, and maintain the Air Vehicle, as well as ensuring compliance with all environmental laws and regulations. Planning for EMD is also included.

Facility (51000). The facility includes all laboratory, integration, and ground support facilities, to include modification of existing Contractor / Government facilities and planning for the same to accomplish EMD.

Equipment (52000). The equipment includes the common support and peculiar support equipment for the ground support facility. It also includes all essential support equipment for the PDRR ABL. It also includes design of the EMD ABL support equipment.

Training (60000). Training provides all necessary training for personnel operating and maintaining the PDRRABL, and planning for all activity required to execute the EMD program.

5.5.2 Compliance and Reference Documents. This Section shall contain a list of proposed compliance and reference documents. The ABL Technical Requirements Document is a compliance document. The Offeror may propose other compliance documents, provided such documents are existing Government or industry specifications or standards. Company practices or procedures may only be listed as reference documents. All compliance documents listed shall include appropriate tailoring. The Offeror shall comply with all requirements contained in compliance documents, as tailored. The version of the listed documents that will be used for the PDRR contract shall be made available for review by the SPO/DPRO. The ITAMP should reflect Contractor authorization to adopt later versions of compliance and reference documents and a process to notify the Government of the planned change in document version.

5.5.2.1 Compliance Documents. Compliance documents, along with proposed tailoring, shall be defined by the Offeror from among any of the currently maintained DoD Instructions, Standards, or Handbooks, IEEE, ANSI or ISO Standards, any other commercial or industry standard practices, or any combination of the above. Tailoring of compliance documents shall be described in this section.

5.5.2.2 Reference Documents. The following reference documents were considered by the Government in developing the RFP and are available in the read library.

a. ABL Single Acquisition Management Plan (SAMP)
b. AFMC Centralized RFP Support Team Lightning Bolt #1 Streamlining Package
c. MIL-STD-881B, dated 25 Mar 93 "Work Breakdown Structure for Defense
Material Items"
d. ABL System Threat Assessment Report (STAR)
e. CAPSTONE STAR
f. Joint Pub 3-55, Doctrine for Joint Reconnaissance, Surveillance and Target
Acquisition.
g. Joint Pub 2-0, Joint Doctrine for Intelligence Support to Operations
h. Joint Pub 3-52, Doctrine for Joint Airspace Control in the Combat Zone
i. Air Force Theater Missile Defense Concept of Operations
j. AFI 14-208, Intelligence Support to the Air Force Acquisition Process
k. AFI 14-206, Modeling and Simulation
l. MIL-STD-882C, 19 January 1993, "System Safety Program Requirements"
m. AFI 91-202, dated 01 Oct 95, The US Air Force Mishap Prevention Program
n. NAS-411, Hazardous Materials Management Program
o. DoD 5200.1-M, Mar 94, Acquisition Systems Protection Programs.
p. ISO 9000, Series Quality System Standard.
q. ISO 12207, Software Life Cycle Processes

5.5.3 PDRR and EMD ABL System Specifications. The Offeror shall provide, as an attachment to Volume III, proposed PDRR and EMD ABL System Specifications based upon the Government's TRD. The Contractor shall include affordability goals (e.g., Design to Cost) for the EMD system in the System Specification (ref para 5.4.b.(5)).

5.5.4 Data Requirements. The Offeror shall also propose data requirements in the form of a Contract Data Requirements List (CDRL), including appropriately tailored Data Item Description (DID) references. As a minimum, this attachment shall include the CDRL and DID requirements specified in the RFP. The Offeror may include additional data requirements. All data requirements shall be traceable to one or more specific tasks defined in the ITAMP. Individual data requirements shall be specified using the DD Form 1423-1, Contract Data Requirements List. The successful Offeror shall submit data in accordance with the information specified in the DD Forms 1423-1.

5.5.4.1 Electronic Data Transfer. The Offeror will describe how relevant program management and technical records, reports, and data will be generated, transferred, and maintained electronically (near real time) including classified information and data. This description should include how this electronic database will be readily available to the Government System Program Office (SPO).

5.5.5 Software Development Plan and Software Development Capability Evaluation (SDCE) (Responses and Sample Data). The Offeror shall include responses to the SDCE questions. This information encompasses the requested Software Development Plan, sample data, and the SDCE cross reference matrix.

5.5.6 Target Option. The Option will not contain any of the tasks or costs to modity or instrument targets. The modification and instrumentation of all targets is solely a contractor responsibility and is part of the basic ITAMP. The RFP is structured to have the Government fulfill the target requirements identified in the proposal by the offeror in paragraph 9.2.6.2 (GFP and/or Base Support Requirements). However, as an option beyond the basic contract, the offeror is to identify, with supporting rationale any ITAMP tasks, equipment and delivery dates associated with the acquisition, operation, and launch of these or other targets that would significantly improve the test program validity, provide significant cost savings or reduce risk if provided by the contractor instead of the Government. The contractor shall provide costs for these ITAMP tasks or equipment. Attachment 7 of the RFP includes a proposed Target Option Matrix to be completed and provided with the proposal. The presentation of this matrix should be structured to allow the Government to negotiate each group. The presentation of this option should also clearly articulate any GFE or other support required for each group. For example, if the offeror chose to use target boards towed by drones in the test program, the activities and equipment to acquire and operate the drones would be included in that group. The offeror shall include any GFP and/or base support requirements associated with this target option using the instructions in paragraph 9.2.6.2. (GFP and/or Base Support Requirements). This matrix is also shown in Attachment 7 of the RFP.

5.6 Other Instructions

5.6.1 Planned Studies and Analyses. Volume III - Section A (ITAMP) shall contain the Offeror's planned tasks for accomplishing the following baseline program studies/analyses at appropriate points throughout Phase I and Phase II of the PDRR program:

5.6.1.1 Threat. These studies are ongoing efforts with periodic updates (e.g., Phase I PDR/CDR, other updates, Phase II PDR/CDR) to assess evolving threat/countermeasures updates. Additionally, the EMD Threat Baseline will need to be defined prior to the start of Phase II.

- Countermeasures impacts, cost/effectiveness, and design analyses

- Threat impacts, cost/effectiveness and design analyses

- Self-defense requirements, cost/effectiveness, and design analyses

- Nuclear, biological, chemical (NBC) protection requirements, cost/effectiveness, and design analyses

- Weapon system vulnerabilities (including aircraft) to support a survivability assessment and planning for EMD Live Fire Test and Evaluation activities

- Adjunct missions requirements, cost/effectiveness, and design analyses (Cruise Missile Defense, Protection of High Value Airborne Assets, Suppression of Enemy Air Defenses, Surveillance)

- Cooperative Engagement Capability (CEC) requirements, cost/effectiveness, and design analyses

- Special classified projects requirements, cost/effectiveness, and design analyses

- EMD system TBM state vector and launch/impact point accuracies, requirements, and design/cost analyses

- Studies to support Authority to Proceed reviews (ATP-1/ATP-2)

- Studies to support the Milestone II Defense Acquisition Board (DAB) review (End of PDRR Phase II)

- Other studies/analyses the Offeror may propose (NLT ATP-2)

Senior engineer/scientist 40%
Mid-level engineer/scientist 40%
Junior engineer/scientist and administrative 20%

Costs and fixed fee shall be shown in Volume IV Section C Task Order Rates by Government Fiscal Year (GFY). Specific ITAMP tasks will not be defined until these efforts are identified, negotiated and authorized.

6.0 VOLUME IV - COST

6.1 Volume Organization

The cost and schedule volume shall consist of the following sections:

Section A - Instant Contract Cost

Section B - Life Cycle Cost Estimate

Section C - Task Order Rates

6.2 Cost/Pricing Information

6.2.1 Cost or Pricing Information Requirements. In accordance with FAR 15.804-5 and 15.805-6, information other than cost or pricing data is required to support price reasonableness or cost realism. Such information shall be submitted using SF 1448. Information shall be provided in accordance with the tailored formats specified hereunder. Use of Contractor formats is encouraged providing that all the required information is available. This information is not considered cost or pricing data, and thus certification is not required in accordance with FAR 15.804-4. Information submitted on the SF 1448 shall be prepared following the instruction in FAR 15.804-6, Table 15-3. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness and none of the exceptions of FAR 15.804-3 apply, the Offeror shall be required to submit certified cost or pricing data.

6.2.2 Cost Credibility. Unrealistically low or high proposed costs or 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 has made an unrealistic proposal. Offers should be sufficiently detailed to demonstrate their cost credibility. The burden of proof for cost credibility rests with the Offeror.

6.2.3 Estimating Techniques and Methods. When responding to the Cost/Price Volume requirements in the RFP, the Offeror and its associated team members/subcontractors may use any generally accepted estimating technique, but they should be explained in detail in the Unpriced Basis of Estimate (UBOE) (see para 7.2) to ensure the Cost to Government (CTG) panel understands how the estimates were developed. Costs in the Cost Volume and information in the UBOE must be referenced to the ITAMP.

6.2.3.1 Aircraft Pricing. The offeror shall clearly identify which approach to pricing the aircraft (CLINs 0003 and 0008) is included in the baseline proposal, i.e., Fixed Price Subject to Escalation or Firm Fixed Price. The alternative pricing of the aircraft shall be included in the 5 page addendum to the Cost Volume (see Table L-2 (1)). The Government will evaluate both pricing arrangements and the one most advantageous to the Government will be included in the definitive contract.

6.2.4 Non-Required Data. Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All dollarized information relating to the proposed cost/price including all required supporting documentation must be included in the section of the proposal designated as the Cost Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

6.2.5 Cost Models. The Offeror will submit a diskette copy of their cost model or spreadsheet that duplicates the logic and formulae reflected in the paper copy of the proposal. The diskette will include operating instructions for the cost model or spreadsheet. Operating instruction should be limited to two pages or less. The diskettes must comply with the following format: Files should be submitted on 3 1/2", double-sided/high density (1.44 Mb) diskettes labeled appropriately. Files should be accessible by an IBM PC compatible computer running MS-DOS 6.0 or later. Files should be .XLS file format (MS-Excel, Release 5.0c) compatible. Files should be checked for viruses before submittal. Specific Offeror cost files are applicable to the Instant Contract cost proposal only. Other parametric models may be used by the Offeror for the valuation of life cycle costs.

6.2.6 Rounding. All dollar amounts shall be rounded to the nearest dollar.

6.2.7 Inflation Rate Table and Explanation. OSD approved inflation indices can be obtained from the world-wide web at "http://www.saffm.hq.af.mil/SAFFM". The funding profile for this contract was inflated with these rates. If rates other than the OSD rates are used, provide the inflation rates only if they are not currently provided to the Offeror's local DCAA/DPRO offices. Identify the title and date of the document with the inflation rates that was provided to the DCAA/DPRO offices. If rates are aggregated from different functions, identify and list individual rates by Government fiscal year. A brief explanation of the source or basis of the rates must be included.

6.2.8 New Mexico Gross Receipts Tax. New Mexico Gross Receipts Tax is assessed for the privilege of performing services in New Mexico. Regulations pertaining to Gross Receipts Tax can be found in the Gross Receipts and Compensating Tax Act, Sections 7-9-1 to 7-9-80.1 NMSA 1978. For assistance, contact the New Mexico Taxation and Revenue Department, 5301 Central Avenue NE, P. O. Box 8485, Albuquerque, NM 87198, (505) 841-8000. The Offeror should demonstrate the method of calculation and identify cost elements and amounts included in the tax base. These cost elements should be where New Mexico represents "first use" of the delivered item.

6.3 Section A - Instant Contract Cost

6.3.1 Organization. Section A shall include the following information: Introduction, index, cost formats, supporting data, SF1448s. Other pertinent information such as GFP/GFE, base support, long lead costs, termination liability costs, and special tooling/test equipment should be included.

6.3.2 Estimating Methodology

6.3.2.1 Management Reduction. If proposed costs have been decreased due to a management reduction, provide a cost element summary and complete rationale.

6.3.2.2 Cost Rationale. Provide rationale to support cost reasonableness, realism, and completeness. Additionally, explain the methodology used to estimate each cost element. As a minimum, provide learning curve parameters and how they were derived, detailed explanations of engineering and manufacturing labor hours (where applicable), how they were developed, and historical data (to include how it relates to the current effort as well as any adjustments that were made). Identify and provide costs (if any) for any warranties included with commercial items (including the aircraft). In the UBOE include a description of what items will have warranties. Narrative support appearing in the Unpriced Basis of Estimate (UBOE) need not be repeated here, but Offerors must make clear references, including page and paragraph numbers, when the UBOE narrative applies.

6.3.3 Explanation Of Required Cost Forms & Formats

6.3.3.1 Standard Form 1448. The Offeror shall submit one SF 1448 for the total program identifying each separately-priced CLIN (FAR 15.804-6).

6.3.3.2 Funding Requirements Summary. Provide Government then-year funding requirements including termination liability, by Government fiscal year.

6.3.3.3 Work Breakdown Structure Cost Summary. Provide a Work Breakdown Structure Then Year Dollar Cost Summary to the WBS levels shown in the following table, by Government Fiscal Year for the Instant Contract.

INSTANT CONTRACT TOTAL BY CWBS IN THEN YEAR DOLLARS
WBS	DESCRIPTION	ITAMP	FY 97	FY98	FY99	ETC.	TOTAL
		REF					COST
00000	ABL PDRR		$	$	$	$	$
10000	Sys Prog Mgmt		$	$	$	$	$
20000	Sys Engineering		$	$	$	$	$
21000	Sys Integ & Analysis		$	$	$	$	$
21100	Oper Anal & Sim		$	$	$	$	$
21200	Risk Management		$	$	$	$	$
21300	Sftwr Integ & Eng		$	$	$	$	$
21400	Int Logistics Spt		$	$	$	$	$
21500	Reliab & Maint		$	$	$	$	$
22000	Ops Analy & Sim		$	$	$	$	$
30000	Air Vehicle		$	$	$	$	$
31000	A/V Integ & Chk		$	$	$	$	$
32000	Aircraft		$	$	$	$	$
33000	Laser		$	$	$	$	$
34000	Beam Control		$	$	$	$	$
35000	Fire Control		$	$	$	$	$
36000	Battle Management		$	$	$	$	$
40000	System Test		$	$	$	$	$
41000	Dev Test & Eval		$	$	$	$	$
42000	Test & Eval Suppt		$	$	$	$	$
43000	Instrumentation		$	$	$	$	$
44000	Data Anal & Rptg		$	$	$	$	$
50000	Ground Support		$	$	$	$	$
51000	Facility		$	$	$	$	$
52000	Support Equip		$	$	$	$	$
60000	Training		$	$	$	$	$
FY Totals

6.3.3.4 List of Subcontractors/Team Members and/or Material Vendors. For subcontract effort or procurement of material over $1,000,000, submit a listing of the proposed subcontractors and inter-divisional transfers showing (a) the supplier, (b) description of effort or material, (c) type of contract, (d) price and hours proposed by each, (e) price and hours included in prime contractor's proposal to the Government, (f) identifying nomenclature or identifying part numbers valued over $1,000,000, and (g) price of contract or quotation for items listed in (f) exceeding $1,000,000. Hour information for subcontractors of non-developmental or commercial off-the-shelf hardware is not required.

6.3.3.5 Commonality With Other Programs. Any cost reductions made in your proposal that are specifically attributed to commonality with other programs, company-funded efforts, or capitalization of equipment must be supported with the following:

(1) Commonality	Identify the specific program(s) and why it is applicable. Address the cost allowability and allocability of this action per FAR and your CAS disclosure statement.
(2) Company Funded Efforts	Identify the specific efforts, the planned start and end dates, the applicability to the current solicitation, the source of company funding and how you plan to account for or allocate these costs in accordance with generally accepted accounting principles, and your CAS Disclosure Statement, if applicable.
(3) Capital Equipment	Identify the specific item(s) capitalized and what other applications exist for the equipment, provide corporate approvals for each action, address the cost allowability and allocability of the action per the FAR and your CAS disclosure statement.

6.4 Section B- Most Probable Life Cycle Cost (MPLCC) Estimate

a. The CTG Panel will develop a Most Probable Life Cycle Cost (MPLCC) for all future phases of the program: EMD, Production, and Operations and Support. The CTG panel will use both data supplied by the Offeror (after review and adjustment, if necessary, by the technical evaluators) and Government historical data to develop the estimates. The CTG will determine the most appropriate estimating methodology for the items and phases being estimated including but not limited to parametric estimating, both established models and Cost Estimating Relationships developed from historical data, grassroots buildup, and analogous techniques. Operations and Support will be estimated using Air Force Instruction (AFI) 65-503 "Air Force Cost and Planning Factors" and in accordance with the Office of the Secretary of Defense (OSD) Cost Analysis Improvement Group (CAIG) Operating and Support Cost-Estimating Guide, May 92. For O&S the CTG panel may also use the "Cost-Oriented Resource Estimating (CORE)" model. The CTG panel will also develop tests of reasonableness for the MPLCC from Government historical data. The Government plans to use the Automated Cost Estimating Integrated Tools (ACEIT) module to develop the MPLCC. The MPLCC will include the following:

(1) Total EMD program including one (1) prototype production unit (i.e. the EMD ABL) (begins in FY03 and completes in FY05).

(2) Total Production program including five (5) Production units and refurbishment of the PDRR and EMD units to a production configuration (buy years: FY04, FY05, and FY06).

(3) O&S Ramp-Up period

(4) Twenty years of Steady-State Operations and Support

(5) Other Government Costs for all phases

(1) Total EMD program including one (1) prototype production unit (i.e. the EMD ABL) (begins in FY03 and completes in FY05). (Note: The aircraft is purchased on the instant contract.)

(2) Total Production program including five (5) Production units and refurbishment of the PDRR and EMD units to a production configuration (buy years: FY04, FY05, and FY06).

(3) O&S Ramp-Up period (as necessary for Offeror's delivery schedule).

(4) Twenty years of Steady-State Operations and Support.

(5) Other Government Costs for O&S phase of the program for Primary Authorized Aircraft and Backup Aircraft.

(6) Include the cost of warranties for all phases if the warranties are separate from the commercial item purchase price (including aircraft).

(1) WBS number, title, and definition.

(2) Time-phased estimate by Government fiscal year.

(3) Estimating methodology including rationale, throughput, input variables, and sample calculations.

(4) Rationale for adjustments made to equations (learning curve, allocations, factors, affordability, etc.).

6.5 Section C - Task Order Rates.

This section should include labor category rates for Advanced Technology Studies (CLIN 0006) and associated Other Direct Costs (ODCs) (CLIN 0007) as described in paragraph 5.6.2.

7.0 VOLUME V - SCHEDULE

7.1 Integrated Master Schedule (IMS)

7.1.1 Integrated Master Schedule (IMS). The IMS shall be prepared in Offeror format. It shall indicate activities required to accomplish the Events, Accomplishments, and Criteria in the ITAMP. IMS activities should be limited to the minimum number of activities required to explain the program schedule including planning and mitigation of the high and moderate risk areas as defined in para 5.3. A goal of not more than 500 tasks should be a sufficient level of detailed planning. For the execution of the program in PDRR, it is anticipated you will require an IMS and ITAMP with significantly more detailed tasks. You are to "roll up" the tasks to the top priority tasks to be evaluated by the Government. Any "roll up" tasks must contain the logic relationships to other tasks.

7.1.1.1 IMS Definition - An integrated program network schedule to include events defined in the ITAMP with further detail to include all of the tasks and activities required to complete each milestone and event. The IMS will be directly traceable to the ITAMP and the CWBS (This can be accomplished using a traceable numbering system). Activities and tasks will be included to account for the entire PDRR program under contract. Include activities for all CWBS elements included in the ITAMP. Definitions and the key elements in the integrated network are described below.

7.1.1.2 Other IMS Definitions

Milestone/Event - A specific definable accomplishment in the program/project network, recognizable at a particular point in time.

Activity/Task - A time consuming element, e.g. work in progress between interdependent events, represented by an activity box. Activities are numbered and are contained within an activity box. The left side represents the beginning of the activity, and the right side is the completion of the activity.

Duration - The length of time estimated to accomplish an activity.

Relationship - A line that defines how two activities or events are logically linked. It can take up to four forms:

(1) Finish to Start (FS) - An activity must finish before another can start.
(2) Start to Start (SS) - An activity depends on the start of another activity.
(3) Finish to Finish (FF) - One activity cannot finish until another activity is finished.
(4) Start to Finish (SF) - An activity cannot finish until another activity starts.

Predecessors - List of tasks upon which a specific task depends. Each predecessor is linked to the task by a specific type of relationship (FS, SS, FF, SF) and a lead or lag time. In Microsoft Project, for example, "14FS+3d" means that task 14 is a predecessor, with a finish-to-start relationship and a 3 day lag time. To show a lead time, the predecessor would be entered at "14FS-3d".

Successors - List of tasks that depend on a specific task. Each successor is linked to the task by a specific type of relationship (FS, SS, FF, SF) and a lead or lag time. In Microsoft Project, for example, "14FS+3d" means that task 14 is a successor, with a finish-to-start relationship and a 3 day lag time. To show a lead time, the successor would be entered as "14FS-3d".

Constraint - A restriction or limitation you set on the start or finish date of a task. For example, you can specify that a task must start on a particular date or finish no later than a particular date.

Total Slack or Float - Extra time available on an activity before it will impact an activity on the critical path.

Lead - The amount of time of overlap between where a successor task begins and a predecessor task completes.

Lag - The amount of time between the end of a predecessor task and the beginning of a successor task.

Critical Path - A sequence of activities in the network that has the longest total duration through the program/project. Activities along the critical path have zero or negative slack/float. It should be easily distinguished on the report formats.

Target Start (TS) - Date of when an activity should start.

Target Complete (TC) - Date of when an activity should finish.

Actual Start (AS) - Actual start date of an activity.

Actual Finish (AF) - Actual finish date of an activity.

Early Start (ES) - The earliest start date an activity can begin without violating the precedence relationships.

Early Finish (EF) - The earliest date an activity can end.

Late Start (LS) - The latest date an activity can start without delaying the program/project target completion date.

Late Finish (LF) - The latest finish date an activity can have without affecting the program/project target completion date.

Gantt Chart - A graphical display of program activities and key milestones that depict work activities. Activities are represented by bars showing the length of time for each activity. Gantt charts should be supported by and consistent with the IMS.

7.1.1.3 IMS Contents. The intent of the schedule is to obtain a functionally integrated understanding of the proposal with clear tracks between the technical, cost, schedule, management, etc., sections in a way that provides the Government confidence that the program is executable for the resources indicated.

Section 1 - Integrated Master Schedule Network - Includes the networked IMS. A 36" wide single sheet plot of continuous roll network paper is preferred.

Section 2 - Proposed Durations - Most likely durations for each event, activity, and task on the network.

Section 3 - Schedule Rationale - Explanation of the derivation of the Section 2 durations.

7.1.1.3.1 Section 1 - Integrated Master Schedule (IMS) Network

a. The Offeror shall provide an IMS network schedule. The IMS network schedule shall show the critical path. All network schedule information shall be consistent with the ITAMP milestones.

b. The Offeror shall provide a traceable numbering system that ties the activities in the network schedule to the ITAMP and the WBS. The IMS network schedule shall contain a sufficient number of activities to provide a detailed understanding of the program. The Offeror shall provide a 3 1/2-inch floppy disk containing the network schedule. The offer shall describe the software application used for building the network schedule. Additionally, the Offeror shall describe how the network scheduling program to be used will be made compatible with Microsoft Project 4.0. In addition to the files submitted on disks, the Offeror shall provide hard copies of the schedule in the following formats: IMS network schedule and Gantt charts to match the level of detail provided in the ITAMP. The Offeror should include any other logic needed to recreate the schedule from the tabular data (i.e., constraints, directed or fixed dates or other assumptions not readily apparent in the tabular format).

c. The schedule information submitted will be used by the CTG panel in evaluating the logic and in the development of the Most Probable Schedule (MPS) based on a Schedule Risk Assessment (SRA). The Government will use Microsoft Project, RISK+ Verson 1.0 to perform the SRA.

7.1.1.3.2 Section 2 - Proposed Durations

a. The durations provided by the Offeror for each event, activity, task, and milestone in the network schedule shall represent most likely durations. Also provide, in tabular format, the following data for each event, activity, task, and milestone in the IMS:
Task Number Early Start
Task Name Early Finish
Duration Float
Predecessors Lead Time
Successors Lag Time
Relationship (FS, SS, FF, SF)

b. The Offeror shall include any other logic needed to recreate the schedule from the tabular data, i.e., directed or fixed dates or other assumptions not readily apparent in the tabular form. The Offeror shall let the logic determine the network and minimize the use of constraints.

7.1.1.3.3 Section 3 - Schedule Rationale

a. The Offeror shall provide the ground rules and assumptions used in estimating the durations shown in the IMS network schedule (i.e., historical data, experience on similar efforts, vendor schedules, number of workdays per week, number of shifts, company holidays, etc.). In addition, the Offeror shall provide supporting narrative for the network diagram that explains the basis for the estimated durations for those activities on the critical path(s) and for those activities designated as high risk. Any unusual aspects of their proposed approach to the program shall also be described as well as the rationale for imposed constraints. Narrative support appearing the UBOE need not be repeated here, but Offeror must make clear reference including page and paragraph numbers, when the UBOE narrative applies.

b. For any activities that have relationships other than Finish to Start (FS), the Offeror shall provide a brief narrative of why these activities do not have a FS relationship and how the respective relationship was determined and the lead or lag estimated.

c. Because a Most Probable Schedule (MPS) will be developed based on a Schedule Risk Assessment (SRA), the Offeror shall also provide minimum and maximum durations (in addition to the most likely durations provided in the schedule) for all moderate and high risk activities to reflect risk planning and mitigation activities.

7.2 Attachment 1 - Unpriced Basis of Estimate (UBOE)

7.2.1 The unpriced BOE shall be submitted for the PDRR Instant Contract only as costed in Volume IV, Section A and include all labor hours, unpriced bills of material, unpriced travel and other direct costs (i.e., communications, reproductions, etc.) to the same detail required in the Cost Proposal; however, NO COST INFORMATION SHOULD BE PROVIDED IN THIS ANNEX. The labor hours, unpriced bills of material, unpriced travel and other direct costs shall be clearly attributed to either the prime Contractor, any subcontractors, any interdivisional work, or any consultants. UBOE information is not required for subcontractors/suppliers of non-developmental or commercial off-the-shelf items. Cost data for non-developmental or commercial off-the-shelf items shall be included in the Cost Volume. The rationale for the proposed labor hours should include the following:

(a) A Project Manning Summary shall be prepared to denote the number of labor hours, equivalent manning, and labor skills allocated to support each ITAMP task. It is required that the submission of the Project Manning Summary(ies) be structured to match the ITAMP and cost proposals.

(b) Describe how the quantity and mix of labor hours were estimated (Identify labor hours by individual IPTs and by Government fiscal year for evaluation). If engineering estimated hours were used, show the rationale for each estimate. Correlate these engineering estimated hours to the ITAMP.

(c) Identify specific historical information that was considered in arriving at the estimated labor hours. Show how that information was used to develop the proposed labor hours.

(d) State whether or not any contingencies are included in the proposed quantities.

(e) Estimating techniques should be explained in sufficient detail. Estimates based on judgment should be supported by (i) description and schedule of work to be accomplished, (ii) quantity of work, (iii) skill levels by time (work force loading), (iv) special conditions, if any, and (v) logic for supporting estimated hours.

7.2.2 Identify cross-references to the technical design package for all hardware whether developed/produced by the prime Contractor or by a team member/subcontractor.

7.2.3 Describe each computer software configuration item (CSCI) to include subcontracted software. In addition, the Offeror shall identify all software purchased, developed or modified for laboratory use if the cost of such software will be a charge to this contract. The Offeror shall identify the name of each CSCI and provide a cross-reference to the applicable hardware as described in the technical design package.

8.0 VOLUME VI - PAST PERFORMANCE

8.1 General.

Each Offeror shall submit a present and past performance volume. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the development of performance risk assessments.

8.2 Early Proposal Information

The past performance volume containing information for each relevant Government contract should be sumitted 29 days prior to proposal submittal. Failure to submit Early Proposal Information will not result in Offeror disqualification.

8.3 Relevant Contracts

Submit information on contracts that you consider relevant in demonstrating your ability to perform the proposed effort. This information may include data on efforts performed by other divisions, corporate management, critical subcontractors, or teaming contractors, if such resources will be brought to bear or significantly influence the performance of the proposed effort.

Provide a list of up to twenty of your most recent, relevant contracts, to include the information identified below. These contracts should further demonstrate your ability to perform the proposed effort. The Government will use information provided in this Volume together with information obtained from other sources to develop performance risk assessments.

(1) Contract number
(2) Total dollar value
(3) Procuring agency (or company if non-Government or subcontract)
(4) Title of contract
(5) Customer program manager, phone number and address
(6) Description of effort and similarities with this SOW
(7) Name, address and phone of PCO and ACO
(8) Period of performance
(9) Contract type
(10) Basis for award (competitive/sole source)

8.3.1 Specific Content. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and may include a discussion of significant achievements or explain past problems they consider relevant to the proposed efforts as well as past efforts to identify and manage program risk. Categorize the relevant information into the specific evaluation areas/factors used to evaluate the proposal.

9.0 VOLUME VII -ADMINISTRATIVE PROPOSAL

9.1 Model Contract/Representations and Certifications.

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The Offeror's proposal shall include a signed copy of the Model Contract, and Sections A through K. This includes:

9.1.1 Except as otherwise stated in this volume or elsewhere in the RFP, changes or alterations to any portion of the proposed contract submitted with the proposal are not authorized.

9.1.2 The contract will consist of Section A, SF 33, Solicitation Offer and Award, and Sections B through J (including exhibits and attachments) of the RFP, as amended. Complete and submit the model contract; submit Section K in its entirety. Page numbers on pages added to the contract shall retain the sequence of the RFP with alphabetic suffixes for each page added (e.g. 7A, 7B, etc.). Complete and return the SF33.

9.1.3 Complete the pricing schedule in Section B to show prices for applicable CLINs. Modify Section B by adding separate pages to reflect any additions or modifications to the CLINs. All dollar amounts shall be rounded to the nearest whole dollar.

9.1.4 Exceptions taken to terms and conditions of the model contract, to any of its formal attachments, or to other parts of the RFP shall be identified. Each exception shall be specifically related to each paragraph and/or specific part of the RFP to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule and cost and specific requirements of the RFP. This information shall be provided in the format and content of Table L-2 (2)

RFP Document	Paragraph/Page	Requirement/Portion	Rationale
SOO, TRD Model Contract, etc.	Applicable Page and Paragraph Numbers	Identify the requirement or portion to which exception is taken	Justify why the requirement will not be met

9.1.5 The offeror must submit proposed security to support proposed Government financing of CLINs 0003 and 0008 and justify the adequacy of this security in accordance with FAR 32.202-4. Note: The Contractor's financial condition may be accepted as adequate security for providing commercial advance and interim payments subject to review of information submitted by the offeror. Nothwithstanding Government acceptance of the Contractor's financial condition as adequate security, the Government reserves the right to require other security under paragraph (c) of FAR 52.232-29, "Terms for Financing of Purchases of Commercial Items," in the event the Contractor's financial condition changes and is no longer determined to be adequate security by the Contracting Officer.

9.2 Other Information Required.

9.2.1 Authorized Offeror Personnel. Provide the name, title and telephone number of the company/division point of contact regarding source selection decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

9.2.2 Non-Government Advisors. Offerors are advised that the following contractors will participate as non-Government advisors in the evaluation of proposals: Aerospace Corporation, BETAC, GRAM Inc., Los Alamos Technical Associates (LATA), Lincoln Laboratory, Mission Research Corporation (MRC), MITRE, RDA-Logicon, S-Systems, the Optical Sciences Company (tOSC), Tecolote, and W.J. Schafer Associates. These advisors will be authorized access to only those portions of the proposal data and discussions that are necessary to enable them to provide specific advice on specialized matters or on particular problems. The non-Government advisors will not be allowed to determine strengths and weaknesses, establish initial or final assessments of risks, or actually rate or rank Offeror's proposals. Any objection to disclose information to these non-Government advisors should be provided in writing before the date set for receipt of proposals and shall include a detailed statement for the basis of the objection. Include in your proposal specific authorizations for release of information to these contractors. The ABL Independent Review Team (IRT) may also act as advisors to the technical evaluators.

9.2.3 Government Offices. Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

9.2.4 Company/Division Street Address. Provide company/division's street address, county and facility code; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

9.2.5 CAS Disclosure Statement. Provide a summary of changes to estimating, accounting practices or CAS Disclosure Statement.

9.2.6 Attachments to the Model Contract. The Offeror shall provide the following as attachments to the model contract.

9.2.6.1 Subcontracting Plan. Include a Subcontracting Plan in accordance with (IAW) FAR 19.702. The plan must be approved by the PCO prior to contract award.

9.2.6.2 GFP and/or Base Support Requirements. The goal is to minimize the use of GFP. If the Offeror requires the use of GFP the Offeror should provide a listing including quantity, federal stock number, nomenclature, date needed and duration of availability, rental value per FAR Section 45.1 and 45.2, reason for need and provide cross reference to cost/price volume paragraphs which pertain to GFP and/or base support. The Offeror should also provide the written authorization from the cognizant ACO, as applicable. The Offeror shall supply this information in the format shown in Table L-2 (3).

Quantity	Federal Stock #	Nomen-clature	Duration of Need	Rental Value	Reason for Need	Cross Ref. to Cost Prop

9.2.6.3 Use of Supercomputing Facilities. The Offeror shall estimate the need for supercomputing resources outside their own facilities for developing and refining simulations and models as follows:

a. Estimate number of "GigaFLOP-hours" required for processing; a "GigaFLOP-hour" is defined as one hour of processing time on a single C90 supercomputer node.

b. Estimate memory size requirements in Mega-words (64-bit words).

c. Estimate number of bytes of disk storage required.

d. Estimate use of archival media (tape backup, etc.) required, both in terms of usage time and number of bytes of storage.

e. Estimate any other parameters or special services (i.e., video, visualization, etc.) which would typically result in fees being charged by supercomputing facilities.

9.2.6.4 Associate Contractor Agreements. Include Associate Contractor Agreements, if applicable.

9.2.6.5 Other Contractual Documents. The ITAMP (Volume III Section A), Compliance Documents (Volume III Attachment 2), Data Requirements (Volume III Attachment 5), and the Target Option (Volume III Attachment 6) will all be included as part of the contract document.

10.0 RFP CROSS REFERENCE MATRIX

The RFP Cross Reference Matrix (Figure L-2(4)) is intended to reduce internal RFP inconsistencies and aid in proposal preparation and evaluation. In the event of a conflict between this matrix and any other section of the RFP, the RFP section shall take precedence. The PCO and project officer are jointly responsible for completing columns 1, 2, 3, and 4 of the matrix and the Offeror is responsible for completing columns 5, 6, 7, 8 and 9 and returning the matrix with your technical proposal volume.