MACHSectionL(27Aug07).doc

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

YA-L001. PROPOSAL PREPARATION INSTRUCTIONS - INFORMATION TO OFFERORS (ITO):

1. Program Structure and Objectives

The Government intends to award a contract for the Modular Aircrew Common Helmet (MACH) System Development & Demonstration (SDD) with options for additional SDD efforts, Initial Operational Test & Evaluation (IOT&E), Low Rate Initial Production (LRIP), a Re-procurement Package, and Full Rate Production (FRP). The contract will have a five year ordering period if all options are exercised. The Source Selection Evaluation Team (SSET) will conduct a Best Value evaluation (See Section M "Evaluation Factors" for further detail.) The Government intends to evaluate proposals and award a contract without discussions with Offerors (except clarifications as described in FAR 15.306(a)). Therefore, the Offeror's initial proposal should contain the Offeror's best terms from a cost or price, technical and schedule standpoint. The Government reserves the right to conduct discussions if the Source Selection Authority (SSA) later determines them to be necessary. The Government intends to award one contract for Systems Development & Demonstration (SDD) with options for the Production phase of the MACH program, however, the Government reserves the right to make two or no awards based on the technology capability and/or funding availability for this program.

2. General Instructions

2.1 General Information

2.1.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address below:

Angelica R. Armenta, Contracting Officer

77 AESG/PSK

7980 Lindbergh Landing, Bldg 578

Brooks City-Base, TX 78235-5119

Telephone: (210) 536-4892

FAX: (210) 536-4563

2.1.2 Debriefings

All Offeror(s) may request debriefings by providing a written request to the CO. The CO will notify Offeror(s) of the source selection decision within 3 calendar days after award. Offeror(s) desiring debriefing must request in writing within 3 calendar days after the CO notification. To the maximum extent practicable, debriefings will be conducted within 5 days after the Offeror(s) request.

2.1.3 Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall notify the CO in writing with supporting rationale immediately, but no later than 10 days after release of the RFP. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

2.1.4 Teaming

a. All team members must have a signed Teaming Arrangement (TA) or Letter of Intent (LOI).

1. If any first-tier subcontractor is projected to perform more than 10% of all work on the contract, a signed TA or LOI shall be provided for that subcontractor.

2. First-tier subcontractors projected to perform less than 10% of all work on the contract may be included as team members at the Prime’s discretion. If included as a team member, a signed TA or LOI shall be provided for that subcontractor.

b. A subcontractor without a TA or LOI with the Offeror is NOT considered as part of the “team” and will not be evaluated as such.

c. Technical Qualification, Mission Capability, Past Performance Information, and Past Performance Questionnaires submitted for subcontractors without a TA or LOI will not be evaluated.

d. The Government will consider the Offeror and all subcontractors a “team” when evidence of a signed TA or LOI is provided in Volume I, Contracting Documentation.

e. A Joint Venture (JV) will be considered a sole business entity.

f. The proposal shall present a complete, coherent presentation of team abilities as applicable.

2.2 Organization/Distribution/Number of Copies/Page Limits

a. The Offeror(s) shall prepare the proposal as set forth in Table 1 below. In addition to the hardcopies, each proposal volume shall be submitted on CD-ROM, with one Master E-copy containing the entire proposal. In case of conflict between the CD-ROM and hard copy, the hard copy marked “original” takes precedence. CD ROM(s) must be submitted in a protective sleeve. They shall be compatible with the Windows XP Professional SP1 operating system and be made, as appropriate, in Microsoft Word 2000 (or latest version available), Microsoft Excel 2003 (data file should be .XLS file format), Microsoft Project 2000, Microsoft PowerPoint 2003, and Adobe Acrobat 6.0. Offeror(s) are responsible for ensuring electronic copies on CD ROM are virus free. The titles and contents of the volumes should be as defined in Table 1 of this document, all of which shall be within the required page limits and with the number of copies as specified in the table. The volumes identified in the table should be separately bound in three-ring, loose-leaf binders, as necessary. The content of each proposal volume is described in the Instruction to Offeror(s) (ITO) paragraph as noted in the table below. In the event that this table conflicts with the detailed instructions in the paragraphs that follow, the detailed instructions shall take precedence.

Table 1 - Proposal Organization

Paragraph

Number

- Executive Summary

10 per PPI Form

Unlimited

Unlimited

Unlimited

b. One hardcopy of each volume shall be clearly identified as “original”. The “original” and all other proposal volumes shall be delivered via UPS or Fed Ex to:

MACH Source Selection

ATTN: Ms. Angelica R. Armenta

77 AESG/PSK

7980 Lindbergh Landing Brooks City-Base, TX 78235-5119

2.3 Proposal Format

2.3.1 Guidance

This section of the ITO 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 ITO and must be submitted in accordance with these instructions. These instructions are intended to elicit brief and specific responses. However, simply stating that the Offeror understands and intends to comply with this effort or paraphrasing statements in the RFP is inadequate. The offer shall be compliant with the requirements as stated in the Statement of Objectives (SOO), Government Performance Specification (PS) PRF-TA-MACH-001-08, Contract Data Requirements List (CDRL), and Model Contract.

2.3.2 Sufficient Detail

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offeror(s) shall assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the Offeror's proposal.

2.3.3 Validity Statement

The proposal acceptance period is specified in Block 12 of Section A of the model contract/RFP. The Offeror shall make a clear statement that the proposal is valid until this date in the proposal documentation volume. Be sure to identify appropriate markings such as the legend at FAR 52.215-1(e), Restriction on Disclosure and Use of Data. In compliance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

2.3.4 Elaborate Presentations Not Desired

Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

2.3.5 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring loose-leaf binder that 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 as to volume number, title, copy number, solicitation identification and the Offeror's name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to identify appropriate markings such as the legend at FAR 52.215-1(e), Restriction on disclosure and use of data.

2.3.6 Page Format Restrictions and Limitations

2.3.6.1 Page Size

Pages shall be 8.5 x 11 inches, not including foldouts. Pages shall be typed with at least 1.5-line spacing. Except for the reproduced sections of the solicitation document, the font size shall be no less than 10 point. Margins on all four edges of each sheet will be at least one inch. Proprietary statements, security markings, and page numbers can fall within the defined margin area. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to Evaluation Notices (ENs).

2.3.6.2 Page Limitations

Page limitations shall be treated as maximums. Compliance with page count limits shall be verified via the hardcopy. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be returned to the Offeror as soon as practicable. Page limitations shall be placed on responses to ENs. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offeror(s). When both sides of a sheet display printed material, it shall be counted as 2 pages. See paragraph 2.3.8 below for foldouts.

2.3.6.3 Pages Counted

Each page shall be counted except the following: cover pages, table of contents, RFP Cross-reference Matrix, SF 294/295s provided in support of Past Performance Information, list of figures, tabs, dividers, glossaries and blank pages.

2.3.7 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.

2.3.8 Foldouts

Legible tables, charts, graphs, diagrams, schematics and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, design drawings, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume. Each printed side of a foldout will count as one page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. For tables, charts, graphs and figures, the font shall be no smaller than 8 point. Design drawings may be in Offeror's format, provided standard commercial policies and practices are followed. All information (except documentation numbers, classification markings, and page numbers) shall be contained within an image area of 9 x 15-1/2 inches.

2.3.9 Cost or Pricing Information

All cost or pricing information shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation Volumes. Cost trade‑off information, work‑hour estimates and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade‑off decisions. All dollar amounts provided in response to these instructions shall be rounded to the nearest whole dollar.

2.3.10 Minimum Cross-Referencing

Each volume shall be written to the greatest extent possible on a stand‑alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal.

2.3.11 Glossary of Abbreviations and Acronyms

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

3. Volume I – Contracting Documentation

3.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. Any GFP/GFE being requested shall be clearly identified as such.

3.1.1 Section A - Solicitation/Contract Form

The Offeror(s) shall complete blocks 12 through 16 and signature and date for blocks 17 and 18 and of the Standard Form 33. Signature by the Offeror on the SF 33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

3.1.2 Section B - Supplies or Services and Prices/Costs

The Offeror(s) shall provide completed pricing information in Section B of the model contract. The funding profile for the SDD phase is provided at Attachment L-13. This funding profile shows what is available for the contract and does not include any Government costs. The offeror may propose additional sub line items to correspond with their proposed approach as necessary.

3.1.3 Section H – Special Contract Requirements

The Offeror(s) shall identify any Government-Furnished Equipment (GFE) or Government-Furnished Property (GFP) being requested in Section H clause, H087, Government-Furnished Property.

3.1.4 Section J – Contract Attachments

The Offeror(s) shall provide a completed set of Exhibit A, B & C CDRLs with appropriate CSOW reference provided in Block 5 of each CDRL.

3.1.5 Section K - Representations, Certifications, and other Statements of Offeror(s)

The Offeror(s) shall provide a printout of completed representations and certifications from the Online Representations and Certifications Application (ORCA) website. In addition to this printout, the offeror shall submit the representations and certification requirements of the DFARS clauses found in Section K of this RFP. The ORCA website is found at http://orca.bpn.gov.

3.2 Executive Summary

The Offeror(s) shall provide an executive summary of the entire proposal, including significant risks, 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. A maximum of ten pages will be allowed for this summary.

3.3 Table of Contents

The Offeror(s) shall provide a master table of contents of the entire proposal.

3.4 RFP Cross-Reference Matrix (RCRM)

The Offeror(s) shall fill out the RCRM at Attachment L-1 of this Instruction To Offeror(s) (ITO) indicating the proposal reference information as it relates to the ITO, SOO (through the CWBS), IMP, proposal volume and paragraph, and CSOW references found therein. The purpose of the RCRM is to show critical interrelationships and dependencies among the documents. The matrix ensures that all requirements are addressed, requirements do not conflict and solicitation sections are internally consistent.

3.5 Exceptions to Terms and Conditions

The Offeror(s) shall meet all solicitation requirements, such as terms and conditions, representations and certifications, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offeror(s) must clearly identify any exception to the solicitation terms and conditions and provide accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 3.1.

Table 3.1 - Solicitation Exceptions

Solicitation

Document

Portion Rationale

SOO, SOW, SPEC

Model Contract, ITO, etc.

Applicable Page and Paragraph

Numbers

3.6 Other Information Required

3.6.1Authorized Offeror Personnel

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

3.6.2 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).

3.6.3 Company/Division Address, Identifying Codes and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; DUNS 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.

3.6.4 Teaming Arrangements and/or Letters of Intent

The Offeror(s) shall provide all Teaming Arrangements and/or Letters of Intent in accordance with Section L, Para 2.1.4 as necessary.

4. Volume II – Management

4.1 Management Documentation

The Offeror(s) shall present their proposed program plan in a fully integrated set of documents consisting of the Contractor Statement of Work (CSOW), Contractor Work Breakdown Structure (CWBS), Integrated Master Plan (IMP), and Integrated Master Schedule (IMS). This set of documents will present detailed insight into an approach that proactively manages cost/schedule/performance and risks in accordance with sound business practices. These documents must give clear visibility into program risks, cost, schedule, performance, testing, manufacturing/production planning and preparation, and logistics.

4.1.1 Contractor Statement of Work (CSOW)

The Offeror shall use the Government SOO and Government Performance Specification to develop an overall program CSOW that is structured to correlate with the CWBS, IMP, and IMS. The proposed CSOW, when accepted by the Government, will be placed on contract at time of award.

4.1.2 Contractor Work Breakdown Structure (CWBS) and Dictionary

The Offeror shall propose a CWBS and CWBS Dictionary using MIL-HDBK-881 as a guide. The CWBS will consist of enough levels (three or more) to identify work packages and provide a framework for program and technical planning. The CWBS should be consistent with the Offeror’s business processes, the CSOW, and the Government Performance Specification (PS). Ensure all integrated test-related work is captured in the CWBS. See Attachment L-2, and Figure 2.

4.1.3 Integrated Master Plan (IMP)

The Offeror shall submit an IMP in accordance with Attachment L-3. The IMP shall be concise, specific, and complete. The Offeror’s IMP shall document the significant accomplishments necessary to: 1) design, develop, test and deliver the product defined in the PS;and 2) achieve the objectives in the SOO. The IMP shall have direct correlation with the events contained in the IMS and the CWBS. The program milestones described in the IMP shall be event-oriented and represent the Offeror’s Integrated Product Process Development approach (IPPD - see Attachment L-2) that encompasses all deliverable products (hardware and other items) and all functional areas (engineering, test, manufacturing, logistics, training, supportability, human factors, safety, quality, configuration management, program management, subcontract and associate contractor relationships, etc.). The IMP shall also include a narrative to discuss the events, the required accomplishments for each event, the criteria for each accomplishment, and how the Offeror shall manage these tasks to achieve a successful program (see Attachment L-3). The IMP shall include the Offeror’s management structure and how it supports and implements IPPD (see Attachment L-2). It is the intent of the Government to attach an agreed upon IMP to the contract.

4.1.4 Integrated Master Schedule (IMS)

The Offeror shall submit an IMS in accordance with Attachment L-4 including programmatic networked relationships and critical path identification.

4.1.5 Life Cycle Cost Management

The offeror shall submit their plan for managing and minimizing life cycle costs. Refer to Attachment L-8, for guidance on life cycle activities.

4.2 Risk Management

The Offeror shall describe the process for implementing proactive risk management. The risk management description shall discuss methods for identifying, analyzing, prioritizing, and tracking risk drivers; risk-handling plans; and planning for adequate resources to handle risk. Include a discussion of any tools or methodologies used in the risk management process and for risk assessments.

4.3 Corporate Experience

The Offeror shall describe their experience, within the last five years, in the areas of systems integration, aircrew systems integration and production of flight helmet equipment. For “Systems Integration”, experience shall be for the prime contractor only. The others areas may include experience of all team members as either a prime or subcontractor.

a. Systems Integration (Prime Contractor experience only). Systems integration experience is defined as total system responsibility, to include working with subcontractor(s) in both SDD and Production, in integrating products/processes/subsystems/components into a total system. The systems integrator does not necessarily have to have a separate product/process/subsystem component of the system to be the systems integrator.

b. Aircrew Systems Integration. Describe your experience with integration of DoD aircrew systems equipment. This should address experience with the following:

(1) Integration of flight helmets with current DoD personal Life Support & Survival Equipment.

(2) Integration of flight helmets with helmet-mounted devices (e.g., NVGs, PNVGs, JHMCS, etc…).

(3) Integration of flight helmets with aircrew NBC protective equipment.

(4) Application of human systems engineering, especially that related to anthropometry associated with flight helmet and mask systems design.

(5) Integration of a pressure breathing oxygen mask into an flight helmet system.

c. Production experience relating to the manufacture of flight helmets.

5. Volume III – Technical

5.1 Design

5.1.1 Offeror(s) shall specifically explain how their design will meet the KPP thresholds, and as many of the KSA and OSA thresholds as possible. Offeror(s) will describe how their proposal incorporates trade-offs of non-KPP threshold requirements in an effort to maximize performance, minimize risk, and/or reduce life cycle costs, while meeting overall schedule length. If the Offeror is proposing trade-offs to eliminate or reduce KSA and OSA threshold requirements, those requirements that were eliminated or reduced must be identified by completing the “MACH Prioritized Requirements Matrix” (Attachment L-7). Offeror(s) shall also provide the rationale (e.g., CAIV analysis, trade off analysis, risk assessment) which substantiates the decision(s) to trade the requirement(s). Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

5.1.2 Offeror(s) shall provide substantiation of their proposed design’s maturity/pedigree by submitting executive summaries of any relevant test data, test reports, technical specifications, analyses, or other supporting documentation that can substantiate how their proposed design will meet the KPP and KSA threshold requirements. Offeror shall clearly state what design efforts remain to be accomplished.

5.1.3 Offeror(s) who choose to propose a multiple helmet solution (e.g., different fixed wing and rotary wing systems) shall delineate the section three and four performance specification requirements/tests which they believe are appropriate to their individual designs.

5.2 Risk Mitigation

Offeror(s) shall identify the technical risks inherent in their specific design approach. Offeror(s) shall provide a risk rating of high, moderate, or low; provide the rationale for each rating; and discuss the plan to mitigate each risk.

Offeror(s) shall also propose risk mitigation strategies for each of the following government-identified technical risks:

a. The choice of design when implementing helmet mounted equipment as well as addressing the increased protection requirements of the MACH system may compromise aircrew safety if mass properties (center of gravity, weight) are not addressed appropriately in the design.

b. The choice of design when developing the appropriate levels of penetration protection may compromise aircrew safety in emergency situations if not addressed appropriately in the design.

c. The choice of design when developing the appropriate levels of impact protection may compromise aircrew safety in emergency situations if not addressed appropriately in the design.

d. Aircrew performance will be degraded if the Offeror does not place emphasis on proper noise protectin and communcication systems early in the design

e. If helmet retention (up to 600 Knots Equivalent Air Speed (KEAS) ejection) is not considered early in the design, aircrew safety may be compromised.

f. Maintainability of the helmet system may be compromised if a comprehensive logistical support strategy (to include training, maintenance, tooling, and support equipment) is not considered prior to fielding of the MACH system.

g. Failure of the MACH system to effectively integrate with existing aircrew equipment may negatively impact aircrew mission effectiveness and safety.

h. Failure to comply with the Berry Ammendment will result in a product which may be unacceptable to the Government.

5.3 Test

Offeror(s) shall document and provide their planned DT&E program in the form of a Contractor Test Plan. The DT&E program shall adequately demonstrate the MACH design’s ability to meet the KPP, KSA, and OSA threshold requirements identified in the Section L Prioritized Requirements Matrix. The test plan shall include a general description of required test resources, general tasks to be performed, and test activities (e.g., CBRN testing, engagement modeling and simulation, aircraft integration/compatibility, cockpit display compatibility, optical integration, life support equipment compatibility demonstration, environmental testing, etc…). Particular test methodologies should be selected on the basis of risk reduction, decreasing DT&E test costs and/or increasing DT&E effectiveness and timeliness. Describe the process and estimated timeline required for analyzing test failures and implementing corrective actions. The DT&E schedule in the IMS shall include the estimated time needed for thorough failure analysis and corrective action activities.

6. Volume IV – Systems Engineering (SE)

6.1 Integration Plan

Offeror shall describe how they will conduct their SE effort for the life of the contract. The discussion shall focus on how the Offeror will organize their team to address integration (e.g., component, equipment, aircraft, etc…), who will have responsibility for the effort, what the Offeror needs in order to accomplish the integration effort (e.g., technical data, visits to see equipment), and the Offeror’s sequenced plan for ensuring that integration is successfully accomplished (which shall be documented in the IMS). The discussion shall address how the information gained from integration efforts/visits will be fed into the design process.

6.2 Operational Safety, Suitability and Effectiveness (OSS&E) Provide a general description of your approach for ensuring the MACH system is operationally safe, suitable and effective for fielding. Include verification plans/processes to be used during SDD and Production.

6.3 Logistics Planning

Provide a general description of how you plan to implement the Systems Engineering process for training, deployment, operations, support and disposal of the system. Also, discuss the anticipated maintenance requirements at the organizational level. Present any risks/issues (cost, schedule, performance) with meeting the supportability and maintenance requirements. Refer to Attachment L-8, for more information and guidance on logistics topics.

7. Volume V – Production Capability

The Offeror shall describe their manufacturing/production capability to include facilities, manpower, equipment, tooling, methods/processes, production rate, yield capability, quality assurance processes, and hazardous material management procedures to meet the MACH system production schedule and quantities, as identified in Sections F and B of the model contract, respectively. If current capability is lacking, describe the events/actions to achieve the necessary manufacturing/production capability (as described above) within the program schedule and any risks that could affect the delivery schedule. Present any data/details that demonstrate the manufacturing/production capability currently exists or is obtainable within the program schedule. Describe the process for material procurement from suppliers and the lead-time required. Offeror shall clearly state who will perform the major manufacturing, assembly, and inspection tasks and where they will be performed. Offerors shall state what they see as critical production processes/tasks and their plans for accomplishing them. Include supporting information for any proposed accelerated production/delivery schedule. Projected total MACH system Production Quantities by Service are provided in Attachment L-12.

8. Volume VI – Small Business Participation

8.1 Applicability for Large Businesses

This subfactor is applicable if a Subcontracting Plan is required by FAR 19.7.

8.2 Corporate Commitment

Describe the Offeror’s corporate commitment in providing subcontracting opportunities for small business, small disadvantaged business, women-owned small business, HUBZone small business, veteran-owned small business concerns, and service disabled veteran-owned small businesses. Describe the strength and specificity of each corporate commitment (i.e., what type of commitment, how binding is the commitment, how specific is the commitment to this proposed effort, and what types of tasks are included in these subcontracting opportunities).

8.2.1 Provide a one year history demonstrating corporate commitment to meeting subcontracting goals/targets by providing SF 294s, Subcontracting Report for Individual Contracts, on those contracts/projects that are being submitted for evaluation under the Past Performance factor. If goals were not met on the SF 294, provide an explanation as to why the goals were not met. This information will be used to determine proposal risk associated with the Offeror’s corporate commitment in achieving small business goals.

8.3 Achievement of MACH Small Business Goals

Describe how you will meet the specific subcontracting goals identified in the table below. These must be expressed in dollars and in percentages of your total proposed subcontracting dollars for each category. These goals may be met by any combination of subcontracts, other business teaming arrangements or vendor purchases, and should make use of small businesses to the maximum extent practicable. Work performed in foreign countries is not allocable to these goals.

8.4 Small Disadvantaged Business (SDB) Participation Program

For the SDB Participation Program (Ref FAR 19.12), provide your targets expressed as dollars and percentages of anticipated total contract value, in each of the applicable, authorized NAICS Industry Sub-sectors. Note: This target should not be confused with the small disadvantaged business goal identified in the table in paragraph 8.3. This SDB Participation Program target is a separate target that you propose for this program, pursuant to FAR 19.12.

8.5 Small Business Subcontracting Plan

8.5.1 Provide a Small Business Subcontracting Plan in accordance with FAR 19.7. The plan will not be evaluated as part of Section M, Evaluation Criteria; it is a basic contract requirement and must be approved prior to contract award.

8.5.2 If a subcontracting plan is NOT required by FAR 19.7, the small business may submit the following information which may be considered advantageous to the Government.

(a) Describe the Prime’s corporate commitment in providing subcontracting opportunities for each small business subcategory. Describe the strength and specificity of each corporate commitment (i.e. what type of commitment, how binding is the commitment, how specific is the commitment to this proposed effort, and what types of tasks are included in these subcontracting opportunities)

(b) Describe, in dollars and percentages of total subcontracted dollars, how the Offeror will meet the subcontracting goals listed in paragraph 8.3.

(c) Provide your targets for SDB Participation Program expressed in dollars and in percentages of anticipated total contract value for the authorized NAICS Industry Subsectors. For proposal purposes, provide your assumption of anticipated total contract value should you be awarded a contract. Note: This target should not be confused with the Small Disadvantaged Business goal addressed in paragraph 8.3. This SDB Participation Program target is a separate target that you propose for this program, pursuant to FAR 19.12.

9. Volume VII – Relevant Present and Past Performance

9.1 Volume Organization

(a) Standard Proposal Information

(1) Table of Contents

(2) List of Tables and Figures

(3) Glossary of Abbreviations and Acronyms

(b) Narrative

(1) Past Performance Summary

(2) Relevance of Present/Past Performance to Mission Capability Subfactors

(3) Organizational Structure Change History

(c) Present/Past Performance Information (PPI) (Attachment L-5)

(d) Present/Past Performance Questionnaires (PPQ) (Attachment L-6)

(e) Consent Letters (Attachment L-9)

(f) Client Authorization Letters (Attachment L-10)

9.2 Narrative

This following information is required on all Teaming Partners and is limited to twenty (20) pages.

9.2.1 Past Performance Summary

(a) Describe the role of each Teaming Partner that will potentially perform on the MACH contract. The Government will only consider work performed by those teaming partners proposed to perform at least 10% of the MACH effort based on the total proposed price, or those that perform aspects of the effort that is critical to the overall successful performance. Separately list by company name, any teaming partners included on the team based upon the criticality of their function(s) that will perform less than 10% of the proposed effort and identify the proposed critical function(s).

(b) This information is to assist the evaluators in determining relevancy of projects submitted for past performance evaluation by confirming the role of the team member compared to the scope of the projects submitted for evaluation.

9.2.2 Relevance of Present/Past Performance to Mission Capability Subfactors

The narrative portion will discuss how the projects submitted for evaluation demonstrate the Offeror’s ability to meet the Mission Capability subfactors.

Subfactor 1.1 - Management

Subfactor 1.2 - Technical

Subfactor 1.3 - Systems Engineering

Subfactor 1.4 - Production Capability

Subfactor 1.5 - Small Business Participation

9.2.3 Organizational Structure Change History

(a) Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant present or past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition.

(b) To facilitate this relevancy determination, include in this proposal volume a “roadmap” describing all such changes in the organization of your company.

(c) As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment.

(d) Since the government intends to consider present and past performance information provided by other sources as well as that provided by the Offeror(s), your “roadmap” should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

9.3 Present/Past Performance Information (PPI) Forms (Attachment L-5)

(a) A maximum of 6 PPI forms per prime contractor and a maximum of 3 PPI forms per teaming partner shall be submitted for evaluation. A maximum of 10 PPI forms per team shall be submitted. Each PPI form can be no greater than 10 pages.

(b) The Government will not consider performance on an effort that concluded more than three years prior to the due date of this solicitation.

(c) Offerors are cautioned the Government will use data provided by the Teaming Partners as well as data obtained from other sources in the evaluation of Present/Past Performance.

(d) A Present/Past Performance Information Summary Sheet identifying (1) all Teaming Partners proposed for the MACH contract; and (2) which of the past performance contracts submitted they teamed on; shall also be submitted. A total of one (1) summary sheet shall be submitted per team. A sample of this summary sheet can be found in Attachment L-5.

(e) The contractor shall determine the mix of projects to best represent depth and breadth of past performance through relevant projects.

(f) IDIQ contracts will typically demonstrate more depth and breadth than a single task order or single project contract.

(g) Identify the scope summary of the contract submitted as it relates to the MACH scope.

(h) Describe the rationale supporting your assertion of relevance of the submitted contract to the MACH acquisition. Clearly link the past performance to the proposed CSOW.

(i) Clearly demonstrate management actions employed in overcoming problems and the effects of those actions, in terms of improvements achieved or problems rectified. This may include a discussion of efforts accomplished by the Offeror, or applicable Teaming Partner, to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. For example, submit quality performance indicators or other management indicators that clearly support that an Offeror, or applicable Teaming Partner, has overcome past problems.

(j) Provide references for each project. For each PPI, identify those persons/customers most knowledgeable about the contract. For Government contracts, provide current information for the Government Program Manager, Project/Task Manager, Contracting Officer, and Administrative Contracting Office. For commercial contracts, provide points of contact fulfilling these same roles. Any additional customers that have in-depth knowledge of the contract may be added.

(k) Offerors are requested to submit the PPI Forms 15 days prior to the date set for receipt of proposals. These can be mailed or faxed to the point of contact identified in para 2.1.1.

(l) Failure to submit early proposal information will not result in Offeror disqualification.

9.4 Past Performance Questionnaires (PPQs) (Attachement L-6)

(a) The number of PPQs submitted shall be limited to five respondents per past performance effort submitted on Attachment L-5.

(b) The responsibility to send out and track the completion of the PPQs rests solely with the Offeror.

(c) Questionnaire respondents shall fax completed PPQs directly to the point of contact identified in para 2.1.1. Information contained in a completed PPQ shall be considered sensitive and shall not be released to the Offeror.

(d) Even though the assessment of Past Performance is separate and distinct from Determination of Responsibility required by FAR 9, past performance information contained herein may be used to support the Determination of Responsibility for the successful awardee(s).

(e) Information provided on the Past Performance Questionnaires assist the evaluation team in determining the confidence ratings for past performance.

9.5 Consent Letters (Attachment L-9)

The Offeror shall provide a consent letter for each Teaming Partner using the format provided at Attachment L-9, Example Format for Consent Letter. This letter allows the release of Teaming Partner adverse Present/Past performance information to the Offeror so the Offeror can respond to such information.

(a) The Offeror shall provide original consent letters for each Teaming Partner and/or joint venture partner.

(b) Past performance information concerning subcontractors and Teaming Partners cannot be disclosed to a private party without the subcontractor's or Teaming Partner's consent.

(c) Because a prime contractor is a private party, the Government will need that consent before disclosing Teaming Partner past and present performance information to the prime during exchanges.

(d) Consent letters are evaluated only to the extent that they are complete and present for each Teaming Partner, and/or joint venture partner that presented past performance information in the proposal.

9.6 Client Authorization Letters (Attachment L-10)

If a Teaming Partner identifies Present/Past performance efforts performed for a commercial customer, then each Teaming Partner shall submit a client authorization letter, authorizing release to the Government of requested information on their respective performance using the format provided at Attachment L-10, Example Format for Authorization Letter.

(a) The Offeror shall provide original client authorization letters for the Offeror and each Teaming Partner and/or joint venture partner.

(b) Each Offeror, Teaming Partner, and/or joint venture partner shall execute a Client Authorization Letter for commercial customers.

(c) Client authorization letters are evaluated only to the extent that they are complete and present for each Teaming Partner, and/or joint venture partner that presented past performance information in the proposal.

10. Volume VI – Cost/Price

10.1 GENERAL INSTRUCTIONS

10.1.1 Price

Since this is a competitive Fixed Price Incentive acquisition, limited pricing data is required. These instructions are to assist you in submitting information other than cost or pricing data that is required to support your proposed cost. Compliance with these instructions is mandatory and failure to comply may render your proposal ineligible for award. Note that unreasonably low or high proposed costs, 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 unreasonable proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed costs rests with the Offeror.

10.1.2 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 information relating to the proposed price including all required supporting documentation must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

10.2 Volume Organization

The cost/price volume shall consist of the following sections:

SECTION 1 ‑ Cost or Pricing information and supporting data.

SECTION 2 ‑ Other information such as GFP, base support, long lead costs, termination costs, development/production schedule, inflation rate summary and explanation, and special tooling/test equipment. List each exception to assumptions provided in the solicitation and each qualification of the cost/price volume, if any, and provide complete rationale.

10.3 Accounting System

Indicate whether prime Offeror has a Government approved accounting system and if so, provide evidence of such approval. Also, identify any deviations from your standard accounting procedures in preparing this proposal.

10.4 Required Information

10.4.1 Price Template

Offerors are required to complete and submit the price template located at Attachment L-11.

10.4.2 Cost Summary by Cost Elements (SDD only)

Since the SDD portion will be priced as a Fixed-Price Incentive (Firm Target) contract arrangement, the following information is needed, in addition to the Price Template, to properly establish a reasonable firm target at time of contract award.

Provide a cost summary for the SSD portion by major cost elements by CWBS and by Contractor Fiscal Year, using the format, essentially as shown below. The contractors’ own format is encouraged as long as they include the required information. The application methods for indirect rates should be demonstrated.

COST ELEMENTS

Prime Contractor

Labor Cost

Labor Hours & Labor Rates

Material Costs

Indirect Costs

Overhead(s)

Other Indirect Costs

G&A

Other Direct Costs

Total Estimated Costs

Subcontractor

Labor Cost

Labor Hours & Labor Rates

Material Costs

Indirect Costs

Overhead(s)

Other Indirect Costs

G&A

Other Direct Costs

Total Estimated Costs

Interdivisional Costs

Facility Capital Cost of Money

Profit

Total

10.4.3 Support Documentation

Offers should be sufficiently detailed to demonstrate their reasonableness. Offeror should fully explain the methodology used to estimate each major cost element. The burden of proof for credibility of proposed costs rests with the offeror.

ATTACHMENT L-1: RFP CROSS REFERENCE MATRIX

For Prospective Offeror(s): See paragraph 3.4 regarding instructions for completion of the solicitation RCRM. If this matrix conflicts with any other requirement, direction or provision of this solicitation, the other reference shall take precedence over this matrix. Additionally, to the extent this matrix discloses details as to the extent or manner by which the Government intends to evaluate Offeror’s proposals for award, Section M references in the matrix are for information purposes only and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of the Section M of the solicitation. Any reference to Factor 1 (Mission Capability) in the RCRM implicitly relates to an evaluation of Factor 2 (Proposal Risk).

RFP CROSS REFERENCE MATRIX

Factor/Sub-Factor(s)

Vol/Para No.

CSOW

Management

4.1.1

CSOW

4.1.2 CWBS and Dictionary

4.1.3

IMP

4.2 Risk Management

4.3 Corporate Experience

5.1 Design

5.2 Risk Mitigation

5.3 Test

Systems Engineering

Production Capability

Small Business Participation

Past Performance

Cost/Price

ATTACHMENT L-2: INTEGRATED PRODUCT PROCESS DEVELOPMENT (IPPD)

Program Structure and Objectives The Government is implementing a streamlined approach based on Integrated Product Process Development (IPPD) for this effort. This approach provides flexibility to the Offeror in planning and executing an effective effort while giving the Government greater visibility into this effort. Two of the major features of this approach are reviewed in this introduction.

The first major feature addresses planning the contract work effort and preparing the contract documentation, see Figure 1. The Government’s solicitation provides the Offeror with the elements shown in the left column of the figure; i.e., Model Contract (Sections A - K), Section L, Section M, Statement of Objectives (SOO), Government Performance Specification (PS), Contract Data Requirements List (CDRL), and Contract Line Item Numbers (CLINs). Based on these solicitation requirements, the Offeror shall submit a proposal containing the items listed in the center column of the figure; i.e., a completed Model Contract, Contract WBS (CWBS), Contract Statement of Work (CSOW), Applicable Documents, an Integrated Master Plan (IMP) and Schedule (IMS), enhanced CDRL, and CLINs, in accordance with the detailed proposal preparation instructions found in this solicitation. The definitive contract contains the elements shown in the far right-hand column of the figure.

The IMP expands on the CWBS, its dictionary, and the CSOW tasks, and establishes, by key events and selective narratives, the significant accomplishments and corresponding accomplishment criteria for both the products and processes necessary to accomplish the effort. Selected narratives will be included to explain where in the process the criteria apply. The IMP will be agreed-to by the Government and placed on contract. The IMS supports the IMP and shows the schedule of tasks necessary to achieve each significant accomplishment.