W56HZV21R0133-0001.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

0001 2022MAR10

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

CHRISTOPHER R. HAVRILLA

EMAIL: CHRISTOPHER.R.HAVRILLA.CIV@ARMY.MIL

W56HZV-21-R-0133

2022FEB14

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 9

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: CHRISTOPHER R. HAVRILLA

Buyer Office Symbol/Telephone Number: CCTA-AHM-B/(586)282-6377

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

1. The purpose of Amendment 0001 to Solicitation W56HZV-21-R-0133 is to revise section L.4.1.2 language, correct administrative numbering errors, and replace Attachment 0005.

2. Section L.4.1.2 has been revised:

From: L.4.1.2. Page Limit: A 10 page limit applies to part of this Volume submission. The page limit only applies to the written narrative(s) required in L.4.1.6. Any substantiating documents submitted in response to Section L.4.1.6 will not be counted in this page limit (Copy of Contract sections, other substantiating documents in response to L.4.1.6.1.1, L.4.1.6.2.1, or L.4.1.6.3.1, etc).

To: L.4.1.2. Page Limit: A 10 page limit applies to part of this Volume submission. The page limit applies to the table of contents of this volume, the information in L.4.1.6.4 (a) through (f), the written narrative required in L.4.1.6.4(i), and any other applicable written narratives that could be required by L.4.1.6.1.1, L.4.1.6.2.1, or L.4.1.6.3.1. It does not include the requested substantiating information or documents, which can be submitted as a stand-alone document(s), such as the requested data in in L.4.1.6.4

(g) and (h), and any applicable substantiating documents that could be required by L.4.1.6.1.1, L.4.1.6.2.1, or L.4.1.6.3.1, etc).

Offerors are cautioned that the Government will not review any pages beyond 10 pages.

3. Correct administrative numbering errors as follows:

Change L.4.1.4.3.1 to L.4.1.6.3.1, and

Change L.4.1.4.6.2 to L.4.1.6.1.2

4. Attachment 0005 - Small Business Certification Form has been revised.

5. There are no other changes as a result of the amendment. All terms and conditions remain unchanged.

*** END OF NARRATIVE A0003 ***

2 9

W56HZV-21-R-0133

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Attachment 0005 SMALL BUSINESS CERTIFCATION FORM EMAIL

3 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 General Proposal Information

L.1.1 The proposal, subject to the Submission, Modification, Revision, and Withdrawal paragraph (c) 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 set forth below. All information necessary for the review and evaluation of a proposal is to 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. 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 270 calendar days.

L.1.2.2. The offeror shall clearly state in its proposal Terms and Conditions volume 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, or fails to provide a proposal 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). Proposals not in English (American Standard) 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 separate volumes as set forth below. The offerors proposal shall consist of the following volumes:

Volume

Number Title

Volume 1 Technical Experience Factor

Volume 2 Small Business Participation Factor

Volume 3 Terms and Conditions

L.2.1.2 A Proposal Executive Summary or transmittal letter is optional. It will neither be considered as part of the volumes required, nor will it be evaluated. If a Proposal Executive Summary is submitted, it should be no more than five pages in length and be submitted as part of the Terms and Conditions volume.

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

L.2.2.1 Method of Submission:

L.2.2.1.1 The proposal shall be electronically submitted via E-mail to the Contract Specialist, Chris Havrilla, and cc the corresponding Contracting Officer at the following e-mail address(s) with the subject header: Proposal Submission - W56HZV-21-R-0133

(company name):

Contract Specialist: christopher.r.havrilla.civ@army.mil

Contracting Officer: john.m.sarti2.civ@army.mil

Fax, hardcopy, and DVD/CD-ROM proposals will NOT be accepted. Hand-carried offers, whether hardcopy or electronic, will NOT be accepted.

L.2.2.1.2 Maximum size of each e-mail shall be 10 megabytes. The offeror may use multiple e-mail messages for each submission, however, it should annotate the subject lines as described above for each message, and number them in this manner: Message 1 of 3, 2 of 3, 3 of

3.

4 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.2.1.3 There is no "expected" or "target" length of time for proposal submission via email; size and content may be factors, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for submission.

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 for example: Volume 2, Small

Business Participation 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.

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.

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 Due Date and Time for Receipt of

Offers specified in the solicitation.

L.2.2.3.1 Lateness

The lateness rules for submitted proposals are outlined in FAR 52.215-1 and are incorporated into this solicitation.

L.2.3 Single Proposal Submission

Offerors are limited to submitting one proposal with one approach to meeting the requirements of this solicitation. An offeror is defined as an entity competing independently that does not share a common parent with any other offeror or, does not have a parent/subsidiary relationship with any other offeror, or is not affiliated with any other offeror. For this Section L.2.3, the

Government will consider Affiliation to exist if associated business concerns or individuals, directly or indirectly, either controls the other or can control the other (control can exist through common ownership, common management, or a contractual relationship such as a joint venture, where members have the power to control performance of the contract); or a third party controls or can control both.

L.2.4 Organizational Conflict of Interest

L.2.4.1 The provisions of FAR Subpart 9.5, Organizational Conflict of Interest (OCI) apply to any award under this Request for Proposal

(RFP). Potential offerors should review their 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.2.4.2 Offerors shall disclose any potential OCI situations to the Contracting Officer as soon as identified including prior to proposal submission. The disclosure should include the facts and an analysis of the actual or perceived conflict and a recommended approach(s) 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.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

5 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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:

a. Technical Experience

b. Small Business Participation

L.4.1 Volume 1 Technical Experience Factor Proposal

L.4.1.1. General Information: The below instructions are provided to advise offerors as to the information required by the Government to assess the contractors proposed experience. Since this information constitutes a basis of the Government's review, it is the offeror's responsibility to submit detailed and complete information as required so the Government may evaluate its Experience volume, and imperative that the offeror present its experience in a clear and complete manner. Failure to provide the applicable information may result in an assessment that the referenced experience lacks comparability or recency, and be discounted in the evaluation. The

Government does not assume the duty to search for data to cure problems it finds in proposals. The burden of providing thorough and complete information remains with the offeror.

L.4.1.2. Page Limit: A 10 page limit applies to part of this Volume submission. The page limit applies to the table of contents of this volume, the information in L.4.1.6.4 (a) through (f), the written narrative required in L.4.1.6.4(i), and any other applicable written narratives that could be required by L.4.1.6.1.1, L.4.1.6.2.1, or L.4.1.6.3.1. It does not include the requested substantiating information or documents, which can be submitted as a stand-alone document(s), such as the requested data in in L.4.1.6.4 (g) and (h), and any applicable substantiating documents that could be required by L.4.1.6.1.1, L.4.1.6.2.1, or L.4.1.6.3.1, etc). Offerors are cautioned that the Government will not review any pages beyond 10 pages.

L.4.1.3 Definition of Contract for the Experience Factor: 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. Indefinite Delivery

Contracts (FAR Subpart 16.5), Basic Ordering Agreements (BOA), Blanket Purchase Agreements (BPA), and Federal Supply Schedules (FSS) are written instruments that typically DO NOT demonstrate actual performance, and as such, would 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/technical instruction, 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 identified on the Contract itself. It is incumbent upon the offeror to demonstrate that a distinct effort was actually performed.

L.4.1.4 For the Technical Experience Factor, the offeror shall substantiate recent experience by providing the requested information below. The offeror shall provide one recent Contract, as defined in L.4.1.3 above that it believes demonstrates comparability to the criteria set forth in L.4.1.5 below. Recent Contract(s) are those performed within three years of the date of issuance of this Request for Proposal (RFP). The Contract must have been performed by the offeror as the prime USG contractor, unless another entity as allowed by L.4.1.6 below. The Government will not consider the experience of individuals, key personnel, or subcontractors; only corporate experience will be considered.

L.4.1.5 Recent experience is defined as tasks completed on a Contract determined to be recent. Recent experience will be assessed for comparability in scope and complexity against the following criteria:

Contractor delivery of a US Army Class IX repair part(s), excluding consumable items as defined by DoDM 4140.26-V2 that was accepted by the U.S. Government.

NOTE: Provide a contract deliverable that has a USG kit number, USG part number, or an USG NSN. See M.4.1.1.2.1

L.4.1.6 Experience Proposal Information Requested

L.4.1.6.1 Associated Corporate Entities. 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.

L.4.1.6.1.1 An associated entity may include a parent company, separate corporate division within the same parent company, subsidiary company, a legally affiliated company, etc. 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.

L.4.1.6.1.2 The offeror shall provide to the Government a narrative that explains the meaningful involvement the associated entity will provide to the proposed effort. Evidence of 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.

6 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4.1.6.2 Predecessor Companies. 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.

L.4.1.6.2.1 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.

L.4.1.6.2.2 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.6.3 Individual Partners of a Joint Venture. If the offeror is a Joint Venture, the Government may consider the 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.

L.4.1.6.3.1 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.

L.4.1.6.3.2 Offeror shall provide to the Government a narrative that explains the meaningful involvement the Joint Venture partner will provide to the proposed effort. Evidence of 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.1.6.4 Contract Information: Offerors proposal shall substantiate what executed work was performed under the proposed Contract. For the submitted Contract, provide the following information:

(a) Prime Contractor Name and Address;

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

NOTE: If the proposed Contract is an Indefinite Delivery Contracts, BOA, BPA, FSS type contract, then provide a single order (i.e task/delivery order, work directive, technical instruction) as the proposed Contract. See Section L.4.1.3 for definition of a Contract.

(c) Contract Period of performance;

(d) Government contracting activity address, telephone number and e-mail;

(e) Procuring Contracting Officers (PCO), point of contact responsible for signing or administering the contract, telephone number and e-mail;

(f) Point of contact responsible for accepting deliverables under the contract (i.e Government (DCMA) or administrative contracting officer (ACO), contracting officers representative (COR), performance certifier) name, telephone number and email;

(g) Copies of the Contract pages or sections that demonstrate the following: Contract number, date of Contract execution, Identification of the contract parties, Delivery Schedule, Performance Work Statement (PWS) or Scope of Work (SOW), Deliverable Identification of USG kit number, USG Part Number and/or USG National Stock Number (NSN); and the CLIN number associated with of the delivered and accepted end item.

(h) Evidence to substantiate USG acceptance of the deliverable end item. Examples of evidence can include (but are not limited to):

Written Government correspondence (Such as PCO, ACO, COR notification through letter, e-mail), and screen images of Wide Area Workflow acceptance and/or payment of CLIN/SLIN that is attributable to the contract deliverable end item.

(i) The offeror shall provide a written narrative that details the executed work performed on the submitted Contract and its comparability to the criteria listed in Section L.4.1.5. Note: Do not provide a breakdown of comparability of all past Contract requirements to the current RFP requirements, only discuss the comparability the executed work performed to the criteria identified in

L.4.1.5. When citing specific work performed on the submitted Contract or its associated ordering instrument, provide references to the specific locations within the scope or other substantiating documents, such as paragraph or page number, when possible. When applicable, in its description, the offeror should specify the location in the proposal (to include filename or document reference with page and paragraph of the past contract information) that further substantiates comparability if stand-alone attachments are submitted in this volume.

(j) An offeror may submit additional information, such as related contractual instruments that enhance the Governments understanding of

7 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

the contract deliverables and/or work performed if it is not identified on the Contract itself. It is incumbent upon the offeror to substantiate what work was actually performed.

L.4.1.6.5 The Government reserves the right to request clarifying information related to the identification of the contract deliverable in order to assist the Governments evaluation of whether the contract deliverable meets the definition in Section L.4.1.5.

L.4.2 Volume 2: Small Business Participation

L.4.2.1 All Offerors (Large and Small Businesses) shall submit Attachment 003 which identifies a list of one or more small business concern(s) that it commits to providing, to the maximum extent practicable, opportunities for performance under this contract. This applies to potential first tier subcontractors only, except for SB Offerors may meet this requirement using work they perform themselves. Please note small business concern(s) can include the following subcategories of Small Disadvantaged Business, Women-Owned

SB, HUBZone SB, Veteran-Owned SB and Service- Disabled Veteran-Owned SB).

See FAR 2.101 for definitions of small business concern and the other socioeconomic small business concern subcategories: Small

Disadvantaged Business, Women-Owned SB, HUBZone SB, Veteran-Owned SB and Service- Disabled Veteran-Owned SB.

L.4.2.2 Attachment 003 Instructions

CAGE Code: If available, fill out the Contractor and Government Entity (CAGE) Code rom the proposed small businesses record in the

System for Award Management (SAM). If the proposed small businesses is not in SAM, see L.4.2.3 below.

NAICS Code: Assign the North American Industrial Classification System (NAICS) Code that best fits the work the proposed small businesses will potentially perform. SBA size standards and corresponding NAICS codes are provided here:

https://www.sba.gov/document/support--table-size-standards

Socioeconomic Categories: List any Small Business subcategories (Small Disadvantaged Business, Women-Owned SB, HUBZone SB, Veteran-Owned

SB and Service- Disabled Veteran-Owned SB) applicable to the proposed small business.

L.4.2.3 Subcontractor Registration or Certification. Pursuant to FAR Clauses 52.219-8 and 52.219-9 in this solicitation, the Offeror may not require subcontractors to be registered in SAM. For any potential small business subcontractor listed in Attachment 003 that is not registered in SAM, the Offeror shall provide in accordance with 13 CFR 121.411(g), a Small Business Certification Form (Attachment

0005) from that potential subcontractor verifying its small business size and socioeconomic status. This certification shall contain, on the same page as the size and status claimed, the signature of the official authorized to sign for that firm. See M.4.2.2.2

L.5 Volume 3: Terms and Conditions

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

L.5.1 Signature Actions/offeror Fill-Ins. Provide 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. Do Not Fill in Section B of the

RFP, as proposed Cost/Price is not being requested or evaluated for this RFP (See Sec A.4.3). 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.5.1.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.5.1.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.5.2 Offerors proposal acceptance period in terms of calendar days from the date for receipt of offers specified in the RFP. (See

Section L.1.2)

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

RFP. Any exceptions taken to the attachments, exhibits, enclosures, or other solicitation terms, conditions, or documents may be grounds for the Government to reject the proposal from further consideration for award (Reference M.2.1).

L.5.4 Assumptions. The offeror shall consolidate and identify all offeror's generated "assumptions" contained anywhere in the proposal.

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 grounds for the Government to reject the proposal from further consideration for award (Reference

M.2.1).

8 9

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.5 Cost Accounting System. At time of proposal submission, please provide a current status of whether or not the offerors accounting system has adequate financial management and fund tracking procedures to accommodate a cost-reimbursement type contract, which has been verified by DCMA or DCAA. If so, please provide evidence which may be in the form of a letter from either DCMA or DCAA that states that the offeror has an adequate accounting system for these purposes. This is informational-only data, and will not be utilized as part of the responsibility determination for award of a base contract.

*** END OF NARRATIVE L0001 ***

9 9