W56HZV21R0011-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0002 2021JUN10

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

JON KAERCHER

EMAIL: JON.F.KAERCHER.CIV@MAIL.MIL

W56HZV-21-R-0011

2021MAY12

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 8

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: JON KAERCHER

Buyer Office Symbol/Telephone Number: CCTA-HCP-D/(586)282-0328

Type of Contract 1: Firm Fixed Price

Kind of Contract: System Acquisition Contracts

*** End of Narrative A0000 ***

1. Amendment 0002 to solicitation W56HZV-21-R-0011 incorporates Sections L.4.3.2.1 and L.4.3.2.2 which includes additional requirements for proposals submitted by a Joint Venture.

2. As a result of Amendment 0002, the following requirements are hereby incorporated:

L.4.3.2.1: Where certifications and approved systems are required for an offeror, if the proposal is being submitted by a Joint Venture, certifications and approved systems for the principals (partners) of the joint venture will be considered as valid for that offeror providing the necessary documentation from all principals (partners) is provided with the proposal.

L.4.3.2.2 Joint Venture (JV): To be recognized as a JV and eligible for award, the membership arrangements of the JV must be identified and the company relationships fully disclosed in the offeror's proposal IAW FAR 9.603.\~ A copy of the agreement establishing the JV must contain the signatures of all of the members comprising the JV.

3. Except as provided herein, all other items remain unchanged.

*** END OF NARRATIVE A0003 ***

2 8

W56HZV-21-R-0011

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

SPECIAL NOTICE FOR SB SET-ASIDE:

This RFP is a total small business set-aside. Offerors are strongly encouraged to ensure that the offeror is a small business based on the size standard for the NAICS Code assigned to this RFP. Reference 13 CFR Part 121, and the clauses and relevant FAR references contained within this solicitation. Ensure that your firm fits the definition including but not limited to any affiliations (domestic or foreign). The Small Business Administration determines whether an entity qualifies as a small business concern by counting its receipts, employees, or other measures including those of all its domestic and foreign affiliates, regardless of whether the affiliates are organized for profit. 13 C.F.R. 121.103(a)(6). SBA has a specific set of rules that explain when another person, business or entity is considered an affiliate for size standard purposes. SBAs rules on affiliation for its programs (except SBIR and STTR) are found at 13

C.F.R. 121.103.

L.1 General Proposal Information

L.1.1 The proposal, subject to the Submission, Modification, Revision, and Withdrawal paragraph of Instructions to Offeror(s)

Competitive Acquisitions (FAR Provision 52.215-1) contained in Section L of the solicitation, shall be submitted in the format and quantities set forth below. All information necessary for the review and evaluation of a proposal shall be contained in the proposal volumes set forth below. Section M of the solicitation sets forth the evaluation criteria and delineates the Factors to be evaluated and their relative order of importance. The offeror's proposal, as required by this section, will be evaluated as set forth in Section

M of this solicitation. The Government will not assume the offeror possesses any capability, understanding, or commitment not specified in its proposal. It is an offeror's responsibility to submit a well-written proposal, with adequately detailed information, which clearly demonstrates an understanding of and the ability to comply with the solicitation requirements to allow for a meaningful evaluation. The Government does not assume the duty to search for data to cure problems it finds in proposals.

L.1.2 Minimum Acceptance Period.

This provision supersedes any language pertaining to the acceptance period that may appear elsewhere in this solicitation (e.g. SF 33

Box 12).

ACCEPTANCE PERIOD means the number of calendar days available to the Government for awarding a contract from the date specified in this solicitation for receipt of offers.

L.1.2.1 The Government specified minimum acceptance period of is 180 calendar days.

L.1.2.2 The offeror shall clearly state in its proposal Administrative Volume 3 the acceptance period. Offerors may specify a longer acceptance period than the Government's minimum acceptance period stated above.

L.1.2.3 An offer allowing less than the Government's minimum acceptance period may be rejected.

L.2 Proposal Content, Format and Instructions

L.2.1 Proposal Content

L.2.1.1 All proposals shall be in English (American Standard) and shall be in US dollars. Proposals not in English (American Standard) or in US Dollars may be rejected. The proposal shall include all information specified and shall address all requirements outlined in

Section L. The offeror's proposal shall be submitted in the separate volumes and in the quantities as set forth below. The offerors proposal shall consist of the following volumes:

Volume Number Title Qty Page Limit

Volume 1 Experience Factor 1 10

Volume 2 Price Factor 1 None

Volume 3 Administrative 1 None

L.2.1.2 A Proposal Cover Letter. The offeror shall include a cover letter within the Administrative Volume of its proposal. The offeror shall ensure the cover letter identifies all volumes, documents, and enclosures that they intend to submit. The cover letter shall be prepared on the companys letterhead and include a point of contact who can be reached with questions regarding your proposal and should receive all correspondence regarding your companys proposal. The cover letter is required as part of the Administrative

Volume; it will not be evaluated.

Note - Classified information shall NOT be submitted in response to this solicitation. Only unclassified proposal information shall be submitted and will be accepted.

L.2.1.3 Acceptable File Formats. All electronic information provided in response to the solicitation must be provided in Microsoft (MS)

Office 2013 or PDF compatible format or except as noted in instructions for individual volumes.

3 8

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.1.4 Offerors shall not include citations for or linkages to websites in its proposal. The offeror shall exercise extreme care in order to ensure that all required volumes and information are included in its proposal and submitted IAW Section L.2.2

L.2.2 Proposal Method of Submission, Format, and Instructions

L.2.2.1 Method of Submission:

Electronic proposals submitted via E-mail or Fax, and hardcopy proposals will NOT be accepted. Hand-carried offers, whether hardcopy or electronic, will NOT be accepted. Offerors are required to submit proposals electronically, via DoD Secure Access File Exchange (SAFE) in accordance with the following Proposal Submission Instructions and Process. Use of DoD SAFE requires the offerors understanding and consent of DoD SAFEs user behavior guidelines and all terms of use. Offerors with CAC cards shall NOT initiate a DoD SAFE Drop-off directly to the Government POC below, all offerors must request the Government POC below initiate a Request for a Drop-Off, and respond in accordance with the DoD SAFE generated e-mail for a Drop-Off Request.

NOTE: In accordance with FAR 15.208, it is the responsibility of the Offeror to ensure the proposal is received, in its entirety, at the required destination by the Due Date and Time for Receipt of Offers specified in the solicitation, in accordance with the Instructions below. It is the offerors responsibility to request all necessary Drop-Off Requests from the Government in order to submit its proposal in a timely manner.

Proposal Submission Instructions and Process:

Step 1 (Offeror): Offerors shall email Contract Specialist, Jon Kaercher, (email:jon.f.kaercher.civ@mail.mil) of their intent to submit a proposal and request the Government initiate a DoD SAFE Drop-Off Request.

NOTE 1: It is recommended that this request is submitted no sooner than 14 days (Drop Off Requests are only valid for 14 days), and no later than 72 hours, prior to proposal due date and time. Offerors shall contact Jon Kaercher or Contracting Officer, Lynn Byrne, at lynn.m.byrne.civ@mail.mil or (586) 282-6880 if they dont receive a SAFE email link by the next business day after submittal.

NOTE 2: Unless otherwise specified in its request, the Government will only initiate one Drop-Off Request. The current file limit for

Drop Off is 25 files. If the offeror intends to submit more than 25 files, it is the offerors responsibility to inform the Government of the number of Drop-Off Requests it needs to submit its complete proposal.

NOTE 3: Unless otherwise specified in the request, the Government will use the senders e-mail address to initiate the DoD SAFE Drop-off

Request (See Step 2). The Government will input a single email address when initiating a Request For Drop-Off.

Step 2 (Government): The Government will initiate a Request For Drop-Off via the DoD SAFE website.

Step 3 (Offeror): DoD SAFE will generate an email to the email address input by the Government (See Step 1, NOTE 3). This email will contain a link.

Step 4 (Offeror): The offeror utilizes the link in the DoD SAFE generated email, and submits its proposal by uploading its proposal files and clicking Drop-off File. Proposal submission does not occur until the Drop-off File occurs.

NOTE 4: The DoD SAFE Request for Drop-Off link will no longer be active after the Drop-off File submission has occurred.

NOTE 5: Please note that when submitting through DoD SAFE, it will take time to upload the proposal submission; size and content may be factors, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for upload.

NOTE 6: Offerors should not upload any files until it is prepared to Submit its DropOff to the Government.

NOTE 7: It is highly recommended that the offeror print Drop Off Completed screen and email a copy to Jon Kaercher

(email:jon.f.kaercher.civ@mail.mil)

Step 5(Offeror): If the offeror needs to update its submission prior to the RFP closing date and needs the Government to initiate a new

DoD SAFE Drop-Off Request, it shall follow the same steps outlined above.

L.2.2.2 Proposal Format and Instructions

L.2.2.2.1 Each submitted File shall be labeled and named so it is identifiable for which volume it pertains (example: Volume 2, Price

Factor)

L.2.2.2.2 Electronic Files. The proposal electronic file name should not exceed 50 characters in length (not including the file extension). Ensure the file name does not contain any periods.

4 8

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.2.2.3 Acceptable File Formats. All electronic information provided in response to the solicitation must be provided in Microsoft

(MS) Office 2013 compatible or Adobe Portable Document Format (PDF) format or except as noted in instructions for individual volumes.

For files in PDF format, scanners should be set to 200 dots per inch. The proposal shall not contain citations for, or active links to live Internet sites or pages. All linked information shall be contained within the electronic proposal. Any linked information that is not contained in the proposal will not be accepted.

L.2.2.2.4 Unless otherwise specified, it is recommended that the proposal be formatted for 8.5 inch x 11 inch paper with a minimum font size of 10 pt. and with a minimum of 0.5 margins. Schedules, drawings and other documents more appropriate to larger size should be formatted for no larger than 8.5 inch x 14 inch dimensions.

L.2.2.2.5 Provide spreadsheets that include all formulas, function, macros, computations, or equations used to compute the proposed amounts. For each workbook, all Rows, Columns, Cells, and Worksheets are to be visible. Do not include Zero height and zero width rows and columns in Worksheets. Do not format Worksheet cells with font color equal to the fill color. If Workbooks or Worksheets are password protected, then the passwords must be provided. Do not submit print image files or pictures or files containing only values are not acceptable. Failure to provide fully functional excel spreadsheets in the proposal may result in the proposal being rejected (See

Section M.2.1(a)).

L.2.2.2.6 The offeror shall make every effort to ensure that the proposal is virus-free. Proposals (or portions thereof) submitted which indicate the presence of a virus, or which are otherwise rendered unreadable by damage in electronic transit, shall be treated as

"unreadable" as described in FAR 15.207(c).

L.2.2.3 Submission Due Date

The offeror must ensure its proposal, in its entirety, reaches the required destination before the Offeror Due Date and Time established in this solicitation.

L.2.2.3.1 Lateness

The lateness rules for submitted proposals are outlined in FAR 52.215-1 "Instructions to Offerors Competitive Acquisition," and are incorporated into this solicitation.

L.3 All or None

Offers in response to this solicitation must be submitted for all the requirements identified in the solicitation. Offers submitted for less than all the requirements called for by this solicitation may be rejected or ineligible for award. Proposals that contain alternative terms and conditions may be considered as taking exception to the requirements of the solicitation. See Section M.2.

L.4 Evaluation Factors

Offeror proposals shall address the following Factors:

Volume 1 Experience Factor

Volume 2 Price Factor

Volume 3 Administrative

L.4.1 Volume 1 Experience Factor

For the Experience Factor, provide information for a total of up to 2 (two) Recent Contracts performed by the offeror as the prime contractor. These may include foreign, federal, state, local and private industry contracts. The burden of providing thorough and complete experience information remains with the offeror. It is the offeror's responsibility to submit detailed and complete information so the Government may evaluate its Experience volume. The Government does not assume the duty to search for data to cure problems it finds in proposals. While the Government may elect to consider data obtained from internal and external sources other than the proposal, the burden to provide thorough and complete experience information rests with the offeror. The below instructions are provided to advise offerors as to the information required by the Government to assess the contractors Recent experience. Since this information constitutes a basis of the Government's review, it is imperative that the offeror present its experience in a clear and complete manner. Failure to provide the information requested under paragraph L.4.1.3 and L.4.1.4 (if applicable) below may result in an assessment that the offeror does not possess a record of Recent and comparable experience.

For the purpose of this Factor, a Contract is defined as a written instrument that requires the performance of a distinct effort and demonstrates the distinct effort was actually performed. Written instruments containing supplies or services that can be ordered but typically do not demonstrate actual performance, such as Indefinite Delivery Contracts (FAR 16.5), Basic Ordering Agreements (BOA), Blanket Purchase Agreements (BPA), and Federal Supply Schedules (FSS) do not meet the definition of a Contract. Written instruments considered to demonstrate actual performance may include a single task or delivery order, a single work directive, or a single definite quantity contract provided it demonstrates a distinct effort was actually performed. An offeror may submit, or the Government may require, written instruments that enhance the Governments understanding of the distinct effort actually performed if it is not

5 8

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

identified on the Contract itself. It is incumbent upon the offeror to demonstrate that a distinct effort was actually performed.

L.4.1.1 The Government will only consider recent experience. Recent experience is defined as tasks completed on a Contract determined to be recent. Recent Contract(s) are those performed within three years of the date of issuance of this Request for Proposal (RFP).

L.4.1.2 The Government will evaluate the extent to which the proposed recent experience is comparable to the following statement of work activities identified below: The contractor shall submit up to 2 (two) recent contracts for the experience factor. The experience factor includes any of following considerations:

(a) Manufactured or integrated an end item to a Government Product Level Technical Data Package (TDP) and MIL-STD-31000

(b) Manufactured or integrated a fluid distribution system to either a TDP or other (e.g. commercial) technical documentation

(c) Manufactured or integrated a major component of a fluid distribution system to either a TDP or other (e.g. commercial) technical documentation.

L.4.1.3 Contract Information: Refer to the definition of a Contract above (L.4.1). The offerors proposal shall substantiate what distinct effort was required and actually performed under each of the proposed Contract(s). For each Contract(s) submitted note which experience factor in L.4.1.2 is being substantiated. Offerors may utilize a single contract for multiple factors but not more than one contract for each factor shall be provided. Additionally contractors are required to provide the following information:

L.4.1.3.1

(a) Prime Contractor name and address;

(b) Contract Number (and delivery/task order number if applicable);

(c) Contract Type;

(d) Total Value of the Contract (beginning & ending value);

(e) Delivery or Performance Schedule;

(f) Government or private industry contracting activity address, telephone number and e-mail;

(g) Procuring Contracting Officers (PCO) and/or Contract Specialists name, or point of contact for private industry entity responsible for signing or administering the Contract, telephone number and e-mail;

(h) Government (DCMA) or private industry administrative contracting officer (ACO), contracting officers representative (COR), performance certifier, and/or quality assurance representative (QAR), name, telephone number and email;

(i) A description of the work performed by the offeror, which shall include a narrative describing the similarities between (1) the comparable work performed under the statement of work requirements of the offerors cited Contract(s) and (2) the experience factor requirements identified in L.4.1.2. In its narrative, the offeror shall specify the location in the cited Contracts statement of work

(to include paragraph and page number) that substantiates the comparability of work performed;

(j) Contract period of performance;

(k) Copy of the Performance Work Statement or Scope of Work or equivalent portion of a commercial contract that described the work that was performed for each of the submitted Contracts. If the proposed Contract was issued under or in connection with a related written instrument (e.g. Indefinite Delivery Contracts, BOA, BPA, FSS) and the details of the distinct effort actually performed needed to establish comparability on the proposed Contract are further defined within the terms and conditions (e.g. statement of work for an end item whereby the specifications were to a Government TDP that conforms to MIL-STD-31000) of that related written instrument, provide that information and any other information necessary to establish this instruments relationship to the proposed Contract. (These documents can be submitted as stand-alone attachments within the proposal volume).

L.4.1.4 Associated Entity, Predecessor Company, and Joint Venture. As stated above (L.4.1), only Contracts performed by the named offeror will be considered;, however, the Government may consider the experience of an associated entity, a predecessor company, or joint venture as explained below.

L.4.1.4.1 Associated Entity. The Government may consider the experience of an associated entity if the offeror successfully demonstrates meaningful involvement by the associated entity in the proposed effort.

a) An example of an associated entity may include a parent company, separate corporate division within the same parent company, subsidiary company, a legally affiliated company. The offeror shall provide to the Government a narrative that explains the offerors relationship to the associated entity. The offeror shall support the narrative with legal documentation, including but not limited to corporate papers, establishing the legal nexus between the offeror and the associated entity.

b) The offeror shall provide to the Government a narrative that explains the meaningful involvement the associated entity will provide to the proposed effort i.e. the work to be performed by the associated entity. Meaningful involvement may include a description of the associated entitys resources, such as its workforce, facilities, and/or other resources that will be provided or relied upon in the proposed effort. A Contract will not be considered unless the offeror successfully establishes meaningful involvement by the associated entity in the proposed effort.

L.4.1.4.2 Predecessor Company. The Government may consider the experience of a predecessor company if the offeror demonstrates the experience of the predecessor company is reasonably predictive of the offerors performance under the proposed effort.

6 8

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

a) A predecessor company may include a company which was acquired by the offeror or merged with the offeror. It may also include other instances where the predecessor company was reorganized, restructured, or otherwise altered. A predecessor company does not include an entity which remains separate and distinct from the offeror. The offeror shall provide to the Government a narrative that explains the offerors relationship to the predecessor company. The offeror shall support the narrative with documentation evidencing the offerors status as the successor company.

b) The offeror shall provide to the Government a narrative that explains why the predecessors experience is predictive of the offerors performance under the proposed effort. Evidence may include, but is not limited to, continuity of operations such as the continued employment of the predecessors employees and the transfer of assets including buildings, furnishings, and fixtures.

L.4.1.4.3 Individual Partners of a Joint Venture. If the offeror is a Joint Venture, the Government may consider experience of each partner of the Joint Venture and any work performed by the Joint Venture itself previously. The offeror must successfully demonstrate meaningful involvement by the partner to the proposed effort.

a) The offeror shall provide to the Government a narrative that discloses the individual partners of the Joint Venture and shall provide documentation evidencing the Joint Venture.

b) The offeror shall provide to the Government a narrative that explains the meaningful involvement the Joint Venture partner will provide to the proposed effort. Meaningful involvement may include a description of the partners resources, such as its workforce, facilities, and/or other resources that will be provided or relied upon in the proposed effort. A Contract will not be considered unless the offeror successfully establishes meaningful involvement by the partner in the proposed effort.

L.4.2 Price Volume

In accordance with FAR 15.403-5(a)(1), certified cost or pricing data is not required for initial proposal submission. However, after initial proposal submission, if only one offer is received, the Government reserves the right to request certified cost or pricing data in accordance with DFARS 252.215-7008. In the event certified cost or pricing data is required, the offeror may submit a written request for exception based on the applicable clauses contained herein.

For initial proposal submission, provide the data other than certified cost or pricing data outlined below. Offerors may submit any other additional cost, price, and financial information it considers to be helpful in the Government's evaluation of its proposal.

L.4.2.1 Provide all prices and costs in U.S. dollars only.

L.4.2.2 Attachment 0040 Pricing Workbook:

Submit your completed Attachment 0040 - Pricing Workbook with your proposal. Complete the attachment in accordance with the instructions included within the attachment. Submit the attachment in Microsoft Excel format. Do not enter any proposed prices into

Section B of the RFP.

L.4.2.3 The Government reserves the right to request additional or more detailed cost or price information to support its evaluation.

L.4.2.4 Use of Existing Government-Furnished Property:

L.4.2.4.1 If the offeror is proposing to utilize Government-Furnished Property (GFP) that it received from another contract, on a rent-free basis in performance of this contract, then the offeror must provide a list of GFP that includes the following for each item:

- Acquisition cost;

- Age;

- Type of GFP;

- The accountable contract under which the property is held;

- The dates during which the property will be available for use (including the first, last, and all intervening months) and, for any property that will be used concurrently in performing two or more contracts, the amounts of the respective uses in sufficient detail to support prorating the rent;

- The amount of rent that would otherwise be charged in accordance with FAR 52.245-9, Use and Charges;

- Evidence that it obtained authorization for its rent-free use from the contracting officer having cognizance of the property; and

- Any additional information required in accordance with Attachment 0041 Use of Existing Government-Furnished Property.

L.4.2.4.2 The offeror is to obtain any rental equivalent amounts (or any other data required) from the cognizant contracting officer necessary to determine the GFP Price Adjustment calculated in accordance with Attachment 0041 Use of Existing Government-Furnished

Property.

L.4.2.4.3 The offeror shall identify the total GFP Price Adjustment (for all classifications of property) that it calculated in accordance with Attachment 0041 Use of Existing Government-Furnished Property, and provide all calculations showing how the total GFP

Price Adjustment was developed. If applicable, the offeror is to also identify the rationale for any allocations to each CLIN.

7 8

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4.3 Volume 3 - Administrative.

In addition to the evaluation factor volumes above, provide the following information:

L.4.3.1 The offeror shall include the cover letter described in L.2.1.2.

L.4.3.2 Signature Actions/offeror Fill-Ins. A scanned image of a signed copy of the SF33 cover page, a copy of all completed fill-ins for Sections A through K, and (if applicable) a signed copy of all Amendments to the solicitation. System for Award Management (SAM) certifications need not be separately submitted; however, all offerors must be successfully registered and valid in SAM prior to award.

L.4.3.2.1: Where certifications and approved systems are required for an offeror, if the proposal is being submitted by a Joint Venture, certifications and approved systems for the principals (partners) of the joint venture will be considered as valid for that offeror providing the necessary documentation from all principals (partners) is provided with the proposal.

L.4.3.2.2 Joint Venture (JV): To be recognized as a JV and eligible for award, the membership arrangements of the JV must be identified and the company relationships fully disclosed in the offeror's proposal IAW FAR 9.603. A copy of the agreement establishing the JV must contain the signatures of all of the members comprising the JV.

L.4.3.3 Minimum Acceptance Period.

L.4.3.1 The offeror shall clearly state its acceptance period. Offerors may specify a longer acceptance period than the Government's minimum acceptance period of 180 days as indicated in L.1.2.1.

L.4.3.4 Statement of Acknowledgement. A statement specifying the extent of agreement with all terms, conditions, and provisions of the

RFP, and a statement of agreement to furnish and deliver the items or perform services set forth in the RFP in consideration for offerors proposed price(s) set opposite each item. Any exceptions taken to the attachments, exhibits, enclosures, or other solicitation terms, conditions, or documents may be determined to be a Deficiency or grounds for the Contracting Officer to reject the proposal from further consideration in the source selection process.

L.4.3.5 Assumptions. The offeror shall consolidate and identify all offeror's generated "assumptions" contained anywhere in the proposal. Also, the offeror shall include a statement that none of the "assumptions" contradict or take exception to any terms, conditions, or requirements of the solicitation. Any exceptions taken to the attachments, exhibits, enclosures, or other solicitation terms, conditions, or documents may be determined to be a Deficiency or grounds for the Contracting Officer to reject the proposal from further consideration in the source selection process (Reference M.2.1).

L.4.3.6 Assertion of Restrictions. The offeror shall include in its proposal submission, each of the following: Non-Commercial

Technical Data, Non-Commercial Computer Software and Software Documentation, Commercial Technical Data, and Commercial Computer Software and Software Documentation and on its Assertion of Restrictions listing required under DFARS 252.227-7017, dated and signed by an official authorized to contractually obligate the offeror. The offerors assertions list will be incorporated into the contract at time of award.

L.4.3.7 Organizational Conflict of Interest

L.4.3.7.1 The provisions of FAR Subpart 9.5, Organizational Conflict of Interest (OCI), applies to any award under this solicitation.

Potential offerors should review current and planned participation in any other Government contracts, subcontracts, consulting, or teaming arrangements where they may be in a position of actual or perceived bias or unfair competitive advantage.

L.4.3.7.2 Offerors shall disclose any potential OCI situations to the Contracting Officer as soon as identified including prior to proposal submission. The disclosure shall include the facts and an analysis of the actual or perceived conflict and recommend approach(es) to neutralize or mitigate the potential conflict. The preferred approach to potential conflicts is to negate/obviate the conflict. Mitigation is considered only if it is not practical to negate/obviate the conflict. The Contracting Officer will promptly respond to resolve any potential conflicts.

L.4.3.7.3 Offerors shall provide an affirmative statement that the offeror does not have an Organizational Conflict of Interest as it applies to this solicitation.

*** END OF NARRATIVE L0001 ***

8 8