KRACEn RFP Amend 0001_mod doc.docx

N0042120R0105

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

RFP AMENDMENT(S) SUMMARY

Amendment 0001:

The purpose of Amendment 0001 is to make the following changes. Changes are reflected in bold green text in the applicable sections wherever possible. Deleted text is reflected as bold green strikethrough text.

1. Remove FAR Clause 52.230-1 from Section K.

2. Provide Attachment L-4 USMC FOSR identified in Section L, Part A, 1 h).

3. Remove “Original” and/or “Copy” verbiage from Section L, Part A, 2.1.1.

4. Remove “Original” and/or “Copy” verbiage from Section L, Part A, 3.

5. Remove part of the Section L, Part A, Table G-4 note that Attachment L-4 will be provided via future amendment.

6. Replace “SAM” requirement with “Section K” in Section L, Part B, 2.4 b.

All other terms and conditions remain unchanged.

SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS

The following have been deleted:

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L INFORMATION

Section L – Instructions to Offerors

PART A GENERAL INSTRUCTIONS

1. GENERAL

a) This solicitation is being issued on a competitive, 100% Small Business set-aside basis and utilizes the North American Industry Classification Code System (NAICS) code 336411 which has a small business size standard of 1,500 employees.

b) Throughout these instructions, “Offeror” is defined as the Prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement between two or more companies that form a separate legal entity to propose as a Prime contractor for the purpose of responding to this solicitation. “JV Members” are the entities that make up a Joint Venture. Each JV Member must be a small business under NAICS code 336411 unless the JV has a mentor protégé agreement approved by the SBA. For this solicitation, the term “entity” is used to mean any or all of the following: Prime contractor, JV, and JV members. The following entities are defined as “principal entities” (a) the Prime contractor (which includes the JV) and (b) JV Members. Only principal entities will be used in the Technical evaluation.

c) Offerors are required to submit sufficient information concerning the technical evaluation factor to enable Government personnel to fully assess whether the Offeror meets all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s capability to meet the requirements of the solicitation. Proposals must demonstrate that the Offeror is able and competent to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Alternate proposals are not acceptable and will not be evaluated.

d) In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal. Unsubstantiated statements that the Offeror understands, can or will comply with the requirements, has the aircraft maintenance experience, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

e) The Offeror shall include any data necessary to illustrate the proposal meets the requirements of the solicitation. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place, summarized, and referenced in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

f) All proposal information is subject to verification by the Government. Falsification of any proposal submission, documents, or statements may subject the Offeror to civil or criminal prosecution under Section 1001 of Title 18 of the United States Code.

g) Questions: Offerors shall submit any questions by using the RFP Question Submittal Form provided in Attachment L-3, requesting clarification of solicitation requirements by emailing the PCO, at Meagan.foster@navy.mil and Contract Specialists at Lydia.munley@navy.mil, and crystal.ashton@navy.mil The Offeror must include the company name and solicitation number in the subject line of the email. The question(s) must include the document and reference paragraph number that pertain to the Offeror’s question(s). The Government will not accept questions in person or by phone. Questions can be e-mailed after the solicitation is posted at http://www.beta.sam.gov; however, any questions received after 10 calendar days of the date this solicitation is issued will only be answered at the discretion of the PCO. The Government will post all non-proprietary Questions and Answers to http://www.beta.sam.gov.

h) The Government intends to compete a Task Order for the USMC FA-18 Maintenance Augmentation Support among MAC awardees concurrent with this source selection. Offerors are not required to submit a proposal for the USMC FA-18 Maintenance Augmentation Support Task Order (TO) to be considered for a KRACEn MAC award. To be considered for an award of the USMC FA-18 Maintenance Augmentation Support TO, Offerors must provide a complete and separate proposal for the TO as part of the response to this solicitation. Proposal instructions and evaluation criteria for the USMC FA-18 Maintenance Augmentation Support TO are provided in Section L as Attachment L-4.

2. PROPOSAL FORMAT AND SUBMISSION

Proposals shall be formatted using a Times New Roman 12 point normal font, single-spaced with 1-inch margins all around, and formatted for/printed on standard 8.5 x 11 inch paper. If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages shall be numbered with volume, paragraph, and page numbers. When fold-out pages are used, they shall not exceed 11 x 17 inches. Drawings may be provided separately and may be any size but shall be folded to approximately 8.5 x 11 inch standard size. If the Offeror uses graphs to convey information, the graphs must show enough detail to easily discern the information described. Graphs and tables shall be presented in no smaller than a 10 pt. font. Graphs shall contain a grid, which allows values to be read directly from the graph. Graphic resolution shall be consistent with the purpose of the data presented. Text utilized in charts, figures, and graphics shall also be no smaller than a 10 point font and may use a font type selected by the Offeror.

2.1 Electronic Submission of Proposal

This section is intended to provide information to the Offeror on the electronic format and application software to be used for submitting proposals. Use of the software and procedures described in this section will reduce the amount of time and effort needed to receive and install proposals onto the electronic evaluation system, and will ensure that the proposals received are suitable for reading electronically. If a discrepancy exists between the original paper copy of the proposal and the original electronic copy on the DVD-ROM disk, the original paper copy shall take precedence.

2.1.1 Electronic Proposal Media

The Offeror shall submit all volumes of its proposal electronically on DVD-ROM(s) compatible with the operating system and applications defined in Section 2.1.2 (Operating System and Applications).

Table G-3 (Proposal Structure) identifies the proposal structure for each volume. The Offeror should submit two sets of DVD-ROMs. The first set of DVD-ROM disks should be marked "Original” and the second set of DVD-ROM disks should be marked "Copy.” All content on the DVD-ROM Disks must be identical.

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft Windows 10 Operating System. Proposal information should be submitted using the following applications: Microsoft Word 2016, Microsoft Excel 2016, Microsoft PowerPoint 2016, and Microsoft Project 2016 and must be accessible to the Government; however, letters and other signed documents should be provided as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is discouraged except where specific instructions for non-.pdf or Office 2016 applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among proposal volumes.

2.1.4 Virus Free Electronic Submission

Offerors are responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information delivered throughout the evaluation (e.g., original proposal submission, responses to evaluation notices, Final Proposal Revisions) has been or will be checked for viruses and certify that its files are/will be virus free. The Offeror should specify the software, version, and virus definition used/that will be used to check the data.

2.1.5 Multimedia

The Offeror should not embed sound or video (e.g., MPEG) files within the proposal submission.

2.1.6 Graphics

The Offeror is encouraged to:

· Simplify the color palette used in creating figures and minimize the use of color print or graphics to the maximum extent possible;

· Minimize size of graphics files; and

· Avoid scanned images.

2.1.7 File Naming Conventions

Valid extensions for files using their associated applications are listed below in Table G-1 (File Extensions):

Table G-1 File Extensions

The Offeror shall follow the basic structure of the file naming convention in Table G-2 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where "#" represents the sequential numbering of files. Offeror’s shall keep the file name as short as possible (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names may become corrupt or inaccessible.

The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Offerors should not provide each section/paragraph as separate files.

The Offeror shall ensure that the electronically submitted files are directly traceable to paper copy submittals.

Table G-2 - Offeror Electronic File Naming Convention

Vol 1 Tech#.pdf

Vol 1 T Tables.pdf

Table T-2 Contract Summary

Vol 1 CAME#.pdf

Vol 2 CA#.pdf

Annexes

AnnA SDfCAME#.docx

Please note: The Offeror should provide both a .pdf and .docx version if they are available.

3. PROPOSAL CONTENT AND VOLUMES

The Offeror must present its proposal information in a manner that facilitates a one for one comparison between the information presented and Section L proposal instructions.

Each volume and annex of the proposal shall be submitted as original and additional paper and/or electronic copies as specified in Table G-3 (Proposal Structure). Each volume, book, or annex should be provided separately in a 3-ring binder. The binders should be of an appropriate thickness for the number of pages it contains (e.g., a 30-page book should not be placed in a 2-inch binder). Each binder must contain the following information using tabs and dividers:

· Cover and title page;

· Title of proposal and proposal number as applicable;

· Offeror’s name, address and POC;

· Solicitation number;

· Proposal volume/annex number; and

· Copy number; and

· Table of Contents (The table of contents must provide sufficient detail to easily locate important elements).

Table G-3 Proposal Structure

Table G-4 lists the attachments provided to the Offeror within Section L.

Table G-4 Section L List of Attachments

* Attachment L-4 will be provided via future amendment to this RFP. Offerors are not required to submit a proposal in response to L-4 to be considered for a KRACEn MAC award.

4. PROPOSAL SUBMISSION AND PACKAGING

4.1 Proposal Submission

a) All Proposals shall be UNCLASSIFIED.

b) Offerors are responsible for submitting all proposal information by the proposal submission date. The submission date for all Volumes of the proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 (Solicitation, Offer and Award) of the solicitation.

c) Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with the Procuring Contracting Officer (PCO), Maggie Foster. Offeror shall submit all paper and/or electronic copies of the proposal to the address provided below. Proposals shall not be submitted by facsimile or electronically via email.

Naval Air Systems Command ATTN: Maggie Foster Solicitation: #N00421-20-R-0105 22244 Cedar Point Road, Bldg. 460 Patuxent River, MD 20670

d) Hand delivered responses may be given to Maggie Foster, Lydia Munley, and Crystal Ashton located at the address above. If an Offeror elects to hand deliver a response, the Offeror must have prior authorized access to the base facilities. Visit requests will not be granted for response delivery. Without proper access, the Offeror will not gain entry into the installation to deliver its response. NAS Patuxent River Security Guards are not authorized to accept responses. If an Offeror does not have prior authorized access to the base facilities, it shall mail the response.

4.2 Unclassified Proposal Packaging

a) The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible, grouping like volumes to the maximum extent possible. Clearly mark all packages with the solicitation number.

b) The outside and inside of the carton(s), the front cover of the proposal volumes, and the DVD-ROMs should be clearly stamped or marked ― “For Official Use Only”; and “Source Selection Information – See FAR-2.101 and 3.104.”

c) The sets of DVD-ROM disks should be clearly marked with the Offeror's name and address, the point of contact's name and phone number, the proposal volumes contained therein.

d) Each carton should identify its contents by including a packing slip detailing each volume/annex number and title, and copy number. Each carton should be double wrapped. The outside of the carton should be plain and should contain only pertinent shipping /mailing information including the intended recipient identified in 4.1 (Proposal Submission).

5. CHANGES TO SOLICITATION

For any changes and additional information to the solicitation, please go to website: https://www.beta.sam.gov/

PART B SPECIFIC INSTRUCTIONS

The Offeror’s shall use the Section L Attachments listed in Table G-4 to provide information for this solicitation.

1. VOLUME 1 – TECHNICAL

1.1 Offeror Summary Table

The Offeror shall complete Table T-1 (Offeror Summary), provided in Attachment L-1, according to the instructions within the attachment, and submit it within this section. This table summarizes the prime contractor (which includes the JV) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and the JV Members proposed for this solicitation.

1.2 Contract Summary Table

a) Table T-2 (Contract Summary) The Offeror shall complete Table T-2 (Contract Summary) provided in Attachment L-1, for all contract references proposed for 1.3 (Evaluation Elements) for the prime contractor (which includes the JV) and the JV Members identified in T-1 (Offeror Summary). The Offeror shall complete the table according to the instructions within the attachment and submit it within this section. The Offeror may submit no more than three contract references. Please designate the contract references in a sequential order from the most relevant (e.g., P1, P2, P3) to those that meet the requirements. A contract reference is defined as:

1. Contracts of all types except indefinite-delivery contracts (see subpart 16.5) (position 9 of Procurement Instrument Identifier instrument “C” type);

2. An order under a basic ordering agreement (BOA); or

3. A delivery order (DO) or a task order (TO) under a single or multiple award Indefinite-Delivery (ID) contract.

b) For the Technical evaluation, a contract reference will only be considered based on the following:

1. If submitting a contract reference for work performed as a Prime Contractor:

i. The contractor with the CAGE code/DUNS identified on the contract reference is the same as the Offeror (prime contractor) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary);

ii. The contractor with the CAGE code/DUNS identified on the contract reference is a part of the Offeror (prime contractor) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary) as a result of a corporate acquisition, reorganization, merger, or other administrative reason. The Offeror must demonstrate that the organizational entity who performed the work in the contract reference is currently a part of the Offeror identified in (organized in) in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary); or

iii. The JV with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award may submit contract references performed by the individual JV Members identified in Table T-1 (Offeror Summary) if the CAGE code/DUNS identified in Table T-1 (Offeror Summary) is the same as the CAGE code/DUNS identified in the contract reference or the contractor with the CAGE code/DUNS identified on the contract reference became a part of the JV Member identified in Table T-1 (Offeror Summary) as a result of a corporate acquisition, reorganization, merger, or other administrative reason. The Offeror must demonstrate that the organizational entity who performed the work in the contract reference is currently a part of the JV Member identified in (organized in) in Table T-1 (Offeror Summary).

2. If submitting a contract reference for work performed as a Subcontractor:

i. The contractor with the CAGE code/DUNS identified on the signed Attachment L-2 CAME is the same as the Offeror (prime contractor) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary);

ii. The contractor with the CAGE code/DUNS identified on the signed Attachment L-2 CAME is a part of the Offeror (prime contractor) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary) as a result of a corporate acquisition, reorganization, merger, or other administrative reason. The Offeror must demonstrate that the organizational entity who performed the work in the contract reference is currently a part of the Offeror identified in (organized in) in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary); or

iii. The JV with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award may submit contract references performed by the individual JV Members identified in Table T-1 (Offeror Summary) if the CAGE code/DUNS identified in Table T-1 (Offeror Summary) is the same as the CAGE code/DUNS identified on the signed Attachment L-2 CAME or the contractor with the CAGE code/DUNS identified on the contract reference became a part of the JV Member identified in Table T-1 (Offeror Summary) as a result of a corporate acquisition, reorganization, merger, or other administrative reason. The Offeror must demonstrate that the organizational entity who performed the work in the contract reference is currently a part of the JV Member identified in (organized in) in Table T-1 (Offeror Summary).

c) All current CAGE Codes/DUNS should appear in Table T-1 (Offeror Summary). The Offeror shall provide a written explanation if multiple CAGE codes/DUNS are applicable. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason and must demonstrate that the organizational entity who performed the work in the contract reference is currently a part of the Prime (including JV) or JV Member.

d) Additionally, if applicable, the Offeror shall provide documentation identifying the Joint Venture Members and demonstrating the JV is a legal entity.

1.3 Evaluation Elements

a) The Offeror shall propose at least one contract reference and a maximum of three, which meet the 1.3.2 Aircraft Maintenance Experience Requirements; however, the Offeror must meet all requirements of 1.3.2 with one contract reference and may not combine multiple contract references to meet the requirements of 1.3.2. The Offeror may submit contract references under NAICS codes other than 336411, regardless of small business status within those NAICS codes, to meet experience requirements identified in 1.3.2.

b) Offerors shall complete a separate Attachment L-2 CAME, according to the instructions within the attachment, for each contract reference proposed to satisfy the requirements of 1.3.2 (Aircraft Maintenance Experience Requirements) for the principal entities identified in Table T-1 (Offeror Summary). All fields in the template must be completed. No other format will be considered. Only contract references (e.g., P1, P2, P3) designated in Table T-2 (Contract Summary) shall be used in completing Attachment L-2 CAME.

c) For each contract reference submitted in Attachment L-2 CAME the Offeror shall provide copies of supporting documentation in Annex A (Supporting Documentation for Aircraft Maintenance Experience) that clearly demonstrates that the contract reference meets the requirements identified in 1.3.2 (Aircraft Maintenance Experience Requirements).

d) The Offeror shall demonstrate that it meets all criteria listed in 1.3.1 and 1.3.2 below:

1.3.1 Small Business Classification under NAICS 336411

a) Offeror shall provide proof of current small business status under NAICS 336411 in Annex A. Acceptable verification may include a copy of the Small Business Representations (FAR 52.219-1) under NAICS 336411 in the System for Award Management (SAM).

1.3.2 Aircraft Maintenance Experience Requirements (Offeror must demonstrate it meets requirements of 1.3.2 a., b., c., d., and e. within one contract reference, with supporting documentation provided in Annex A)

a) Performed on a U.S. Government contract as a prime or subcontractor.

b) Contract reference shows the same physical location and the same CAGE code/DUNS as the entities identified in Table T-1 (Offeror Summary) unless the Offeror provides an acceptable explanation based on the considerations in Volume 1 (Technical), Section 1.2.2.

c) Performed aircraft maintenance (as defined in the Section J, Attachment 1 PWS) of:

1. Aircraft; or

2. Aircraft systems; or

3. Aircraft subsystems; or

4. Aircraft components; or

5. Aircraft support equipment; or

6. Aircraft engines

d) Performance is within two (2) years of the solicitation release date.

e) Total awarded contract value is equal to or greater than $2M. If contract reference is work performed as a subcontractor, the offeror must demonstrate that the subcontracted value is equal to or greater than $2M.

1.4 Annex A (Supporting Documentation for Aircraft Maintenance Experience)

a) The Offeror must substantiate all information by providing enough evidence within a contract or task order document or other verifiable contractual documents to support each answer. The Offeror may provide any official, verifiable documentation necessary to validate. Supporting contract documentation may include plans (e.g., Monthly Maintenance Plans), documents (e.g., designation, assignment, certification, or appointment), and/or letters delivered to, signed, or accepted by the Government that clearly show that the contract reference, meets the requirements identified in Evaluation Elements 1.3.1 and 1.3.2. A requirement not specifically identified in the SOW/PWS or otherwise demonstrated through documents discussed herein will not be considered.

b) Within Annex A, the Offeror shall highlight in yellow, the portions of the documents that clearly identify that the contract reference meets each of the requirements identified in Evaluation Elements 1.3.1 - 1.3.2; the Offeror shall denote which highlighted areas correspond to each requirement. Additionally, within Attachment L-2 CAME the Offeror shall identify the document name, page numbers, and paragraphs that show the contract reference meets the requirements identified in Evaluation Elements 1.3.1 – 1.3.2.

c) For each Contract Reference, Offerors must provide the following (unless utilizing the alternate written verification described in Section 1.4 d) below):

1. Copy of Contract SOW/PWS - The SOW or PWS, from the contract that describes the general scope, nature, complexity, and purpose of the supplies or services the customer acquired under the contract. Additionally, the Offeror must also identify and call attention to the specific section or sections of the SOW that support the claim of having performed the experience requirements in Attachment L-2 CAME;

2. Federal Procurement Data System – Next Generation (FPDS-NG) - FPDS-NG Report that provides verification of the NAICS for the contract reference (if multiple FPDS-NG reports are available, the most recent report shall be submitted); and

3. Copy of original contract award document, this may include the following:

i. Standard Form (SF) 1449 – Solicitation/Contract/Order for Commercial Items – (Block 17a identifies the Prime Contractor; Block 9 identifies the U.S. Federal

ii. Government Agency, Block 3 identifies the Award/Effective Date, and Block 31c. identifies the date the Contracting Officer signed)

iii. SF 26 – Award/Contract – (Block 7 identifies the Prime Contractor, Block 5 identifies the U.S. Federal Government Agency, Block 3 identifies the Effective date, and Block 20C identifies the date the Contracting Officer signed)

iv. SF 33 – Solicitation, Offer, and Award – (Block 15A identifies the Prime Contractor, Block 7 identifies the U.S. Federal Government Agency, and Block 28 identifies the date the Contracting Officer awarded/signed)

v. Department of Defense (DD) 1155 – Order for Supplies or Services (Block 9 identifies the Prime Contractor, Block 6 identifies the U.S. Federal Government Agency, Block 3 identifies the date of Order, and Block 24 identifies the Contracting Officer signature)

vi. Fully executed subcontract from the prime identified in one of the contract documents outlined above.

d) Alternate written verification may be provided for a contract reference submitted on the Attachment L-2 CAME by obtaining signature on the Attachment L-2 CAME from one of the following individuals. Any contract reference that provides signed verification from one of the individuals listed below does not require additional supporting documentation for those elements. Any individual evaluation element not verified by one of the individuals outlined below shall require official and verifiable supporting documentation.

If submitting a contract reference for work performed as a Prime Contractor:

If submitting a contract reference for work performed as a Subcontractor:

7. VOLUME 2 – CONTRACT ADMINISTRATION

The Offeror shall provide the following contract administration information.

2.1 Offeror Representatives and Information

The Offeror shall provide a summary sheet comprised of the information listed below for the Prime (includes JV) identified in Table T-1 (Offeror Summary).

a) Prime (includes JV)

1. Business Name;

2. Address;

3. Primary point of contact for this solicitation (Name, title, phone number, email);

4. Secondary point of contact for this solicitation (Name, title, phone number, email);

5. Individuals authorized to negotiate with the Government and contractually bind the Offeror (Name, title, phone number, email);

6. DUNS; and

7. CAGE code.

2.2 Government Agency Information

Provide the mailing address, telephone, email address and facility codes for the Offeror’s local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, provide the name, telephone number, and email address for the Administrative Contracting Officer (ACO) at DCMA.

2.3 Terms and Conditions

a) All exceptions and deviations that the Offeror takes from the provisions of the solicitation and its applicable documents shall be included in this section.

b) An exception is where an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions.

c) Non-compliance with the terms, conditions, or requirements set forth in the solicitation may result in an Offeror being considered unawardable. The Government may consider an Offeror ineligible for award who proposes any exception or deviation to any term or condition of the solicitation that is not expressly authorized by the solicitation.

d) The Offeror shall provide one of the following two statements in this section. If the Offeror takes any exceptions or deviations to the provisions of the solicitation and its applicable documents, the Offeror shall provide the following statement: “All exceptions and deviations taken from the solicitation terms, conditions or requirements, including any applicable documents, are included in this section”. If the Offeror does not take any such exceptions or deviations, then the Offeror shall provide the following statement: “No exceptions or deviations are taken to the terms and conditions or any requirement of the solicitation.”

2.4 Model Contract Documents

The Offeror shall provide the model contract documents as a separate electronic file and as a separate section in this volume. In the event there is any discrepancy between these contract documents and any other volume, Volume 2 (Contract Administration) shall take precedence. The Offeror shall provide the following documents within this section:

a. Original signed SF33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation. The SF-33 Block 12 “fill-in” (proposal validity date) shall be completed to read “365” (valid 365 days from proposal due date); and

b. Signed System for Award Management (SAM) reference Section K per Section K.1 a).

(End of Summary of Changes) image1.wmf