CHOBS_Section_L_Final.pdf

6 November 2017

SECTION L

INSTRUCTIONS TO OFFERORS (ITO)

Cockpit-Selectable Height-of-Burst Sensor

(C-HOBS)

SOURCE SELECTION

1. PROPOSAL PREPARATION INSTRUCTIONS

This is a best value source selection conducted in accordance with Federal Acquisition Regulation (FAR) 15.3, Source Selection, as supplemented by the Defense Federal Acquisition Regulation Supplement (DFARS), DoD Source Selection Procedures dated 31 March 2016 and the Air Force Federal Acquisition Regulation Supplement (AFFARS). These regulations are available electronically at the Air Force (AF) FARSite, http://farsite.hill.af.mil. A hybrid approach will be utilized by evaluating some factors using trade-offs, while other factors (as identified) will be evaluated on an acceptable/unacceptable basis.

To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including all stated terms, conditions, representations, certifications, and technical requirements, in addition to those identified as evaluation factors or sub-factors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The response shall consist of four (4) separate volumes; Volume I - Technical, Volume II – Past Performance, Volume III – Cost/Price, Volume IV - Contract Documentation.

2. PROGRAM STRUCTURE AND OBJECTIVES

The Government intends to award one contract for the C-HOBS program. However, the Government reserves the right to award more, or no contract(s) at all if the Source Selection Authority (SSA) determines it is in the Government's best interest. The SSA will consider the Government's expected volume of work, available funding, adequate competition, and the availability of best value proposals.

Budget/Funding Information – Funding will be obligated on each delivery order awarded under the basic contract.

3. GENERAL INSTRUCTIONS

This section provides general guidance for preparing proposals as well as specific instructions on format and content. The offeror's proposal shall include all data and information requested and shall be submitted in accordance with (IAW) these instructions. Any offeror who submits an incomplete package may be eliminated from the competitive range or not be awarded a contract. The offer shall be compliant with the requirements as stated in the System Requirement Document (SRD) and Statement of Objectives (SOO), Attachment 2 “Rights in Data” Contract Data Requirements Lists (CDRLs), and Model Contract. Non-conformance with these instructions may result in an unfavorable proposal evaluation.

Non-Government Advisors – Non-Government advisors will assist in providing input regarding evaluation of Offeror’s proposals. All Non-Government advisors have signed a non-disclosure agreement for this source selection. Non-Government advisors will not determine ratings or rankings of Offeror’s proposals. Non-Government advisors will not participate in the review and evaluation of past performance information.

Submission of an Offeror’s proposal signifies the Offeror’s consent and acceptance of providing Non-Government Advisors access to the Offeror’s proposal, excluding past performance information.

Include 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 shall not simply copy and paste, rephrase or restate the SRD and SOO, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their experience and will base its evaluation on the information presented in the offeror’s proposal.

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

The proposal acceptance period is specified in Block 11 of Standard Form 1447 within the model contract/solicitation. Offerors providing less than the specified calendar days for Government acceptance after the date offers are due may be considered non-responsive and may be eliminated.

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

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:

AFLCMC/EBHKA

Attn: Kyle Andersen 6072 Fir Ave Building 1233 Hill AFB, UT 84056-5820 Kyle.andersen@us.af.mil

Pre Award Debriefings - The CO will promptly notify offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing IAW FAR 15.505.

Post Award Debriefings - The CO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

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

Electronic Reference Documents - All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

Oral Presentation - Oral presentations will not be allowed.

Amendments to Solicitation - If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this request by the date and time specified in the amendment(s) by signing and returning the front page of each amendment.

Submission, Modification, Revision, and Withdrawal of Proposals - Proposals and modifications to proposals shall be submitted in both paper and electronic media (both must be submitted on time) to the address located in paragraph 3.7 of this document, showing the time and date specified for receipt, the solicitation number, and the name and address of the offeror. Late proposals will only be considered IAW FAR 15.208.

3.14.1. Acceptable evidence to establish the time of receipt at the Government installation includes the time/date stamp of that installation on the proposal http://www.fedbizopps.gov/ wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.

3.14.2. Proposals may be withdrawn by written notice received at any time before award. Proposals may also be withdrawn in person by an offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award.

Organization/Number of Copies/Page Limits

The title page of each volume must show:

3.15.1. Solicitation Number

3.15.2. Company name, address, Commercial and Government Entity (CAGE) Code and Data Universal Numbering System (DUNS) Number

3.15.3. Primary point of contact name, telephone number and email address

3.15.4. Volume number and name (i.e. Volume I, Technical) and copy number (i.e.

Original, Copy 1, Copy 2)

3.15.5. The offeror shall prepare the proposal as set forth in the Proposal Organization Table below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies specified. The volumes identified in the Table shall be separately bound in three-ring, loose-leaf binders. The contents of each proposal volume are described in the Section L paragraph as noted in the Table below:

Table 1 - Proposal Organization

VOLUME SECTION L

PARAGRAPH

TITLE COPIES PAGE LIMIT

I 4.0

Technical

Original plus 5 Hardcopies and

2 CDs

80 pages (IMS, IMP, SEMP &

QSP will not count against the 80-page limit)

II

5.0 Past

Performance

Original plus 1 Hardcopy and 2

CDs 12 pages

III 6.0 Cost/Price Original plus 2 Hardcopies, and

2 CDs

Unlimited With the exception of a 4 page pricing assumption limit

IV

7.0 Contract

Documentation

Original plus 1 Hardcopy and 2

CDs Unlimited

Page Limitations - Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs) if applicable. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, glossary of abbreviations and acronyms, cross reference matrix, and those noted in the Proposal Organization Table as “Unlimited.”

Pricing Information - All pricing information shall be addressed ONLY in the Price Volume.

Cross Referencing - Each volume of the proposal shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. In certain cases, information may need to be duplicated so each volume can be evaluated on a stand-alone basis i.e., pricing rights to data in Technical Volume I as required by attachment 2 “Rights in Data” and populating the TEP worksheet that will be found in Volume 3. Cross-referencing within a volume is permitted. Note: TEP is for data inputs only, do not change the format in any way i.e., adding new items, revising columns, rows etc.

The offeror shall fill out the proposal section of the cross reference matrix in the format as provided in Appendix 2 of Section L, indicating the proposal reference information as it relates to the Section L, and Section M - Evaluation Factors for Award. The cross reference matrix shall be included in the Technical Volume (Volume I). The cross reference matrix addresses each requirement within the SRD, SOO and Attachment 2 “Rights in Data” and Section L and Section M Factors/sub-factors. The offeror shall fill in the proposal section independently labeled with the appropriate paragraph number or page number from its proposal that addresses the requirement or factor/sub-factor.

Indexing

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

3.20.2. Include an indexed list of tables and figures. Tables and figures do not count against the page limitations for their respective volumes.

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

Page Size and Format - A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches, not including foldouts, and printed on both sides. Sheets shall be double-sided which will count as two pages. Except for the reproduced sections of the solicitation document, the text shall be Times New Roman and font size shall be no less than 12 points and lines shall be single spaced. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top, bottom, and side. Pages shall be numbered sequentially by volume. These limitations shall apply to both electronic and hard copy proposals. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, be printed only on one side, and count as a single page unless the foldout contains tables and/or figures which do not count against the page limitations for their respective volumes. 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 text shall be no smaller than 10 point. These limitations shall apply to both electronic and hard copy proposals.

Binding and Labeling – Each volume of the proposal should be provided separately in black or white three-ring loose-leaf binders large enough to permit the volume to lie flat when open. Staples shall not be used. The outside of each binder shall include a cover sheet, clearly marked as to volume number and title, copy number, solicitation identification and the offeror's name. The same identifying data should be placed on the spine of each binder. Be sure to apply all appropriate markings including those prescribed IAW FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

Electronic Offers – The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD the volume number and title. Use separate files for each volume to permit rapid location of all portions, including sub-factor required plans, exhibits, annexes, and attachments, if any. The offeror shall submit volumes I-IV in electronic format, using CD-Rs. Each volume shall be on a separate CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted as searchable PDF documents. Excel Spreadsheet shall not be locked and all calculations shall be viewable.

Distribution – The "original" proposal shall be identified. Proposals shall be addressed to the CO and mailed or hand-delivered to:

AFLCMC/EBHKA

Attn: Kyle Andersen 6072 Fir Ave Building 1233 Hill AFB, UT 84056-5820 Office (801) 777-9188 Kyle.andersen@us.af.mil

4. VOLUME I – TECHNICAL

General – In order to provide the Government sufficient information to make a data driven decision, the Technical Volume shall be clear, specific, complete and include adequate detail for effective evaluation. Legibility, clarity and coherence are very important. Responses will be evaluated against the Technical sub-factors defined in Section M, Evaluation Factors for Award. Offerors should review Section M criteria to ensure at least the minimum requirements are met. Provide as specifically as possible the actual methodology the offeror would use for accomplishing/satisfying each sub-factor. There will be no reference to price in this volume, other than what will be provided in Attachment 2 “Rights in Data.” Offerors shall assume that the Government has no prior knowledge of their experience and certifications, and will base its evaluation on the information presented in the offeror’s proposal. All the requirements specified in the solicitation are mandatory. By the offeror’s proposal submission, the offeror is representing that the company/firm or its subcontractor(s) will perform ALL the requirements to meet at least the threshold requirements in the SOO and SRD and the minimum requirements for Rights in Data specified in the solicitation; it is not necessary or desirable to tell us so in the proposal.

4.1.1.Adequate Responses – It is imperative that the offeror fully describe and provide detail as to how the offeror shall meet the sub-factor requirements.

Do not merely copy and paste, rephrase or restate the objectives or reformulate the requirements specified in the solicitation. Evidence (which clearly demonstrates and supports the offeror’s claims) is essential. The absence of such evidence may result in a technically unacceptable proposal.

Volume Organization - The Technical Volume shall be organized according to the following general outline:

1. Table of Contents

2. List of Table and Drawings

3. Technical Capability

a. Technical Requirements

b. Manufacturing and Quality

c. Management Approach

d. Small Business Approach

4. Glossary

Technical Capability

4.3.1. Sub-factor One – Technical Requirements

(a) HOB Performance

(i) HOB Tolerance The offeror’s proposal shall document the approach to the HOB Tolerance requirements defined in paragraph 3.2.1.8.2 and sub paragraphs of the SRD and shall include details and supporting documentation to clearly demonstrate compliance to the requirement.

(ii) Terrain Discrimination The offeror’s proposal shall document the approach to the Terrain Discrimination requirements defined in paragraph 3.2.1.8.4 of the SRD and shall include details and supporting documentation to clearly demonstrate compliance to the requirement.

(iii) HOB Selection The offeror’s proposal shall document the approach to the HOB Selection requirements defined in paragraphs 3.2.1.8.1 and sub paragraphs of the SRD and shall include details and supporting documentation to clearly demonstrate compliance to the requirement.

(b) Interfaces The offeror’s proposal shall document the approach to the following interface requirements: Common Munition BIT Reprogramming Equipment (CMBRE), Joint Direct Attack Munition (JDAM), DSU-33 Form Factor/Fire Pulse defined in paragraphs and sub paragraphs of 3.1.2, 3.2.1.4, 3.2.1.6, and 3.3.1 of the SRD and provide a level of detail and supporting documentation to clearly demonstrate compliance to the requirement.

(c) Maintenance and Reliability

(i) Captive Carriage The offeror’s proposal shall document the approach to the Captive Carry requirements defined in paragraph 3.8.6.2 of the SRD and provide a level of detail and supporting documentation to clearly demonstrate compliance to the requirement.

(ii) Shelf/Service Life The offeror’s proposal shall document the approach to the Shelf/Service Life requirements defined in paragraph 3.9.1 of the SRD and provide a level of detail and supporting documentation to clearly demonstrate compliance to the requirement.

(iii) Reliability The offeror’s proposal shall document the approach to the Reliability requirements defined in paragraph 3.9.2 of the SRD and provide a level of detail and supporting documentation to clearly demonstrate compliance to the requirement.

4.3.2. Sub-Factor Two – Manufacturing and Quality

(a) Diminishing Manufacturing Sources and Material Shortages (DMSMS) The offeror’s proposal shall document the approach to DMSMS and provide a level of detail and supporting documentation to clearly demonstrate compliance to the requirement defined in SOO paragraph 2.11.2

(b) Product Transition Plan The offeror’s proposal shall provide a Product Transition Plan that provides a level of detail and supporting documentation to clearly demonstrate compliance to the requirement defined in SOO paragraph 2.11.9

4.3.3 Sub-Factor Three – Management Approach

(a) Data Rights Attachment 2 “Rights to Data.” The offeror shall complete Attachment 2 in accordance with the following instructions:

(i) Provide Unlimited rights to all noncommercial technical data listed in Table 1 of Attachment 2 where the phrase “Unlimited” is stated in column 3 of the row associated with that item of technical data;

(ii) Provide Unlimited Rights or Government Purpose Rights to all remaining noncommercial technical data and computer software listed in Table 1 of Attachment 2 where the phrase “Offeror to Complete” is stated in column 3 of the row associated with that item of the technical data or computer software.

(iii) With respect to all commercial item technical data and computer software licenses listed in Table 2 of Attachment 2, licenses that comply with Attachment 2 section a.(5) of the RFP;

(iv) Special License Rights to data other than technical data (e.g., schedule/milestones data, financial data) described in section a.(6) and listed in Table 3 of Attachment 2 and;

(1) Special License Rights to review all data used by the contractor to create any CDRL or CLIN delivered under this contract to verify the currency, accuracy and completeness of the data contained in those CDRLs/CLINs described in Attachment 2 a.(5), (6) and (7).

With respect to paragraph a.(1), the Government made the determination that various CDRLs listed in Attachment 2 must be delivered with Unlimited Rights after reviewing the tailored Data Item Descriptions referenced in those CDRLs consistent with the statutorily-defined categories in 10 U.S.C.

2320(a)(2)(F)(i)(II). With respect to paragraph a.(2), the Government made the determination that various CDRLS listed in Exhibit A must be delivered with Government Purpose Rights to meet the C-HOBs Program minimum needs consistent with Federal law.

(2) All data produced under CLIN 1000, 1000AA and 1001 is associated with design, development, qualification and is a cost-reimbursable CLIN. The Government will be reimbursing the contractor its allocable, allowable, and reasonable costs of performing the work to satisfy the requirements of this RFP.

As a result, the Government is to receive unlimited rights to all data produced under CLIN 1000, 1000AA and 1001.

(v) The offeror shall:

(1) Complete the Section K provision entitled “Identification and Assertion of Use, Release, or Disclosure Restrictions” (DFARS 252.227-7017) and Column 3 of Table 1 in Attachment 2 by identifying the specific type of data rights the offeror asserts it will retain and ensure that the statements in both the Section K provision and Attachment 2 are consistent with each other in all respects,

(2) Complete Table 1 in Attachment 2 in the following manner:

(A) With regard to items of technical data associated with cells in Column 3 of that table labeled as “Unlimited”, leave those cells as is.

If, however, the offeror is not willing to sell Unlimited Rights to an item labeled as such in Column 3, place the following character (“—“) in the corresponding cell in Column 3 of the table in Attachment 2 associated with that item.

(B) With regard to items of technical data or computer software associated with cells in Column 3 of that table labeled as “Offeror to Complete,” insert either “Government purpose” or “Unlimited” into each such cell. If, however, the offeror is not willing to sell Government Purpose Rights to an item that contains the phrase “Offeror to Complete” in Column 3 for that item, place the following character (“—“) in the corresponding cell in Column 3 of the table in Attachment 2 associated with that item.

(C) Insert a proposed estimated cost into each cell in Column 4 of that table for those items of data or computer software associated with that item’s corresponding cell in Columns 1-2. Because CDRLs **35, **36, **37, **38, **39, **40, and **45 contain technical data, computer software and computer software documentation, the offeror shall propose one estimated cost for the rights in noncommercial technical data, computer software and computer software documentation to be delivered for each of those CDRLs. If the offeror is not willing to sell Unlimited Rights to an item labeled as such in Column 3 or Government Purpose Rights at a minimum to an item labeled as “Offeror to Complete” in that column, the Offeror shall place the following character (“—“) in the corresponding cell in Column 4 of the table in Attachment 2 associated with that item to signify that the Offeror is not willing to sell such rights to that item.

The Government notes that it is entitled to Unlimited Rights in technical data and computer software associated with certain items delivered under this contract in certain situations, even where those items were not developed exclusively with Government funding (see DFARS 252.227-7013(b)(1)(ii, iv-ix) and DFARS 252.227- 7014(b)(1)(ii-vi).

(vi) Complete Table 2 in Attachment 2 in the following manner:

(1) In Column 1 of that table, identify the CDRL number which will contain that commercial technical data or computer software

(2) In Column 2 of that table, identify the Data Item Title (Subtitle) of that CDRL.

(3) In Column 3 of that table, identify the name(s) of all vendor(s) that will be supplying commercial item technical data or computer software in alphabetical order, the trade name(s) of the technical data or computer software application(s) and the version number or issue date of that technical data or computer software (e.g., “Adobe Acrobat 9”), and the license number(s) of that commercial item technical data or computer software to be provided as part of that CDRL. (Note: If the offeror purposes to deliver any Public Domain/Open Source Software (PD/OSS), the offeror shall only identify the base product in Column 3 – not the dependencies (e.g., PD/OSS licenses referenced in the proposed PD/OSS license)).

(4) In Column 4 of that table, insert the quantity associated with the licenses relating to the delivery of commercial item technical data, commercial item software, or commercial item software documentation the offeror proposes to deliver to the Government in that CDRL or CLIN

(5) In Column 5 include the estimated cost.

(vii) Complete Table 3 in Attachment 2 by inserting a proposed estimated cost into each cell associated with that item’s corresponding cell in Column 3 including only direct costs. If the offeror is not willing to sell the rights described in Attachment 2 to an item listed in that table, the Offeror shall place the following character (“—“) in the corresponding cells in Column 3 of that table associated with that item to signify that the offeror is not willing to sell such rights to that item.

(viii) In subsection a.(7), replace the asterisk (**) with the estimated direct cost for Special License Right Category B. If the Offeror is not willing to sell the rights described in Attachment 2 for the rights described in that subsection, the offeror shall place the following character (“—“) in the corresponding cells in Column 3 of that table associated with that item to signify that the Offeror is not willing to sell such rights to the Government.

(viv) To ensure that the parties will maintain proper configuration control of all licenses throughout the performance of the resulting contract, create an “Appendix A” to Attachment 2 with a separate tab for each vendor listed in Table 2 (e.g., “appendix A-1: Adobe”). Insert into that separate tab one copy of every license listed in column 3 of Table 2 associated with any technical data or computer software the Offeror will purchase from that vendor and subsequently deliver to the Government, including, but not limited to all licenses associated with any Public Domain/Open Source Software (PD/OSS)(including licenses to the base software application and all dependencies) proposed to be delivered to the Government under any CDRL or CLIN listed in the order in which that license appears in that table. If an offeror proposes to deliver such software to the Government, the base license(s) associated with that PD/OSS may incorporate by reference licenses from dependent PD/OSS. Under such circumstances, to minimize duplication of such dependent licenses in Appendix A the offeror shall (1) list those dependent licenses on a separate sheet of paper immediately following a copy of the base license and indicate in which tab of Appendix A that/those dependent license(s) may be found, and (2) include only one copy of that/those depend license(s) in a separate tab for that vendor. Each non-PD/OSS license contained in that appendix shall expressly refer to the identical vendor, trade name, version number and issue date of that technical data or computer software listed in Table 2.

The Government expects that prior to inserting any proposed license into Appendix A, the offeror will have carefully read the license to ensure that its terms and conditions are consistent with all requirements of this RFP.

(b) Integrated Master Schedule (IMS) The offeror’s proposal shall provide an IMS that provides a level of detail and contains the supporting documentation that clearly demonstrate compliance to the requirement defined in SOO paragraph 2.6, 2.11, 2.11.1. Submit IMS as an appendix to your technical Volume I.

(c) Integrated Master Plan (IMP) The offeror’s proposal shall provide an IMP that provides a level of detail and contains the supporting documentation that clearly demonstrates compliance to the requirement defined in SOO paragraph 2.6 and 2.11. Submit IMP as an appendix to your Technical Volume I.

(d) System Engineering Management Plan (SEMP)

The offeror’s proposal shall provide an SEMP that provides a level of detail and contains the supporting documentation that clearly demonstrates compliance to the requirement defined in SOO paragraph 2.2. Submit SEMP as an appendix to your Technical Volume I.

(e) Quality Management System (QMS) The offeror’s proposal shall provide AS9100C or higher certification and QMS documentation that meets the requirements outlined in AS91000C or higher. Submit certification and QMS documentation as an appendix to your Technical Volume I.

4.3.4 – Small Business Approach

If the offeror is other than a small business, the offeror shall submit small business goals as identified in paragraph 2.2.7(a) of Section M within the Contractor Statement of Work (CSOW). Section 3.11 of the SOO shall be populated with Small Business Goals and submitted in the CSOW.

5. VOLUME II – PAST PERFORMANCE

Offerors shall submit recent, relevant contracts that can demonstrate performance quality as defined below. The Government will consider this information, along with information obtained from other sources (e.g. Past Performance Information Retrieval System (PPIRS)).

5.1.1. Recency is defined as performance five years old or less. The Government will not consider performance on contracts/task orders where performance was concluded more than five years prior to this solicitation’s issue date.

5.1.2. Relevancy is defined as work that involves similar types and complexities of products described in the Request For Proposal (RFP). For Government contracts, any relevant Government contract will be considered and reviewed to determine past performance history.

5.1.3. Performance Quality is defined as past performance that was compliant with subcontracting plan goals, adverse information identified, positive information identified and will be determined based on formal rating systems to include but not limited to CPARs and informal ratings to include but not limited to customer surveys or interviews.

Offerors may address any performance problems/issues that the Government may identify and explain corrective action taken and current status. The Government will consider this information in determining the offeror’s past performance rating.

5.2.1. An offeror’s failure to address performance problems/issues within this volume does not preclude the Government from using such information in determining a past performance rating.

If a joint venture is contemplated, provide complete information as to the joint venture.

Include any relevant and recent past performance information on previous joint ventures with same partner. If this is a first time joint venture, each party to the joint venture must provide a list of past relevant contracts.

Offerors must use the PPI Tool (Use latest version from FBO.gov) in order to electronically submit the Past Performance Volume in accordance with the RFP. See Appendix I for instructions.

6. VOLUME III – COST/PRICE

General Instructions – This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness of your proposed cost/price just for effort associated with Cost Reimbursable CLINs; CLIN 1000 “Design and Development (1000AA “Container and Packaging Design” –NSP) 1001 “Low Altitude Drop Test” and CLINs 2002, 3010, 4009, 5009, 6009 and 7010 “Travel.” Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that for Cost Reimbursement CLINs unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the Offeror does not understand the requirement or has submitted an unrealistic proposal. The pricing criteria will be: (1) Completeness, (2) Reasonableness, (3) Balance, (4) Realism and (5) Total Evaluated Price (TEP) as defined in Section M of the RFP which will be assessed from the information provided in this volume. Offerors should review Section M criteria to ensure the minimum requirements are met.

Total Evaluated Price (TEP)

6.2.1. Offerors shall input into the TEP Worksheet, located in Appendix 3 (attached separately) of Section L costs for the development CLINs and costs for the production CLINs in the specified quantity bands. Fee for the Cost Plus Fixed Fee (CPFF) shall be separately priced as found in the TEP worksheet. The notional quantity for sensors and associated weighting of the band prices will not be disclosed to offerors. The TEP is for evaluation purposes only, however all proposed cost, prices and fee are contractually binding.

6.2.1.1. The offeror shall provide priced Basis of Estimates (BOE)s located in Appendix IV (separately attached) of Section L for CLIN 1000 for Design and Development (CLIN 1000AA Container and Packaging Design – NSP), and CLIN 1001, “Low Altitude Drop Test” to the third level Work Breakdown Structure (WBS) detail. The offeror shall show base labor rate, material (if applicable), a breakout of all indirect rates applied, any other applicable costs, and fee. Also, indicate the basis for these rates and reference (if applicable) the current Forward Pricing Rate Agreement/Recommendation/Proposal (FPRA/R/P) or audit the rates were taken from. The organization of this BOE shall follow the offeror’s technical proposal, and be arranged in a logical fashion. Unlike the TEP, offerors can adjust the BOE worksheet to capture different labor categories, subcontractor costs, etc. The figures included are just for example only and should be modified.

6.2.1.2. Submit a copy of the completed TEP worksheet in Price Volume III in Microsoft Excel (non PDF format).

6.2.2. Cost or Pricing Information Requirements – IAW FAR 15.402, 15.403-1(b) and 15.403-3(a), information other than certified cost or pricing data may be required to support price reasonableness. If after receipt of proposals, the CO determines that there is insufficient information available to determine the reasonableness of the proposed pricing the offeror may be required to submit additional information other than certified cost or pricing data. If, during the source selection process, the CO determines that adequate competition no longer exists, certified cost and pricing data may be required.

6.2.3. Rounding – All dollar amounts provided shall be rounded to the nearest dollar.

6.2.4. Pricing Assumptions – Summarize all significant pricing assumptions, scope limitations and/or qualifications of the Price Volume III. IAW with Table 1, Pricing Assumptions shall not exceed 4 pages.

6.2.5. Estimating Techniques and Methods – Offerors shall use generally accepted estimating techniques to develop their estimates for the cost or prices in the TEP.

7. VOLUME IV – CONTRACT DOCUMENTATION

Provide all Volume IV Contract Documentation in the prescribed format identified in Table 1.

Model Contract/Representations and Certifications.

Section A – Solicitation/Contract Form: Complete blocks 8, 15, 16, 17 and 18.

Signature by the offeror on the SF 33 constitutes an offer, which the Government may accept.

Section B – Supplies or Services and Costs/Prices: Do not input pricing information in Section B of the model contract. All required prices shall be proposed in the TEP Worksheet Appendix III (separately attached) to Section L.

Section I – Contract Clauses

Section K – Representations, Certifications, and other Statements of Offerors:

Complete representations, certifications, acknowledgments and statements. Offeror must have filled out an online provision 52.204-08 Annual Representations and Certifications (Dec 2012), Online Reps and Certs at http://www.sam.gov.

CSOW – In accordance with SOO

7.8 Ability to obtain resources - Submit acceptable evidence that your company possesses adequate financial resources to perform the contract. This information will be used as part of the Contracting Officer’s determination of responsibility IAW FAR 9.104.

7.9. Small Business Contracting Plan - Submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9 that also identifies and specifies the extent of offeror’s commitment to the participation of small businesses, veteran-owned small business, service-disabled veteran-owned small business, HUBZone small business, small disadvantaged business, and woman-owned small businesses, whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable submit a copy of your approved Master Plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the offeror must submit the information that identifies and specifies the extent of its commitment to the participation of small and small disadvantaged businesses

7.10 Associate Contractor Agreement (ACA) - The contractor shall enter into an Associate Contractor Agreement with the Boeing Company under Contract FA8681-14-D- 0028 to be able to interface the sensor with the JDAM. The contractor is responsible for negotiating the terms and conditions and negotiating a price with Boeing for entering into an ACA. The contractor shall be in compliance with paragraph 1.2 of the SOO.

7.11 Exceptions to Solicitation Requirements – Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or sub-http://www.sam.gov/ factors. Failure to meet a requirement may result in an offer being ineligible for award.

Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete 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 2.

Table 2 – Solicitation Exceptions

7.12 Other Information Required

7.12.1 Authorized Offeror Personnel - Provide the name, title, telephone number, and email address of the company/division point of contact responsible for negotiating with the Government.

SOLICITATION

Document

Page/ Paragraph

Requirement/ Portion

Rationale

CSOW, Model Contract, Section L, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

SECTION L APPENDIX I

Downloading the PPI Tool

The PPI Tool can be downloaded by performing the following steps (if you are unable to download the Tool, contact the contracting officer for assistance):

1. Access the FedBizOpps (https://www.fbo.gov/) website.

2. Find the solicitation posting.

3. Locate the “ppi tool” link from the “All Files” column on the solicitation’s “Notice Details” tab .

4. Select the link and save the “ppi tool” to your computer. Name the file as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA8213-18-R-3015.mdb).

Note: PPI Tools saved in Microsoft version 2007 and greater will be saved with “.accdb” file extension.

Entering information in the PPI Tool

After selecting and saving the tool, enter information by performing the following steps:

1. Open the saved PPI Tool.

2. Select the “Options” button from the “Security Warning” banner, if applicable

3. The “Security Alert” pop-up screen displays.

Figure 1: Security Alert Pop-up https://www.fbo.gov/

Note:

• Files saved using Microsoft Office 2010 will have the “Enable Content” button on the “Security Warning” banner and therefore will not get a Security Alert pop-up.

• If a "read only" file is opened, in order to populate data in the file, click "Save As" in the "Read-Only" message bar. Enter the filename as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA8213-18-R-3015.mdb).

4. Select the radio button “Enable this content” and then click “OK.” A setup pop-up screen displays.

Figure 2: Setup Pop-Up

5. Select the “Start” button. The “Application Setup” screen displays.

Figure 3: Application Setup Screen

Note: Once the Offeror’s Name and RFP Number have been entered they can be edited by selecting the “Edit Offeror And RFP Number” button from the “Contractor’s Menu”

6. Enter the Offeror’s Name and RFP Number and then click the “Next” button. The application setup continues.

Figure 4: Continue the Application Setup

7. Choose the appropriate option by selecting the corresponding radio button and then click the “Next” button. The “Contractor’s Menu” displays.

Figure 5: Contractor’s Menu

8. Click the “Step 1: Set up Business Relationships” button to create a business relationship, if applicable, for each business entity before proceeding throughout the PPI Tool (refer to Section L of the RFP for detailed instructions). Identify all prime and sub-prime organizations and categorize them according to the appropriate role in the proposed acquisition. The “Business Relationships” screen displays.

Figure 6: Business Relationships

9. Click the “New” button to create a business relationship for the proposed acquisition. An additional “Business Relationships” screen displays.

Figure 7: Enter New Business Relationship

10. Complete the fields as follows (fields marked on the screen with an asterisk ‘*’ are required):

• Contractor’s Name: Self-explanatory

• Role in Proposed Acquisition: Choose one of the four options – Prime, Sub, Joint

Venture, or Other (Explain). An explanation comment box will display when you select “Other.”

• Place of Work: Location where contractor will perform work.

• Percentage of Work: Identify percentage of work contributed by specified contracting organization.

• Responsibilities: Detail responsibilities of specified contracting organization.

11. Select one of the buttons at the bottom of the screen.

• Add – Saves the current business relationship and allows for the addition of a new one.

• Close – Cancels the current business relationship without saving.

Note: In order to edit or delete an existing business relationship in the list, double-click on it.

12. Select the “Close” button on the “Business Relationships” screen after all of the business relationships has been added.

13. Click the “Step 2: Enter Past Performance Information (PPI)” button to enter the Past Performance Information. The “Past

Performance” screen displays.

Figure 8: Past Performance

14. Click the “New” button to enter Past Performance Information for the proposed acquisition. An additional “Past Performance” screen displays.

Figure 9: Enter Past Performance Information

15. Complete the fields on each of the tabs as follows (fields on the screen marked with an asterisk ‘*’ are required):

• Contract Information Tab Contractor: Select from the dropdown the appropriate contractor.

Cage Code: Self-explanatory.

Contract Number: If you don’t have a contract number, enter “N/A.”

Program Title: Enter full name of program.

Contracting Agency/Customer: Enter servicing contracting agency and customer

(office symbols suffice).

DUNS Number: Self-explanatory

Delivery Task/Order: If the order is provided as a stand-alone reference, enter the task/call/delivery/purchase order number.

Contract Type: Enter Firm-Fixed-Price (FFP), Cost Plus Fixed-Fee (CPFF), Indefinite Delivery/Indefinite Quantity (ID/IQ), LH, Blanket Purchase Agreement (BPA), Cost Plus Incentive-Fee (CPIF), Cost Plus Award Fee (CPAF), etc. For additional clarification, click the question mark button.

Short Program Title (i.e. Acronym): Enter abbreviated title for the program or enter “N/A.”

Contract Dollar Value:

o Original: Input total contract dollar value, with all options if applicable, in the amount originally awarded on the referenced contract.

If ID/IQ or BPA, provide total ceiling.

If stand-alone task/call/delivery/purchase, provide amount of the individual contract.

o Current: Input total contract dollar value, with all options if applicable, as the contract stands at time of PPI submission.

If ID/IQ or BPA, provide total ceiling.

If stand-alone task/call/delivery/purchase, provide amount of the individual contract.

o Explain the differences in Contract Value, if applicable: Enter an explanation of the difference between the original contract dollar value and the revised value as of the time of PPI submission.

Period of Performance (mm/dd/yy) o Start Date: Input start date of contract.

o Original End Date: Input original end date based on award.

o Current End Date: Input end date, as the contract stands at time of PPI submission.

o Explain the differences in Period of Performance, if applicable: Enter an explanation of the difference between “Original End Date” and “Current End Date.”

Program Details Tab Brief Description of Effort as:

o Select Prime, Sub, Joint Venture, or Other (Explain). An explanation comment box will display when you select “Other.”

o Provide a brief description of the service provided and actual work performed under this contract reference.

o ****If applicable: Provide information on problems encountered on the identified contracts. At a minimum, briefly describe the problem experienced, actions taken to alleviate the problem, and whether or not the problem was satisfactorily overcome.****

Explain how your performance on this contract is relevant for each applicable factor or sub-factor, as instructed under Past Performance in Section M of the RFP. Include any unique aspects that demonstrate relevancy in this effort. Provide evidence to support such relevance to the requirements as described in the RFP.

Include relevant information concerning your compliance with FAR 52.219-8, Utilization of Small Business Concerns, on the contract you are submitting, if applicable

Identify whether a subcontracting plan was required for the contract you are submitting. If one was required, identify in percentage terms the planned versus achieved goals during contract performance. Explain why goals were not met, if applicable:

POC & Key Individuals Tab Key Individuals: Click the “New” button to specify any key individual or individuals who participated in this program or who may support the proposed acquisition. Also indicate their roles for both acquisitions, previous and current. To edit or delete an existing key individual, double-click an item from the list.

Note: In accordance with FAR 15.305(a)(2)(iii), relevant contract efforts performed by from key personnel may be evaluated. If you wish to include the past performance of individual key personnel, select the “New” button for each individual and fill out the necessary information.

Customer Points of Contact: Click the “Program/Site Manager,” “Contracting Officer” or “Admin POC” button for the point of contact that you would like to add, edit, or delete.

Note: For government contracts provide current information on Program Manager, Contracting Officer, and Admin POC, if available.

For commercial contracts provide points of contact fulfilling these same roles, if available.

16. Select from the buttons at the bottom of the Past Performance screen:

• Save – Saves the Past Performance Information and displays the “Contract Information” tab on the Past Performance screen.

• Close – Closes the Past Performance screen. If there were any updates, a pop-up window displays asking to save before closing.

• Delete – Deletes the current PPI record. A pop-up window displays, select “Yes” to delete the record or “No” to close the window without deleting the record.

Note: In order to edit or delete an existing PPI record in the list, double-click on it.

17. Select the “Close” button on the “Past Performance Information” screen after all of the PPI records have been added.

Printing Reports and Submitting PPI Tool In order to print the Business Relationships and PPI reports, perform the following steps:

1. Click the “Step 3: Print Report” button . A pop-up displays asking which report to print.

Figure 10: Select Report to Print

2. Select separately each of the two options, “Business Relationships” or “Past Performance.”

The Business Relationships and Past Performance documents will print separately; combine the two to create your Past Performance Volume.

In order to submit the Business Relationships and PPI, perform the following steps:

3. Click the “Step 4: Submit” button . The “Submission Instructions” screen displays.

Figure 11: Submission Instructions

4. Follow the submission instructions. Hard copies of the pages generated from this tool shall be used in the hard copy of the Past Performance Volume subject to the limitations outlined in this RFP and should be Tab 1 of the Past Performance Volume.

Note:

• Submit an electronic copy (e.g. CD) of the saved PPI database file with your proposal. If a prime contractor is submitting the file enter the filename as:

o Prime contractor + RFP number + file extension (e.g. XYZCompany FA8213-18- R-3015.accdb)

If a subcontractor is submitting the file enter the filename as:

o Subcontractor + RFP number + file extension (e.g. ABCCompany FA8213-18-R-

3015.accdb)

• Once the file is saved to a CD or any…