DRAFT_Section L.pdf

FA8609-21-R-XXXX

Section L – Instructions, Conditions and Notices to Offerors

SOURCE SELECTION INFORMATION - SEE FAR 2.101 and 3.104

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

SECTION L

Instructions, Conditions and Notices to Offerors (ITO)

FOR THE

KC-46 INITIAL SPARES (KIS)

Solicitation #FA8609-21-R-XXXX

XX XXXXX 2021

Prepared by:

Mobility Directorate, KC-46 Program Office (AFLCMC/WLC)

Table of Contents

1.0 KIS Structure and Objectives

1.1 Objectives

1.2 Approach

1.3 Proposal Preparation Instructions

2.0 General Information

2.1 Point of Contact (POC)

2.2 Debriefings

2.3 Discrepancies

2.4 Electronic Reference Documents

2.5 Communications

2.6 Pre-Award Surveys

2.7 Organization/Number of Copies/Page Limits

2.7.1 Page Limitations

2.7.2 Classified Information

2.7.3 Indexing

2.7.4 Glossary of Abbreviations and Acronyms

2.7.5 Marking

2.7.6 Page Size and Format

2.7.7 Electronic Offers

2.7.8 Proposal Submission

2.7.9 Deadlines

3.0 Volume I - Executive Summary

3.1 Narrative Summary

3.2 Table of Contents

4.0 Volume II - Technical Approach

4.1 General

4.2 Technical

4.3 Technical Risk

4.4 Strengths

4.5 Volume II Organization

4.5.1 Entry Gates

4.5.2 Technical Approach

5.0 Volume III - Price

5.1 General Instructions

6.0 Volume IV- Contract Documentation

6.1 Model Contract/Representations and Certifications

6.1.1 Section A - Solicitation/Contract Form

6.1.2 Section B - Supplies or Services

6.1.3 Section C - Statement of Work

6.1.4 Section D - Packaging and Marking

6.1.5 Section E - Inspection and Acceptance

6.1.6 Section F - Deliveries or Performance

6.1.7 Section G - Contract Administrative Data

6.1.8 Section H - Special Order Requirements

6.1.9 Section I - Order Clauses

6.1.10 Section J - Attachments

6.1.11 Section K - Reps., Certs., and other Statements of Offerors

6.2 Exceptions to Terms and Conditions

6.3 Other Information Required

6.3.1 Authorized Offeror Personnel

6.3.2 Government Offices

6.3.3 Company/Division Address, Identifying Codes, & Applicable Designations . 14

6.4 Non-Government Advisors

6.5 Small Business Subcontracting Plan (SBSP)

1.0 KIS Structure and Objectives

1.1 Objectives

The KC-46 Initial Spares Program, hereafter referred to as KIS, is a contract vehicle designed to provide reparable line replaceable units (LRU)(s) to worldwide locations to include but not limited to USG and Foreign Partner Main Operating Bases (MOB)(s) that comply with Federal Aviation Administration (FAA) defined processes and procedures.

Air Force Life Cycle Management Center (AFLCMC), Mobility Directorate, KC-46 Program Office (AFLCMC/WLC) plans to competitively award multiple Indefinite Delivery Indefinite Quantity (ID/IQ) contracts to streamline and standardize the acquisition and support the procurement process of initial spare parts for the KC-46.

1.2 Approach

KIS will establish a flexible and responsive capability to meet our customers’ needs by providing a base of pre-qualified contractors who can be rapidly accessed through both competitive and noncompetitive methods, as appropriate, to provide the required products described in the KIS Statement of Work (SOW). Each delivery order will specifically define the spares required by the contractor.

The ordering period for KIS is ten (10) years. The ordering period is defined as the time period that delivery orders can be issued under this contract. The ordering period is broken out as follows: a five (5) year base, plus one five (5) year option, if exercised.

The Government intends to award basic ID/IQ KIS Firm-Fixed Price (FFP) contracts.

Applicable contract type contract line item numbers (CLINs) will be specified on each individual delivery order.

In accordance with FAR 52.216-19, the stated “minimum order amount” of $1.00, but no more than $1,000.00, will be obligated via orders issued after announcement of successful Offerors.

Offerors must receive a basic contract award to be eligible to receive a delivery order award.

Delivery orders issued under these contracts will be incrementally or fully funded in accordance with (IAW) federal appropriations law. The aggregate ceiling of the KIS program is $1.894B.

1.3 Proposal Preparation Instructions

This section of the ITO provides general guidance for preparing proposals, as well as specific instructions on the format and content of the proposal. Offerors are required to submit one proposal with sufficient information concerning all factors to enable Government personnel to fully ascertain the Offeror’s capabilities to perform the requirements. The Offeror’s proposal must include all data and information requested by the ITO and must be submitted IAW these instructions. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors. Alternate proposals are not acceptable. Non-conformance with the instructions provided in the ITO may result in a grossly deficient proposal evaluation and may render the proposal unawardable.

CHARLES SMITH

If all acceptable offerors get an award, what is the purpose of stating this?

ENGELMAN, BRANDON L CIV USAF AFMC AFLCMC/WLC, KC-46 Sustainment Similar to Section L, will discuss with ACE

CHARLES SMITH

Based upon your Section M language (“The Government intends to award multiple contracts; one to each Offeror that has an “Acceptable” Technical Factor and a Low/Moderate Risk rating”), it’s not clear on what basis you would do this. The TEPs will not help you make a cut, so on what basis would one reasonably be made?

CHARLES SMITH

This type of language is more appropriate for Section M.

ENGELMAN, BRANDON L CIV USAF AFMC AFLCMC/WLC, KC-46 Sustainment Will move/delete

CHARLES SMITH

Meaning unclear. If they are an “offeror,” they are part of the competition.

BRAINERD, TANIS K CIV USAF AFMC AFLCMC/WLC, KC-46 Development IPT Fall out of delivery window, defective part – poor performance – off ramp…thinking 5 base, 5 option…on ramp…COVID…can we off-ramp during the base period?

BRADY CILLO

This statement doesn’t sound quite technically correct since the funding will be on the order, not on the basic. I think you are covered by the first sentence of this paragraph and can delete this sentence

The proposal shall be clear and 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. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and that the Government will base its evaluation on the information presented in the Offeror’s proposal. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

Offerors are advised that the costs of any response to or otherwise incurred as a result of responding to this proposal request are not chargeable to this proposal effort.

The proposal acceptance period is specified in Section A of the model contract/ solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid until 31 March 2022.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one digital copy of all unsuccessful proposals. The Government will not return any proposals and will destroy any additional digital or printed copies of proposals.

2.0 General Information

2.1 Point of Contact (POC)

The Contracting Officer (CO), Tanis Brainerd, e-mail: tanis.brainerd.1@us.af.mil and Contract Specialist, Brandon Engelman, e-mail: brandon.engelman@us.af.mil are the exclusive POCs for this acquisition. Written questions or requests for clarification may be sent via email to these individuals. It is encouraged that any such questions or requests be submitted within 10 days after the RFP release date. Answers to such questions and clarifications will be provided via posting questions and answers (Q&As) and/or RFP amendments on the beta.SAM website (https://beta.sam.gov). In the event of conflict between the answer to questions and the RFP, the RFP shall take precedence.

2.2 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. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to receive their debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing and must make their request within three days after being notified that they have been excluded from the competition.

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

file://c1aafsaa1/users/HallMA/Documents/far/FAR15.DOC#b15505 file://c1aafsaa1/users/HallMA/Documents/far/FAR15.DOC#b15506 ENGELMAN, BRANDON L CIV USAF AFMC AFLCMC/WLC, KC-46 Sustainment Do we want to specify his date? (Add 6 months).

BRADY CILLO

Yes, otherwise it defaults to 60 days. See what is on your schedule for projected award date and use that number

BRAINERD, TANIS K CIV USAF AFMC AFLCMC/WLC, KC-46 Development IPT Note to self: Ensure I can check voicemails from this number

ENGELMAN, BRANDON L CIV USAF AFMC AFLCMC/WLC, KC-46 Sustainment I don’t really have an office phone number… recommend just including my email

2.3 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, as well as, the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right, and it is the Government’s intent, to award this effort based on the initial proposal, as received, without discussions.

2.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the beta.SAM website (https://beta.sam.gov). Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.5 Communications

Exchanges of source selection information between the Government and Offerors will be controlled by the CO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR

2.101 & 3.104 – Controlled Unclassified Information (CUI)” in the Subject line. Otherwise, source selection information will be transmitted via DoD SAFE (https://safe.apps.mil/).

2.6 Pre-Award Surveys

The Government may conduct Pre-Award Survey (PAS) IAW FAR 9.106 during proposal evaluations to aid in determining contractor responsibility.

2.7 Organization/Number of Copies/Page Limits

The Offeror shall prepare the electronic 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 as specified in the table. The contents of each proposal volume are described in the ITO paragraph as noted in the following table.

Volume Title Section L Para. No. Page Limit

I Executive Summary 3 2 II Technical Approach 4

Entry Gates 4.5.1 Subfactor 1 - Procurement Standard 4.5.2.1 Subfactor 2 - Requisition Process 4.5.2.2

III Price 5 Unlimited IV Contract Documentation 6 Unlimited https://beta.sam.gov/ file://c1aafsaa1/users/HallMA/Documents/far/Far02.doc#T2101 file://c1aafsaa1/users/HallMA/Documents/far/Far02.doc#T2101 file://c1aafsaa1/users/HallMA/Documents/far/FAR03.DOC#b3104 https://safe.apps.mil/

Do you really want to allow this?

2.7.1 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. Offerors will be notified of any excess page count.

Each page shall be counted, except as indicated in the paragraphs below. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

2.7.2 Classified Information

No classified information is required or permitted in the Offeror’s response.

2.7.3 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tables of contents do not count against the page limitations for their respective volumes.

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

2.7.5 Marking

All proposal pages shall include the following legend at the bottom of each page:

2.7.6 Page Size and Format

Page size shall be 8.5 x 11 inches. Pages shall be single-spaced as defined in paragraph settings/spacing in Microsoft Word, with a double space between paragraphs. Except for the reproduced sections of the proposal request document, the text size shall be no less than 12-point Times New Roman. 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 and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs.

Legible tables, charts, graphs, figures, diagrams, and schematics shall be used wherever practicable to depict organizations, systems and layout, implementation schedules, plans, etc.

These displays shall be uncomplicated and legible and shall not exceed 11x17 inches in size and shall be counted as two pages. For these displays, the text shall be no smaller than 10-point.

Transmittal letters will not be considered in the overall page count nor will they be evaluated.

I think this may be a legacy of hard copy proposals. What do you envision this to be for electronic only?

2.7.7 Electronic Offers

This is an electronic only submission. Offerors may submit their proposal via DoD SAFE (https://safe.apps.mil/), ensuring proposal submission by the required due date. No hard copies of proposals will be accepted. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office 2010 or later or in Adobe Acrobat 9.0 or later. Do NOT submit any documents in PDF format that are copied as “images.” When creating PDF files always submit with textual search and copy functions enabled.

FA8609-22-D-XXX, Section J, Attachment 2, Eligible Parts List, shall be submitted in workable Excel format.

The file-naming convention for the proposal volumes is as follows. It is permissible to expand on these file names if a list of the content of each is provided. It is permissible to shorten these file names as long as the Volume number and title, Factor number, and a keyword or phrase is utilized to ensure clarity and consistency.

Files File Name Volume I Executive Summary Offeror Name

Volume II Technical Approach Technical Approach

Volume III Price Price

Volume IV Contract Documentation Contract Documentation

2.7.8 Proposal Submission

The Offeror’s proposal shall be prepared and submitted in four (4) volumes: Executive Summary (Volume I); Technical Approach (Volume II), Price (Volume III) and Contract Documentation (Volume IV). All volumes must be received via DoD SAFE. In order to submit via DoD SAFE, a drop-off request is required. In order to receive a DoD SAFE drop-off, email the CO or Contracting Specialist listed in paragraph 2.1 above no more than 14 days and no less than 3 days prior to proposal submittal date.

2.7.9 Deadlines

All KIS proposal volumes must be received by 3:00 pm EDT on XX XXXX 2021.

3.0 Volume I – Executive Summary

In the executive summary volume, the Offeror shall provide the following information.

3.1 Narrative Summary

https://safe.apps.mil/

BRADY CILLO

I think you are just creating more work for yourselves by allowing this alternate submission method. DoD SAFE is simple enough to use and can just be the only method. Your call though. Don’t just include it because TSA IV included it, do what makes the most sense

BRADY CILLO

If using, capitalize the final R like the other places

BRADY CILLO

I understand why you are doing this (to keep Price separate), but this shouldn’t be necessary. The PCO/buyer will be the only one transferring files from either the discs or DoD SAFE onto the EZ Source file share. The technical team will be firewalled from accessing the price team’s folder. So rather than create this additional requirement, you will just put the appropriate volume in each team’s folder

BRADY CILLO

Completely up to you, but I might suggest naming these like:

Executive Summary – Offeror Name

One of your tasks is going to be to make sure none of the wires get crossed between a large number of offerors and if all the files are named the exact same, it doesn’t help your cause.

BRADY CILLO

Four

BRAINERD, TANIS K CIV USAF AFMC AFLCMC/WLC, KC-46 Development IPT Do these go to the ACE?

CHARLES SMITH

The ACE will have someone available to receive any proposals submitted via CD.

CHARLES SMITH

Do you want to reference TSA IV or KC-46 INITIAL SPARES (KIS)

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features. The salient features should tie in with Section M evaluation factors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal, and will not be evaluated.

3.2 Table of Contents

Include a master table of contents of the entire proposal.

4.0 Volume II – Technical Approach

4.1 General

The Technical Acceptability Volume should be specific and complete. Legibility, clarity, brevity, and coherence are important. Your proposal will be evaluated against the Technical Factor as defined in Section M, Evaluation Factors for Award. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2 Technical

In the Technical Volume, Offerors shall address their technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each technical subfactor.

4.3 Technical Risk

Address Technical Risk associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance.

Provide the rationale for each risk and its rating, including quantitative estimates of the impact on schedule and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: SOW), regardless of whether or not those requirements are identified as subfactors. Propose a realistic work-around or risk mitigation measures for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation and any proposed mitigation measures.

4.4 Strengths

Strengths will be contractually binding upon contract award. To incorporate strengths, the Offeror shall make recommendations in the appropriate contractual document(s) to include Section J Attachments with change bars. The Government reserves the right to determine the final contract language to incorporate these strengths into the contract.

4.5 Volume II Organization

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

a. Table of Contents (not included in the 20-page limit)

b. List of Table and Drawings (not included in the 20-page limit)

c. Glossary (not included in the 20-page limit)

d. Cross Reference Matrix (not included in the 20-page limit)

e. Entry Gates

i. FAA Certification Capability

ii. DDTC Certification

f. Technical Approach

i. Subfactor 1: Procurement Standard

ii. Subfactor 2: Requisition Process

4.5.1 Entry Gates

4.5.1.1 FAA Certification Capability

The Offeror must provide documentation to include but not limited to FAA 145 Repair Station Certification, 121 Operator Certification or Parts Manufacturer Authorization (PMA) Certification which validates that the Offeror is capable of providing FAA certified parts with an 8130-3, Authorized Release Certificate, Airworthiness Approval Tag.

4.5.1.2 DDTC Certification

The Offeror must be registered with the State Department’s Directorate of Defense Trade Controls (DDTC). Offeror’s must provide their valid DDTC documentation with proposal submission.

4.5.2 Technical Approach

4.5.2.1 Subfactor 1: Procurement Standard

A compliant proposal shall include:

The submittal of FA8609-22-D-XXX, Section J, Attachment 2 documenting delivery times after receipt of award for all items on the eligible parts list that the Offeror is able to deliver while still meeting all the requirements of paragraph 3 of the SOW. This delivery information shall be for a minimum of ninety (90) different eligible parts.

Title

BRADY CILLO

Perhaps “….documentation showing registration status…”? You want them to prove what is required in the first part of the sentence…“must be registered”

CHARLES SMITH

What kind of verification will they submit to prove this?

CILLO, BRADY M GS-14 USAF AFMC AFLCMC/AZK, Acquisition Center of Excellence Just throwing it out here, but would it be worth asking for “catalog pricing” for each of these parts? You will not evaluate them as part of the source selection, but they can be used in future price analysis if you ever get only one offer for these types of parts (without having to go back out and ask for more information at the time of the D.O….they will already be on file for comparison).

KTR format acceptable, but must include X,Y,Z in Excel

4.5.2.2 Subfactor 2: Requisition Process

A compliant proposal shall include:

Documentation that demonstrates the Offeror’s ability to provide a list of items (NSN/Part numbers) and delivery dates, a narrative describing their order management system for processing offline requisition numbers and tracking and enabling receipt of parts by the Air Force supply system.

5.0 Volume III – Price

5.1 General Instructions

a. The Offeror shall submit the price for CLIN TBD, Post Award Conference (PAC) in Section B of the model contract. The proposed price will serve as the contract minimum order IAW FAR 52.216-19 Order Limitations.

The Offeror will consider the following parameters in regards to the PAC.

1. The PAC shall be held virtually using an electronic communication venue mutually agreeable by both the Procuring Contracting Officer (PCO) and the vendor.

2. The number of vendor attendees shall be limited to a maximum of four persons and the PAC duration shall not exceed four hours.

b. The price for CLIN TBD shall be rounded to the nearest whole dollar.

c. Data beyond that required by this instruction shall not be submitted. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

d. Compliance with these requirements is mandatory and failure to comply may result in rejection of the proposal.

e. The CO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the CO will review this determination and if, in the CO’s opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit cost or pricing data.

ENGELMAN, BRANDON L CIV USAF AFMC AFLCMC/WLC, KC-46 Sustainment Phrasing, manual/automated

BRAINERD, TANIS K CIV USAF AFMC AFLCMC/WLC, KC-46 Development IPT See comment on Section M – Need this to be written to convey this is a “trade space” area

CHARLES SMITH

According to Section M, this will lead to “additional consideration” (strength), but there is no opportunity for an offeror to get any higher than Acceptable. This can’t be valued when everyone who is “acceptable” gets a contract.

KRISTY LEE

Would suggest re-wording. Might be confused with certified cost or pricing data. Maybe delete this sentence and add Volume III to the sentence after?

BRADY CILLO

In Vol IV you say “Section” B. Sections A – H of the contract are called “The Schedule” so Section is the correct term

KRISTY LEE

Update paragraph to the verbiage below;

The CO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the CO will review this determination and if, in the CO’s opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit cost or pricing data.

KRISTY LEE

What is the difference between this paragraph and the Communications paragraph above?

I’m not familiar with this type of paragraph. Are you planning to do oral presentations in discussions or is this a TSA IV thing that can be deleted?

6.0 Volume IV- Contract Documentation

6.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 digital copy of the Model Contract (Sections A through K). The completed model contract include the following:

6.1.1 Section A - Solicitation/Contract Form

Completion of blocks 13 through 16, signature for block 17, and date for block 18 of the Standard Form 33 is required. Signature by the Offeror on the SF33 constitutes an offer, which the Government may accept. The “original” signed copy should be clearly marked.

6.1.2 Section B - Supplies or Services

The price for CLIN TBD PAC needs to be completed. The Offeror shall not complete any other information in Section B. The contract clauses pertinent to this section and that are required to be filled-in are contained in Section B of the solicitation.

6.1.3 Section C - Statement of Work

The contract clauses pertinent to this section and that are required to be filled-in are contained in Section C of this solicitation.

6.1.4 Section D - Packaging and Marking

The contract clauses pertinent to this section are contained in Section D of this solicitation.

6.1.5 Section E - Inspection and Acceptance

The contract clauses pertinent to this section are contained in Section E of this solicitation.

6.1.6 Section F - Deliveries or Performance

The contract clauses pertinent to this section are contained in Section F of this solicitation.

6.1.7 Section G - Contract Administrative Data

The contract clauses pertinent to this section are contained in Section G of this solicitation. Upon award, Section G data will be provided by the Government.

6.1.8 Section H - Special Order Requirements

The contract clauses pertinent to this section are contained in Section H of this solicitation.

6.1.9 Section I - Order Clauses

The contract clauses pertinent to this section and that are required to be filled-in are contained in Section I of this solicitation.

6.1.10 Section J – Attachments

The following Section J attachments will be included as part of the KIS contract:

• Attachment 1, Statement of Work

• Attachment 2, Eligible Parts List

• Attachment 3, Small Business Subcontracting Plan (SBSP) (large businesses only)

Note: Large business Offerors are to submit their SBSP as an attachment to Volume IV (See Section 6.5 below).

6.1.11 Section K - Representations, Certifications, and other Statements of Offerors The Offeror’s completed representations, certifications, acknowledgements, and statements shall be submitted IAW FAR 52.204-8 “Annual Representations and Certifications.”

6.2 Exceptions to Terms and Conditions

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. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall specifically identify each paragraph and/or specific part of the solicitation to which the exception is taken.

As stated in paragraph 2, above, non-compliance with any solicitation requirement, including exceptions the Government deems unacceptable, may render a proposal unawardable. 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 following format.

Solicitation Document Paragraph/ Page

Requirement/ Portion Rationale

SOW, Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Justify why the requirement will not be met

6.3 Other Information Required

6.3.1 Authorized Offeror Personnel

Provide the name, title, email, and telephone number of the company/division POC authorized to negotiate with the Government and who can obligate your company contractually. Also, provide the name, title, email, and telephone number of the CEO, Division President, and/or Vice President.

6.3.2 Government Offices

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

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

6.4 Non-Government Advisors

Offerors are advised that contractors will participate as non-Government advisors in the evaluation of proposals. These advisors will sign non-disclosure agreements and will be authorized access to only those portions of the proposal data and discussions that are necessary to enable them to provide specific advice on specialized matters or on particular problems. The non-Government advisors will not determine or establish initial or final assessments of Offeror’s proposals. They will have access to Offeror proprietary, confidential, or privileged commercial data. The non-Government advisor support will be provided by:

Odyssey Systems 2012 Edgewater Drive Suite 270 Wakefield, MA 01880 781-245-0111 POC: Robin Sgrosso

Offerors shall provide, in the Contract Documentation Volume, a copy of paragraph (2) below or provide written objection to disclosure as indicated in paragraph (1). If the Offeror objects to disclosure of a portion of the proposal, the consenting paragraph (2) shall be provided for the remainder of the proposal.

1. Any objection to disclosure:

i. Shall be provided in writing to the Contracting Officer within the

Contract Documentation Volume of the proposal; and

ii. Shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the Offeror objects to disclosure to non-Government advisors.

2. I understand that proprietary, confidential, or privileged commercial data submitted to the Government in response to this solicitation may be released to non-Government advisors. I consent to the release of any (unless objection is provided in (1) above) proprietary, confidential, or privileged commercial or financial data provided by the firm(s) named below in response to this solicitation, to non-Government advisors for review and analysis:

Signature: Firm:

Name (individual authorized to commit firm):

Title:

Date of Execution:

The CO will evaluate any objection to disclosure and make a determination whether the non- Government advisor(s) shall be permitted to participate in the source selection. The CO shall inform the objecting Offeror of the final determination, and, if the use of non-Government advisors has been changed, shall inform all Offerors of the change.

6.5 Small Business Subcontracting Plan (SBSP)

Large businesses shall submit a SBSP (see FAR 19.701) that contains all the elements required by the clause at FAR 52.219-9, Small Business Subcontracting Plan. The SBSP shall be submitted as part of Volume IV and has no page limit. The SBSP shall include the subcontracting goals expressed at the ID/IQ contract level as a percentage of annual total obligated dollars on awarded task orders for each of the following: small business, veteran-owned small business, service-disabled veteran owned small business, HUBZone small business, small disadvantaged business, and women owned small business. The SBSP shall also describe the Offeror’s approach to meeting each of its subcontracting goals.

A plan, when incorporated in an individual contract, shall apply to that contract throughout the life of the contract. Although plans shall be effective for the life of the contract after approval by the contracting officer, it is incumbent upon contractors to maintain and update plans to include goals each time they win a task order award. Changes required to update plans are not effective until approved by the contracting officer. Failure to submit an acceptable plan may make the Offeror’s proposal unawardable. A contractor’s comprehensive SBSP and its successors, which are authorized by and approved under the test program of Section 834 of Pub. L. 101-189, as amended, may be submitted in lieu of the SBSP described above.

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_215.htm#P1296_221566