Amendment 2 to Brakes Modification RFP N00019-09-R0296.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

SECTION J -LIST OF ATTACHMENTS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS, CONDITIONS & NOT

L-[1]

CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(10/28/2008)

ADDITIONAL INSTRUCTIONS FOR PREPARATION AND SUBMISSION OF PROPOSALS:

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information concerning the following areas to enable Government personnel to fully ascertain capabilities of the Offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise and capability as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the requirements and associated risks, is able, willing and competent to devote the resources necessary to meet the requirements, and has valid and practical solutions for all requirements and potential risk areas. Respond to all requirements of the solicitation. Do not alter or rearrange the solicitation. The burden of proof for all the evaluation factors identified in this solicitation rests with the Offeror. Offerors are advised that the Government may incorporate into the final contract enhancing features included in the Offeror’s proposal deemed beneficial to the Government. With the exception of the Price Volume, no cost or pricing information should appear in any other volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the various work efforts, support, and management approaches, as well as price, to be meaningfully evaluated without discussions. Statements that the prospective Offeror understands, can or will comply with the specifications and paraphrasing the requirements or parts thereof without supporting information are considered inadequate and may render a rating of unsatisfactory.

The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. Failure to clearly and positively address a specific factor or subfactor may be considered a deficiency. There is no need to repeat information in more than one volume. If an overlap exists, the detailed information should be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal are neither necessary nor desired.

Offerors are expected to comply with all requirements of the RFP. Taking exception or deviating from any term or condition of the RFP may make an offer unacceptable and the Offeror ineligible for award unless the RFP expressly authorizes such an exception or deviation with regard to that specific term or condition. The Government may consider any exception or deviation to any term or condition of the RFP that is not expressly authorized by the RFP to be a deficiency, as defined in FAR 15.001.

Throughout these instructions, the term “Principal Subcontractor” is defined as a subcontractor that provides at least 10% of the proposed total cost/price (excluding the Offeror’s profit/fee), for the contract. The term “Team Member” is defined as an entity that makes up a joint venture or single legal entity (JV/SLE) that is formed for the purpose of responding to this solicitation. The JV/SLE is considered to be the Offeror. The term “Critical Team Member” is defined as an entity of the JV/SLE that performs a critical function in the performance of the resulting contract, whether it is technical or financial, and/or has an important role in any high or medium risk areas identified in the Offeror’s proposal.

For the purpose of this acquisition, relevance is defined as something that has a logical connection with the matter under consideration. Such aspects or relevance include the type of effort (e.g., development, production, repair), the type of requirements (e.g., weapon systems, information systems, engineering services, scheduled depot maintenance), service similarity, service complexity, contract type, contract dollar value, the division of the company that will perform the work, and participation of Principal Subcontractors, Team Members, or Critical Team Members.

2.0

PROPOSAL FORMAT

Written proposals must be formatted using a Times New Roman 12 pt normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. When foldout pages are used, they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 pt font and should contain a grid that allows values to be read directly from the graph to the same accuracy a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented.

3.0

PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal Instruction. The proposal shall be structured such that its paragraph numbers/letters correspond to the Proposal Instructions paragraph numbers, although the Offeror may add lower tier subparagraphs. The Offeror shall provide reasons if it does not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third and fourth parts correspond to the volume, book, section, and element, etc., in the Offeror’s proposal.

Each volume of the proposal shall be submitted as an original with additional copies as specified in the table below. In addition, the Offeror shall provide an electronic file fully compatible with Microsoft Office 2000 and the latest Adobe Acrobat reader on a CD-ROM. The Price Volume shall be provided on a separate CD-ROM. Each CD-ROM is to be labeled for content with the Offeror’s name. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy shall take precedence. Page limitations for each volume, if any, are also specified in the table below as follows (title and table of contents pages do not count towards page limit). Proposal pages beyond a specified maximum limit, if any, will not be reviewed as part of the evaluation. Each Volume shall be provided in a separate 3-ring binder. Each binder shall be an appropriate thickness for the number of pages it contains (e.g., a 30-page book shall not be placed in a 2-inch binder).

Information that may be submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information requested in Part B Specific Instructions. Annexes do not have page limitations. The authorized Annexes are summarized in the table below.

1 Original/2 Copies

AND WAIVERS

All exceptions, deviations, waivers and alternate terms and conditions must be addressed in Volume 5. If none exist, a one page Volume 5 may be placed in the same binder as Volume 1, Executive Summary, with a statement to that effect.

Each volume must contain the following information. Please use tabs and dividers.

Cover and title page

Title of proposal

Offeror’s name, address and POC

RFP number

Proposal volume/book number

Copy number

Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

Master Index - The Master Index provides a single integrated index for the entire proposal and ensures that all requirements are addressed and easily accessible to the evaluators. This index should cross reference the proposal volume and paragraphs to specific RFP requirements and CLINs, as well as other parts of the proposal that contain relative information. The Master Index is not included in the page limitation.

4.0

PROPOSAL SUBMISSION

Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP. However, it is requested that Volume 2, Past Performance, be submitted two weeks prior to the submission date/time specified on Standard Form 33 (Block 9).

Proposals shall be submitted via United States Postal Service or through a commercial carrier using the address provided below. Proposals shall not be submitted by facsimile or electronically via email.

Naval Air Systems Command

Code: AIR-2.2.4.3.3, Meghan Huett

21983 Bundy Road, Building 442 Patuxent River, MD 20670-1547

Solicitation Number: N00019-09-R-0296

Hand carried proposals may be delivered to the address above, attention Meghan Huett.

5.0

PROPOSAL PACKAGING:

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible, grouping like volumes to the maximum extent possible. Each carton shall be single person portable. However, the Master Set, as described below, shall be packaged separately and marked as the Master Set. Each box should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each box should be stamped or marked “For Official Use Only” and “Source Selection Information – See FAR Subparts 2.101 and 3.104”.

The Master Set shall include one paper copy and one electronic copy, the signed SF-33 with the acknowledgement of all solicitation amendments, and a completed Section K, Representations, Certifications and other Statements to Offerors. These forms shall be included in the Volume 1, Executive Summary.

6.0

CLASSIFIED DATA

All proposals must be UNCLASSIFIED

7.0

SOLICITATION CHANGES

For any changes and additional information for the solicitation please go to website:

https://www.fbo.gov

Solicitation Number N00019-09-R-0296

8.0

TECHNICAL LIBRARY

Technical Libraries containing information directly related to the requirements of this solicitation are available to all Offerors by appointment. The main library is located at Patuxent River, MD, and the libraries for training information are located in Oklahoma City, OK. A SECRET clearance is required to obtain access to the main library at Patuxent River, MD.

The locations of the libraries are listed below. For further information on access to the libraries, please contact the POC for each library.

1) Department of the Navy

Naval Air Warfare Center Aircraft Division

PMA 271 Information Management Center, Bldg 1652

22487 Cedar Point Road Unit 1

Patuxent River, MD 20670-1609

POC: Ms. Carol Mattingly

Phone: (301) 342-6743

E-mail: carol.mattingly.ctr@navy.mil

2) Officer in Charge

CNATT Detachment Tinker

7641 Mercury Rd. Bldg 830

Tinker AFB, OK 73145-8702

POC: AM1 Robert Hudson

Phone: (405) 739-5894

E-mail: robert.e.hudson@navy.mil

3) Officer in Charge

CFCTS Detachment Tinker

7641 Mercury Rd. Bldg 830

Tinker AFB, OK 73145-8702

POC: Mr. Nam Nguyen

Phone: (405) 739-3242

E-mail: nam.nguyen@navy.mil

PART B SPECIFIC INSTRUCTIONS

1.0

VOLUME 1: EXECUTIVE SUMMARY

Note: This volume shall not contain any reference to cost or price aspects of the offer.

The purpose of the Executive Summary is to provide the evaluators with an overview of the Offeror’s proposal and strategy. The Offeror shall include the following in this volume:

i.

A concise abstract of the Offeror’s strategy for each of the evaluation criterion contained in the solicitation.

ii.

Offeror Summary Table: The Offeror shall complete the table below. The Offeror should include all Subcontractors and Team Members that will be involved with the performance or management of the program work and should list all sites where the work will be performed. If a subcontract or teaming arrangement is proposed, identify the work share, distribution elements, and ratios that each Subcontractor or Team Member will perform using the table below. Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

Name

(Indicate Prime, i.e., the Offeror, Subcontractor, or Team Member

iii.

Signed SF33 for basic solicitation and acknowledgement of all amendments

iv. Signed Representations, Certifications and Acknowledgements or OnLine Representations and Certifications Application (ORCA) reference v.

Affirmation of no Exceptions, Deviations or Waivers if Volume 5 is not being submitted as part of the proposal.

2.0 VOLUME 2 – TECHNICAL - This volume consists of two books – 1) Design Approach and 2) Program, Schedule and Capability.

Note: This volume shall not contain any reference to cost or price aspects of the offer.

As previously stated, please provide each book in a separate 3-ring binder. In this volume, provide the information described below:

2.1 Book 1 – Design Approach ‑ In this book, the Offeror shall describe the technical approach proposed by the Offeror to fulfill the tasking identified in the Statement of Work (SOW). The description shall convey the Offeror's thorough understanding of the tasks required to meet contract objectives including the unique aspects of the E-6B fleet operations (system concept of operation), engineering, and logistic support structure. The description shall also identify the proposed tasks to achieve the requirements as identified in the SOW.

The end results for the E-6B brakes initiative is weight savings. The Offeror’s design approach shall provide the minimum 800 lbs weight savings for the combined wheels and brakes plus the additional minimum of 200 lbs for the tires. The Offeror shall propose lighter brakes and radial tire manufacturers that would be best fit for the Fleet’s needs to the E-6B Program Office. The proposed design solution shall be based on maintenance, engineering, logistics, financial, and programmatic parameters. The Offeror shall propose the total amount of weight saved by transitioning to lighter brakes and radial tires.

The design of the lighter brakes and radial tires is to ensure that the lighter brakes and radial tires are compatible with the existing hydraulic and pneumatic (emergency) braking system, and with the Mark II Anti-Skid System. The proposed lighter brake design and/or radial tires shall be compatible with the primary and/or emergency braking system or the anti-skid system.

The Offeror shall demonstrate that they have worked with braking system(s) on either military or commercial aircraft, that shall include rotors, stators, hydraulic and/or pneumatic braking systems, check valves, butterfly valves, deboost valves, or any other braking system components. The design of the lighter brakes shall be such that it shall minimize the parts that need to be modified for lighter brake replacement. A list of modified parts shall be presented.

2.1.1 Systems Integration – The Offeror shall describe their approach to incorporate their proposed lighter brakes and radial tire design modifications into the existing E-6B aircraft. System hydraulic power, component cooling times, crash safety, and weight and balance shall be included in this section. As a minimum, the following areas should be addressed:

2.1.1.1 Mission Systems and Component Architecture – The Offeror shall define how the proposed lighter brake and radial tire modifications will be integrated with the existing E-6B systems. The Offeror shall describe how the legacy systems will interface with the lighter brake system, including hydraulic components, mechanical components, electrical system components, and other systems with which the brakes operate. The Offeror shall identify all tasks and procedures into which the proposed design will integrate, and how such integration relates to the associated weight reduction. The Offeror shall identify system attributes that allow for crew workload sharing and enhanced coordination.

2.1.1.2 Brake Temperature Monitoring System Software Architecture/Design (if needed; to be used for testing) – The Offeror shall describe the overall software architecture and design for the lighter brake modifications, specifically with the Brake Temperature Monitoring System (BTMS). The Offeror shall also identify the features of the hardware/software design which ensure hardware/software independence.

The Offeror shall also describe how the BTMS will interface with each thermocouple, the electrical requirements of the Brake Temperature Monitoring Unit (BTMU), and how the BTMS information is to be read, used, stored, and collected during the test phase of the lighter brake effort.

2.1.2 Subsystem Designs -

2.1.2.1 Hydraulic Braking System - The Offeror shall describe their proposed hydraulic interface design. The Offeror shall propose how the lighter brakes and radial tires will interface with the existing hydraulic braking system, including, but not limited to:

· Determination if de-boost valve removal is necessary.

· Identification of optimum system braking pressure.

· Whether lighter brakes would be compatible with 46” X 17” radial tires.

2.1.2.2 Airframe – The Offeror shall explain how the lighter brake and radial tires interface with the airframe. This includes maximum (not to exceed) brake torque requirements, impact if brake torque requirements are exceeded (inspection requirements, inspection or test intervals, etc.), and mitigation strategies. The Offeror shall also explain how the brake torque requirements affect the airframe and wing stresses.

2.1.2.3 Radial Tires – The Offeror shall recommend a component radial tire size that is compatible with the proposed lighter brake design and the dimensions inside the E-6B wheel well.

2.1.2.4 Maintenance Requirements - The Offeror shall describe maintenance requirements of the lighter brakes, radial tires, and the component hydraulic system (if some or all of the hydraulic system changed). The maintenance requirements shall include, but are not limited to:

-Recommended inspection interval(s).

-Recommended maintenance personnel rate for each inspection/test interval.

-Detailed inspection requirements.

2.1.2.5 Pneumatic (Emergency) Braking System – The Offeror shall describe how the proposed lighter brakes and radial tires shall interface with the pneumatic braking system, including recommended system braking pressures, estimated braking distances (unless classified or source selection sensitive information) based on wet/dry conditions, and how the pneumatic braking system will interface with the BTMS.

2.1.2.6 Trainers – The Offeror shall describe their approach for the design and build of the lighter brake Trainer modifications. Trainer plans shall include a preliminary list of faults that can be inserted into the various trainers to allow for maintenance and trouble shooting training. Differences between the trainer kits and the aircraft kits shall be identified.

The Offeror shall also explain how the trainer software requirements shall be integrated with the E-6B trainer assets. The software is used to train E-6B pilots, flight engineers, and maintenance personnel on the use and integration of lighter brakes.

2.1.3 Logistics -

2.1.3.1 Overall Approach - The Offeror shall describe its technical approach to provide cost-effective and timely accomplishment of all logistics requirements identified in the SOW, including hardware and software/firmware (flight computer operational changes, etc.). This description shall include all ten logistics elements plus environmental impact reductions, and provide a level of detail which demonstrates working knowledge of the Government's Logistics Management Information (LMI) program, Integrated Product Team (IPT) philosophy, Contractor Logistics Support (CLS) program, spares and Support Equipment acquisition process, NATOPS and other technical manual development processes. Additionally, the Offeror shall address the requirement for the most effective location for Engineering Technical Services during the interim-support period. Contract Data Requirements List (CDRL) items contained in this solicitation are to be reviewed by the Offeror with the intent of ensuring due dates for deliverables are realistic.

2.1.3.2 Supportability – The Offeror shall describe the approach it will employ to ensure that each system and subsystem, including software and firmware, replaced or modified as part of the Brake Program, meets system peacetime readiness and wartime utilization requirements. System design characteristics, coupled with logistics resources (including manpower) will be addressed on how they will facilitate ease of maintenance, including inspections and remove/replace and repair requirements (if any).

2.1.3.2.1 Operations and Sustainment cost – The Offeror shall define and describe the total ownership cost of their proposed solution. This will include providing the technical and cost data for the proposed solution.

2.1.3.3 Reliability – The Offeror shall describe the approach it will employ to ensure that each system and subsystem, including software and firmware, replaced or modified as part of the E-6B Brake Effort meets the desired reliability targets. A description of the design features that will ensure that the Offeror’s design will meet reliability requirements shall be included. The Offeror shall explain, using a Work Breakdown Structure (WBS) or block diagrams, consequences of failures. Estimated factors such as Mean Time Between Failure (MTBF), Mean Time To Overhaul (MTTO), and the design life of each major component of the lighter brakes and radial tires shall be provided.

2.1.3.4 Maintainability – The Offeror shall describe the approach it will employ to ensure that each system and subsystem including software and firmware replaced or modified as part of the Brake Program will meet the agreed-upon maintainability targets. Skill levels, and any unique procedures that may be required to support the O to D maintenance concept, and that will facilitate maintainability, shall be specified. Estimated factors such as Mean Time To Repair (MTTR), whether tasks are On-Condition or Hard-Time, and any lubricating or other preventative maintenance tasks shall be provided.

2.1.3.5 Design Interfaces- The Offeror shall describe the design interface activities and processes that will be employed to ensure that each system and subsystem including software and firmware replaced or modified as part of the Brake Program addresses Design Interface. The description of the design interface activities as they pertain to the Systems Engineering process must include, but are not limited to; (1) optimizing use of logistic resources (manpower, skill levels, support equipment, etc), (2) avoiding excessive logistic resource requirements, (3) utilizing configuration and other systems engineering data as input to Supportability Analysis (S Analysis).

2.1.3.6 Training - The Offeror shall fully describe training proposed for Development/ Operational Test, Cadre and Instructor personnel to ensure that training provided under the Brake program complies with the requirements of the SOW. This discussion shall address maximum class size, composition, plan for student handouts, class schedules, and preparation of Training Material Change Packages.

2.1.3.7 Reliability-Centered Maintenance (RCM) – The Offeror shall demonstrate understanding of the NAVAIR 00-25-403 RCM processes. The Offeror shall understand the basic RCM concepts, and be able to demonstrate how those concepts relate to the lighter brakes and radial tires. Factors such as the probability of failure, criticality determination, inspection interval requirements (potential failure and functional failures), cause of and consequences of any failures, and inspection manhours shall be addressed. The Offeror shall finally demonstrate how the proposed inspection requirements shall fit into the existing E-6B maintenance concept.

2.1.4 Aircraft Integration - The Offeror shall address their aircraft integration approach for the Lighter brake design. Identify all hardware interfaces, component heat loading estimates, power/electrical impacts, heating and cooling impacts, human factors, aircraft structural impacts, and weight and balance impacts.

2.1.5 Test Plan(s) – The Offeror shall demonstrate their competency in developing test plans and reports. The test plan shall include all information required for the successful completion of the test, test failure mitigation strategies, test plan goals, where the test(s) were to take place, test plan schedule, etc. The test report gives the results of the test plan.

2.1.6 Risk Areas

2.1.6.1 Heat Shield Cracking – The Offeror shall show and demonstrate their understanding of reasons why the heat shield (if included in the design) is cracking/splitting in certain areas. The Offeror shall also develop and explain possible heat shield mitigation strategies, ranking them based on their own ranking system, using criteria such as cost, ease of maintenance, ease of engineering and logistics, repair costs, repair times, ease of implementation, etc.

2.1.6.2 Rubber Bumpers Cracking/Dissolving – The Offeror shall demonstrate their understanding of why the rubber bumpers are dissolving/cracking (if included in the design). The Offeror shall also develop and explain possible rubber bumper mitigation strategies, ranking them based on their own ranking system, using criteria such as cost, ease of maintenance, ease of engineering and logistics, repair costs, repair times, ease of implementation, etc.

2.1.6.3 Rubber Seating Area Cracking – The Offeror shall demonstrate their understanding of why the wheels are cracking where the outer lip of the wheel meets the tire rubber. The Offeror shall also develop and explain possible wheel cracking mitigation strategies, ranking them based on their own ranking system, using criteria such as cost, ease of maintenance, ease of engineering and logistics, repair costs, repair times, ease of implementation, etc.

2.1.6.4 Frozen Brakes - The Offeror shall demonstrate their understanding of why the lighter brakes are freezing. The Offeror shall also develop and explain possible frozen brake mitigation strategies, ranking them based on their own ranking system, using criteria such as cost, ease of maintenance, ease of engineering and logistics, repair costs, repair times, ease of implementation, etc.

2.1.6.5 Wheel Drive Key Spacer Grinding - The Offeror shall demonstrate their understanding of why the rotors are grinding material out of the drive keys. The Offeror shall also develop and explain possible chipped drive key mitigation strategies, ranking them based on their own ranking system, using criteria such as cost, ease of maintenance, ease of engineering and logistics, repair costs, repair times, ease of implementation, etc.

2.1.6.6 Other – If the Offeror’s design does not include any of the above issues, then any other maintenance, logistics, engineering, or programmatic issues shall be presented and addressed. The Offeror shall also develop and explain possible mitigation strategies, ranking them based on their own ranking system, using criteria such as cost, ease of maintenance, ease of engineering and logistics, repair costs, repair times, ease of implementation, etc.

2.1.7 Quality Assurance Plan (s) – The Offeror shall provide a quality assurance plan with the proposal. The quality assurance plan shall demonstrate Contractor compliance with ANSI/ASQC Q-9002/ISO-9002 standards, or equivalent and shall demonstrate their competency in developing Quality Assurance Plans.

2.1.8 Configuration Management – The Offeror shall demonstrate their competency in developing a configuration management plan.

2.1.9 Weight Management – The Offeror shall demonstrate their competency/expertise in the area of weight calculations and reporting.

2.1.10 Publications Handling – The Offeror shall describe their understanding of the complexities of the interrelationships with the publications to be changed, the areas they anticipate changing, and if applicable the areas they do not expect to change with regard to the braking system.

2.2 Book 2 – Program, Schedule and Capability ‑ In this book, the Offeror shall describe its approach, its assessment of program magnitude and, complexity, and the Offeror's ability to execute the program on cost and on schedule. The Offeror shall also describe the associated program risks.

2.2.1 Program Execution Approach – The Offeror shall discuss its program execution approach, fully describing its ability to execute the Brakes program in accordance with the requirements of this RFP with emphasis on systems engineering, requirements, programmic and logistics management. The approach shall include the following information:

A description of how your program execution approach is linked to the WBS.

a. An Integrated Management Plan (IMP) that will identify key events, milestones, reviews, integrated technical tasks (such as reliability and maintainability tasks), logistics efforts, trade studies envisioned and risk reduction activities. The IMP shall be included in the proposal as Annex A.

b. A description of your proposed management system to execute the SOW in accordance with the IMP and IMS. This should include your management techniques that will be applied to this program, and should contain: (1) A description of the Program Organization and how it will interface with the Government and other subcontractors/team members. (2) Identification of the subcontractors/team members that will be needed to augment your capability and a description of how they will be used and controlled in the execution of the program 3) A description of the planned approach for control and distribution of technical documentation.

2.2.2 Schedule – The Offeror shall provide an Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) for the Brakes program to meet the requirements of the solicitation. The IMP and IMS shall be included in the proposal as Annex B. The Offeror shall identify key milestones (including hardware/software milestones and functionality demonstrations), engineering tasks, logistics tasks, management decision points, and provide the critical path. The IMP and IMS shall clearly identify the logistics tasks necessary for designing, developing, procuring and fielding all logistics tasks necessary to fully support testing, fleet introduction and initial operating capability of the modified aircraft. The detailed IMP and IMS shall identify the activity, timeline, and duration of tasks to be performed, and shall be to the third level of indenture. In addition, the Offeror shall provide a top-level schedule (roll-up) showing the key milestones and tasks, highlighting the critical path and identified risks. The Offeror shall also provide an overall program schedule that reflects the key milestones for the design and production phases. Show explicit linkage between the WBS, SOW, IMP, and IMS. For the purposes of this proposal, assume a contract award date of October 2010, with key milestones such as Design Reviews 1 and 2. The final Design Review shall be completed no later than twelve (12) months after contract award, and the prototype installation and testing shall be completed within twelve (12) months of final design review. The IMP and IMS shall be created using Microsoft Compatible software and shall be delivered in paper and electronic format. Periods of performance shall be a 24 month base period and Option Periods for production. The IMS shall be submitted in accordance with IMS DID DI-MGMT-81650. The Offeror shall provide the results of the statistical Schedule Risk Analysis (SRA). The SRA data shall include a narrative describing the ground rules and assumptions used to perform the simulation and histograms for each of the activities identified above as minimum IMP events. The evaluation schedule shall be included in the proposal as Annex C. (Annex C may be incorporated into the successful offeror’s contract.)

2.2.3 Risk Assessment and Mitigation –Provide a Program Risk Assessment and Mitigation plan identifying areas of technical and programmatic risk associated with the proposed system configuration as defined in the program WBS. This plan shall place specific emphasis on the degree that risk assessment and mitigation has been integrated into guiding the design effort and its coordination with and reflection in the program and technical plans. Risk shall be addressed at each level of the WBS. Risk is defined as follows:

LOW

Has little or no potential to cause disruption of schedule, increase in Cost, or degradation of performance. Normal contractor effort will probably be able to overcome difficulties.

MEDIUM

Can potentially cause some disruption of schedule, increase in Cost, or degradation of performance. However, special contractor emphasis will probably be able to overcome difficulties.

HIGH

Likely to cause significant serious disruption of schedule, increase in Cost, or degradation of performance even with special contractor emphasis.

Provide an analysis of your program plans and schedule. Identify your risk areas in the order of your concern and describe your plan to mitigate the risk. Support your assessment and plans with historical information and technical analysis. The plan shall identify program risks and describe risk management techniques to be applied to those risks. Risks shall be reflected in the IMP and IMS. The plan shall clearly show how these risks will be mitigated.

2.2.4 Test and Evaluation (T&E) – Describe your approach to T&E. As a minimum, provide the following:

a. the test approach of the Brakes program to support model verification to include instrumentation response rates and risk mitigation prior to testing.

b. the flow down of the Brakes System Specification requirements to the individual tests to validate them.

c. the proposed management approach to the system test program to include the following:

1. The overall approach to the Integrated Test Team Structure and process including roles and responsibilities of the Offeror’s test team and related assumptions.

2. The approach to integrating processes and resources of third party vendors, Government Development and Operational test agencies, independent test agencies, and the Offerors own testing efforts into an integrated test program.

3. The approach to conducting the facilities coordination and installation of the contractor test equipment at the Government test sites.

4. Handling and storage of classified material and testing with co-operating terminals.

5. Generation and approval of test plans and procedures using NAVAIRINST 3960.4 series for guidance.

d. Plan for Software Testing - The Offeror shall provide their approach for validating error handling, exception handling, and automated testing capabilities.

2.2.5 Software Engineering Capability – If any software development is proposed, the Offerer shall demonstrate that all team members who are responsible for software development will have an SEI Software Capability Maturity Model (SW-CMM) Level 3 or DOD approved equivalent certification. If this certification was not obtained or can not be demonstrated, provide a Risk Mitigation Plan to account for the risk associated with a software capability of less than SEI SW-CMM Level 3 or equivalent.

2.2.6 Small Business Concern Subcontracting Strategy – Large businesses shall address their strategy for utilizing Small Businesses Concerns in the performance of this contract. In describing its strategy, the Offeror shall describe its approach of identifying small business concerns, the extent of participation of small businesses on this contract, the extent of commitment to use such small businesses, the complexity and variety of the work small businesses are to perform, past experience in meeting proposed goals and what processes have been implemented to correct inability to meet proposed goals. The Offeror shall also describe how its strategy is consistent with its Small Business Subcontracting Plan and any Small Disadvantaged Business targets that are proposed. All Offerors proposing Small Disadvantaged Business targets (in accordance with FAR 52.219-24) shall complete the Section L clause FAR 52.219-24 Small Disadvantaged Business Participation - Targets. Please provide the Small Business Subcontracting Plan as Annex E.

3.0

VOLUME 3 : PRICE PROPOSAL

The following guidelines and instructions are provided to assist the Offerors in preparing clear, concise, comprehensive and traceable proposals.

3.1 Price Proposal Guidelines:

(a) All price information shall be contained in Section B and the price proposal. No price or price supporting information shall be included in any technical volume including cover letters.

(b) This Volume shall contain the information requested below and shall include a copy of Section B with the Contract Line Item (CLIN) and Subcontract Line Item (SLIN) Unit Prices and, for evaluation purposes, the Total Prices filled in (Supplies and/or Services and Prices and/or Costs) using the quantities in the solicitation and the instructions below. Section B prices shall be provided separately in one digital data copy in MS Office 2000 or 2003 Excel format on CD-ROM media.

(c) The following is a list of the Section L Cost Attachments that the Offeror shall utilize to provide price information as required for this Volume. The Offeror may provide Contractor-format Cost Attachments in lieu of entering data on established Government forms on the condition that they include the same information as the established Government forms. The electronic version of these attachments shall be provided in Microsoft Excel 2000 or 2003 format. Clearly identify the CLIN on each form submitted.

Cost Attachment 1 (CA-1)

GFE/GFP/GFF/GFI List

(d) Provide a copy of any narrative in Microsoft Office 2003 Word format and any numerical data in a Microsoft Excel 2000 or 2003 format on CD-ROM. Files received in a format other than requested are unacceptable. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using output type “value only” cells. If links are utilized, supply those referenced files. Spreadsheets shall not be protected. Ensure that the electronically submitted filenames are directly traceable to the hard copy submittals.

(e) The information required in these price instructions applies to both the Offeror and to any principal subcontractors required to meet the requirements of this solicitation, as defined in paragraph one (1) of the General Proposal Instructions. Due to the proprietary nature of company rates, rate information may be presented separately for each Offeror and principal subcontractor. Each principal subcontractor that provides a separate volume shall follow the same format as described in these instructions.

3.2 Price Proposal Instructions:

The proposal provided by the Offeror shall be constructed in the following format and shall contain all data/information applicable to the entire contract to include all contract options.

Section 1 – Price Summaries

Section 2 – Ground Rules and Assumptions

Section 3 – Price Information

Section 4 – Contractor Rates

3.2.1 Section 1 – Price Summaries:

(a) Price information shall be submitted in Then Year dollars (TY$) based on the Government’s fiscal year (1 October through 30 September). The Offeror shall provide a summary level of the Price Proposal in Then Year dollars by Fiscal Year by CLIN. The Offeror shall provide a summary level of the Price Proposal in Constant Fiscal Year 2009 dollars (FY09 $) by Fiscal Year by CLIN using escalation/de-escalation factors supported by the rates and factors used in its price proposal.

3.2.2 Section 2 – Ground Rules and Assumptions:

(a) As this is a competitive acquisition with adequate price competition anticipated, the price documentation requested is not considered cost or pricing data and shall not be certified in accordance with FAR Subpart 15.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the Offeror shall provide cost or pricing data pursuant to FAR Part 15.

(b) The Offeror shall provide sufficient information to support its price as well as an explanation of all ground rules and assumptions that affect the price. Any apparent imbalances in the pricing, high or low proposed prices as compared to historical data, or any other anomalies should be fully explained. Topics to be addressed include, but are not limited to, investments and programmatic variables (e.g., inflation/escalation, location, make/buy decisions, prime/subcontractor relationships, and business base concerns, etc.)

(c) Government Furnished Equipment (including Data, Facilities). Identify any GFE and Government Furnished Property/Facilities/Information (GFP/GFF/GFI) required in performance of the contract. Cost Attachment 1 (CA-1): GFE/GFP/GFF/GFI List, shall include as applicable: the associated CLIN, item description, NSN and/or P/N, unit cost, quantity, total cost, contractor/supplier, location, availability, and any additional comments the Offeror believes to be pertinent to the Government’s evaluation. The Offeror’s proposal shall specifically identify requirements for any available GFE/GFP/GFF/GFI listed in the RFP Section H clause 5252.245-9500, Government Property for the performance of this contract. List on a separate schedule any Government owned facilities e.g., Software Integration Laboratories (SIL) and Distributed Simulation/Test Facilities, or Government-owned special tooling and test equipment that will be required for the performance of the contract. Estimated rental factors/costs for the authorized use of the assets must also be provided in accordance with FAR 52.245-9. The Offeror shall provide this data in a summary format as provided in CA-1.

3.2.3 Section 3 – Price Information:

(a) Reasonableness and Consistency between the Technical and Price Volumes. Demonstrate that the unit prices and the total evaluated price are reasonable and are commensurate with the work required by the solicitation and the technical approach identified in the technical volume of the proposal. Show traceability with the CLINS, statement of work, specification, and proposed effort. Refer to specific sections in the Technical Volume as needed to illustrate the consistency between the Price and Technical Volumes. Provide proposed manning levels (including labor hours by category and rates), material cost (including bill of material), subcontract cost, other direct costs (including travel and per diem), and proposed unit prices. The Offeror shall also state the number of hours used in determining an employee work year.

(b) The Government is not soliciting any investments. However, in order to properly assess a proposed cost/price that appears low or decreases program costs due to a corporate decision to absorb costs, (e.g., company investment or management challenge or a contribution of resources and/or equipment), the Offeror shall fully identify and explain any such investments. Additionally, the Offeror shall propose an H-clause that clearly identifies what equipment and/or material, and the associated data and data rights that are conveyed to the Government, and that also specifically states the fiscal adjustment(s) and identifies the Offeror’s liability in Volume 5, Exceptions, Deviations and Waivers, of its proposal. This shall be a contractually binding clause.

(c) Identify the proposed prices for CLIN or SLIN as specified in Section B of this solicitation. The Offeror shall sum up the proposed Total Prices by line item, provide a total overall price of the proposal using the quantities in Section B, and submit a complete Section B. For Fixed Priced and Time and Material (T&M) CLINs/SLINs, the Schedule B Total Price is equal to the proposed unit price multiplied by the Quantity for that CLIN.

3.2.4 Section 4 – Contractor Rates:

(a) The Offeror shall provide all rate information used in the proposal preparation. Due to the proprietary nature of company rates, this information may be presented separately for each Offeror and principal subcontractor. Traceability to Section B and the Price Summaries shall be included to ensure proper use of the rates. If providing calendar year rates, include traceability between calendar year rates and Government Fiscal Year (GFY) rates used in developing the proposal. If, for accounting purposes, the Offeror uses a yearly base different from the calendar year base, a description is required.

(b) Indirect rates: The Offeror shall identify the indirect rates for both the Offeror and the principal subcontractors used in the proposal. The Offeror shall include a projection of indirect rates that assumes the award of this contract in its business base. Any changes to a current Forward Pricing Rate Agreement (FPRA) due to the award, variation of the business base or other factors shall be fully described and justified. Discuss the application of these rates in the proposal. In addition, provide summary-level definitions for each major indirect rate account, explaining what costs are included in each overhead pool. The indirect accounts may include, but are not limited to, engineering overhead, manufacturing overhead, general and administrative (G&A), material handling overhead, and Cost of Money (COM). Describe the development of composite indirect rates that represent a combination of company labor categories, functional elements, or calendar year accounts.

(c) Direct rates: The Offeror shall provide the most current direct labor rates for both the Offeror and the principal subcontractors that are in effect at the time of proposal submission. This includes the current FPRA direct labor rates, the projected direct labor rates assuming award, the current company labor categories, and the mix of company labor categories proposed for this contract. Discuss the application of these rates in the proposal. The Offeror shall document the development of composite direct rates that represent a combination of company labor categories, functional elements, or calendar year accounts. In addition, the Offeror shall submit detailed definitions for each direct labor category and include the basis for any projected annual increases and any other factors. Direct labor categories may include, but are not limited to, engineering, maintenance/support, tooling, quality control, manufacturing, and integration.

(d) Removed

(e) Cost to Sell Equations: The Offeror shall submit the methodology used to transfer the cost data (i.e., direct labor hours or material direct dollars) into a sell cost to the Government (i.e., fully burdened with fee). This includes the sequence in which indirect rates, profit/fee, etc. were applied to direct costs to determine the sell cost. Include the base against which each of the overhead pools is applied in this description.

(e) Escalation: The Offeror shall provide all escalation-related assumptions used in the proposal. Information required in this section includes, but is not limited to, annual rates of escalation, source of the escalation indices, rationale for their applicability, and the method of their application.

4.0

VOLUME 4: PAST PERFORMANCE

Note: This volume shall not contain any reference to the cost or price aspects of the offer.

4.1 General

The Offeror shall submit a list of at least three, but no more than five, contracts whose relevant performance is within five years of this proposal submission and contain efforts similar to those efforts, e.g., tasks, contract type, location, contract dollar value, etc., required by this solicitation for the Offeror and the Principal Subcontractors. Identify contracts; list the contracts from the most relevant to the least relevant. In general, recent performance will be considered more relevant than older performance. Contracts listed should include those entered into by the Department of Defense, Federal Government, agencies of state and local government, and commercial customers. If proposing as a JV/SLE, provide three to five past performance references for the JV/SLE. If fewer than three past performance references are available for the JV/SLE, each Team Member of the JV/SLE should individually submit three to five references in addition to the JV/SLE references.

For each contract identified, provide contract data, relevancy, past performance and systemic improvement information as…