signed-amendment-SPRDL117R0474-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 2017DEC27

SPRDL1

DLA LAND WARREN

WARREN, MI 48397-5000

KIMBERLY POHL

EMAIL: KIMBERLY.D.POHL.CIV@MAIL.MIL

SPRDL1-17-R-0474

2017DEC22

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 7

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: KIMBERLY POHL

Buyer Office Symbol/Telephone Number: ZGB/(586)282-3190

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

1. This modification is issued to definitize the following changes:

2. CDRL 1423 as Exhibit A and NDA (non-disclosure agreement)as an attachment are added to this solicitation as follows:

CONTRACT DATA REQUIREMENTS LIST

DD FORM 1423 (MECHANIZED)

CATEGORY: MISC

SYSTEM/ITEM: ADAPTER, PINTLE: UNIVERSAL

TO CONTRACT/PR: EH7C1016EH

NSN: 1010-01-445-6143

1. \*.SEQUENCE NUMBER

2. TITLE OF DATA ITEM

3. SUBTITLE

4. DATA ITEM NUMBER

5. CONTRACT REFERENCE

6. TECHNICAL OFFICE

7. DD 250

8. APP CODE

9. DIST STATEMENT REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF 1ST SUBMISSION

13. DATE OF SUBSEQUENT SUBMISSION

14. DRFT/REG/REPRO/DISTRIBUTION/COPIES

1. A001

2. ENGINEERING CHANGE PROPOSAL (ECP)

3. N/A

4. DI-SESS-80639

5. SECTION C

6. RDAR-EIS-PD

7. LT

8. N/A

9. SEE BLOCK 16

10. ASREQ

11. N/A

12. ASREQ

13. ASREQ

14. SEE BLOCK 16

15. TOTAL 0 / 2 / 0

16. REMARKS

DATA MUST BE IN GOVERNMENT COMPATIBLE SOFTWARE (e.g., MICROSOFT OFFICE OR

PORTABLE DOCUMENT FORMAT (pdf)). *DISTRIBUTION STATEMENT WILL BE ASSIGNED

AND IMPLEMENTED BY THE DOD CONFIGURATION MANAGER. **SUBMIT ELECTRONICALLY TO

"mailto:usarmy.pica.rdecom-ardec.mbx.ecp-document@mail.mil" AND TO THE GOVERNMENT _

CONTRACT SPECIALIST. ELECTRONIC FILES SHALL BE LESS THAN 7MB. THE PREFERRED

METHOD IS THE DD FORM 1692 WHICH IS LOCATED AT

http://www.dtic.mil/whs/directives/infomgt/forms/ . CONTRACTOR FORMAT

ALTERNATIVE TO THE DD FORM IS ACCEPTABLE PROVIDED THE NECESSARY DATA

ELEMENTS ARE PROVIDED.

1. A002

2. REQUEST FOR VARIANCE (RFV)

2 7

SPRDL1-17-R-0474 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

3. N/A

4. DI-SESS-80640

5. SECTION C

6. RDAR-EIS-PD

7. LT

8. N/A

9. SEE BLOCK 16

10. ASREQ

11. N/A

12. ASREQ

13. ASREQ

14. SEE BLOCK 16

15. TOTAL 0 / 2 / 0

16. REMARKS

DATA MUST BE IN GOVERNMENT COMPATIBLE SOFTWARE (e.g., MICROSOFT OFFICE OR

PORTABLE DOCUMENT FORMAT (pdf)). *DISTRIBUTION STATEMENT WILL BE ASSIGNED

AND IMPLEMENTED BY THE DOD CONFIGURATION MANAGER. **SUBMIT ELECTRONICALLY TO

"mailto:usarmy.pica.rdecom-ardec.mbx.ecp-document@mail.mil" AND TO THE GOVERNMENT _

CONTRACT SPECIALIST. ELECTRONIC FILES SHALL BE LESS THAN 7MB. THE PREFERRED

METHOD IS THE DD FORM 1692 WHICH IS LOCATED AT

http://www.dtic.mil/whs/directives/infomgt/forms/ . CONTRACTOR FORMAT

ALTERNATIVE TO THE DD FORM IS ACCEPTABLE PROVIDED THE NECESSARY DATA

ELEMENTS ARE PROVIDED.

1. A003

2. NOTICE OF REVISION (NOR)

3. N/A

4. DI-SESS-80642

5. SECTION C

6. RDAR-EIS-PD

7. LT

8. N/A

9. SEE BLOCK 16

10. ASREQ

11. N/A

12. ASREQ

13. ASREQ

14. SEE BLOCK 16

15. TOTAL 0 / 2 / 0

16. REMARKS

DATA MUST BE IN GOVERNMENT COMPATIBLE SOFTWARE (e.g., MICROSOFT OFFICE OR

PORTABLE DOCUMENT FORMAT (pdf)). *DISTRIBUTION STATEMENT WILL BE ASSIGNED

AND IMPLEMENTED BY THE DOD CONFIGURATION MANAGER. **SUBMIT ELECTRONICALLY TO

"mailto:usarmy.pica.rdecom-ardec.mbx.ecp-document@mail.mil" AND TO THE GOVERNMENT _

CONTRACT SPECIALIST. ELECTRONIC FILES SHALL BE LESS THAN 7MB. THE PREFERRED

METHOD IS THE DD FORM 1692 WHICH IS LOCATED AT

http://www.dtic.mil/whs/directives/infomgt/forms/ . CONTRACTOR FORMAT

ALTERNATIVE TO THE DD FORM IS ACCEPTABLE PROVIDED THE NECESSARY DATA

ELEMENTS ARE PROVIDED.

1. A004

2. SPECIAL INSPECTION EQUIPMENT DESCRIPTIVE DOCUMENTATION

3. ACCEPTANCE INSPECTION EQUIPMENT (AIE) DOCUMENTATION ACCEPTANCE

4. DI-QCIC-81006

5. SECTION E

6. RDAR-EIQ-P

7. XX

8. A

9. A

10. ASREQ

11.

12. ASREQ*

13. ASREQ**

14. THRU QAR 0/1/0 PCO (LT ONLY) 0/1/0 RDAR-QEW 0/1/0 RDAR-EIQ-P 0/1/0

15. TOTAL 0/4/0

3 7

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

16. REMARKS

DD FORM 250 IS NOT REQUIRED.

BOX 12: SUFFICIENTLY PRIOR TO INITIATION OF PRODUCTION OR FIRST ARTICLE

TEST, IF CONTRACTUALLY REQUIRED (SEE NOTE 1).

BOX 13: WHENEVER ANY REVISION THERETO IS NEEDED FOR ANY REASON.

NOTE 1: THE GOVT WILL FURNISH DISPOSITION WITHIN 45 DAYS AFTER RECEIPT.

ELECTRONIC SUBMISSION:

1) ENGINEERING: USARMY.PICA.ARDEC.MBX.QESA-QEW-AIE@MAIL.MIL

2) QA: USARMY.RIA.ARDEC.MBX.RDAR-QEP2@MAIL.MIL

NOTE 2: MICROSOFT OFFICE 97 DRAWINGS: AUTOCAD-RELEASE 14 (EXPRESS MAILED

HARD COPIES WILL BE ACCEPTED) FILES MAY BE COMPRESSED USING ZIP PROGRAM.

WARNING: LARGE PACKAGES MAY CAUSE DELAYS IN DELIVERY USING M

USING MAIL INTERNET.

EMAIL SUBJECT LINE MUST CONTAIN END ITEM NOMENCLATURE.

1. A005

2. TEST PROCEDURE-PHOSPHATE COATING

3. PRE-PRODUCTION PROCEDURE

4. DI-NDTI-80603

5. TT-C-490, TYPE 1, PARAS 3.2.1, 3.2.2

6. RDAR-MEE-W(R)

7. XX

8. A

9. N/A

10. ONE/R

11. N/A

12. 60DAC

13. N/A

14. THRU CONTRACTING OFFICER / / *RDAR-MEE-W / 1 /

15. TOTAL 0 / 1 / 0

16. REMARKS

BLOCK 8 CONT.- PRIOR TO PRODUCTION APPROVAL THRU THE CONTRACTING OFFICER IS

REQUIRED W/IN 60 DAYS AFTER CONTRACT AWARD. *RDAR-MEE-W(R), EMAIL:

"mailto:usarmy.ria.ardec.mbx.ri-corrosion-team@mail.mil" , SHALL PROVIDE PROCEDURE REVIEW RESPONSE BACK TO CONTRACTING OFFICER.

COATED PANELS PER PARA 3.2.2 SHALL INCLUDE THREE WITH PHOSPHATE ONLY, THREE WITH PHOSPHATE AND PRIMER, AND THREE WITH PHOSPHATE, PRIMER AND TOP COAT. A DD FORM 250 IS NOT REQUIRED FOR PHOSPHATE COATING PROCEDURAL APPROVAL. CONTRACTOR FORMAT ACCEPTABLE.

WRITTEN PROCEDURES SHALL BE SUBMITTED USING A PC COMPATIBLE FORMAT (I.E. PDF, RICH TEXT FORMAT (RTF), OR WORD).

1. A006

2. TEST PROCEDURE - PHOSPHATE COATING

3. PRE-PRODUCTION PROCEDURE

4. DI-NDTI-80603A

5. MIL-DTL-16232G, PARA 3.1

6. RDAR-MEE-W(R)

7. XX

8. A

9. N/A

10. ONE/R

11. N/A

12. 60DAC

13. N/A

14. THRU CONTRACTING OFFICER / / *RDAR-MEE-W / 1 /

15. TOTAL 0 / 1 / 0

16. REMARKS

BLOCK 8 CONT.- PRIOR TO PRODUCTION APPROVAL THRU THE CONTRACTING OFFICER IS

REQUIRED W/IN 60 DAYS AFTER CONTRACT AWARD. *RDAR-MEE-W(R), EMAIL:

"mailto:usarmy.ria.ardec.mbx.ri-corrosion-team@mail.mil" , SHALL PROVIDE PROCEDURE REVIEW RESPONSE BACK TO CONTRACTING OFFICER. A

DD FORM 250 IS NOT REQUIRED FOR PHOSPHATE COATING PROCEDURE APPROVAL. CONTRACTOR FORMAT ACCEPTABLE. WRITTEN PROCEDURES SHALL BE

SUBMITTED USING A PC COMPATIBLE FORMAT (I.E. PDF, RICH TEXT FORMAT (RTF), OR WORD).

1. A007

2. REPORT, RECORD OF MEETING/MINUTES

3. START OF WORK MEETING MINUTES

4. DI-ADMN-81505

4 7

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

5. SECTION C/SOW

6. RDAR-EIQ-P

7. XX

8. A*

9.

10. ASREQ*

11. N/A

12. ASREQ*

13. N/A

14. QAR 0 / 1 / 0 PCO 0 / 1 / 0 RDAR-EIQ-P 0 / 1 / 0

15. TOTAL 0 / 3 / 0

16. REMARKS

Block 4: CONTRACTOR FORMAT IS ACCEPTABLE.

BOX 5: CONTRACT REFERENCE. THE CONTRACTOR SHALL PROVIDE TO THE PROCURING

CONTRACTING OFFICER, QAR, AND RDAR-EIQ-P AT LEAST 7 CALENDAR DAYS ADVANCE

NOTICE (IN WRITING) OF THE SCHEDULED DATE, TIME AND LOCATION OF START OF

MEETING, SO THAT THE GOVERNMENT MAY ATTEND.

BLOCK 12: MEETING SHALL BE HELD WITHIN 30 DAYS OF CONTRACT AWARD.

MEETING MINUTES SHALL BE COMPLETED AND FORWARDED TO QAR, PCO, AND QUALITY

ASSURANCE WITHIN 7 CALENDAR DAYS AFTER MEETING. MEETING MINUTES SHALL BE

SENT ELECTRONICALLY TO QUALITY ASSURANCE:

"mailto:USARMY.RIA.ARDEC.MBX.RDAR-QEP2@MAIL.MIL" -----------------

1. A008

2. TEST/INSPECTION REPORT

3. FIRST ARTICLE TEST REPORT (FATR)CONTRACTOR FACILITY

4. DI-NDTI-80809B

5. SECTION E

6. RDAR-EIQ-P

7. XX

8. A*

9.

10. ASREQ

11. N/A

12. ASREQ

13. ASREQ

14. THRU QAR 0 / 1 / 0 PCO 0 /1 / 0 RDAR-EIQ-P O / 1 / 0

15. TOTAL 0 / 3 / 0

16. REMARKS

REQUIRED BY THE AUTHORITY IN BOX 4, PARA 10.2 AND ITS SUBPARAGRAPHS.

CONTRACTOR FORMAT IS ACCEPTABLE.

BOX 5: CONTRACT REFERENCE. THE CONTRACTOR SHALL PROVIDE TO THE PROCURING

CONTRACTING OFFICER, QAR, AND RDAR-EIQ-P AT LEAST 15 CALENDAR DAYS ADVANCE

NOTICE (IN WRITING) OF THE SCHEDULED DATE, TIME AND LOCATION OF START OF

FAT, SO THAT THE GOVERNMENT MAY WITNESS THE TESTS. THE GOVERNMENT WILL

REVIEW THE FATR AND PROVIDE FEEDBACK TO THE CONTRACTOR WITHIN 30 DAYS OF

RECEIPT OF FATR.

BLOCK 13: SUBSEQUENT SUBMISSION ONLY IF INITIAL FAT FAILS.

BLOCK 16: FATR MAY BE SUBMITTED ELECTRONICALLY THROUGH THE QAR, CONTRACTING

OFFICER, AND QUALITY ASSURANCE. QUALITY ASSURANCE ELECTRONIC SUBMISSION:

USARMY.RIA.ARDEC.MBX.RDAR-QEP2@MAIL.MIL ---------------------------

DATE: 14 June 2017

5 7

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Use and Non-Disclosure Agreement

For Government Technical Data

The undersigned, ______________________, an authorized representative of the _______________________, (which is hereinafter referred to as the "Recipient") requests the Government to provide the Recipient with technical data or computer software (hereinafter referred to as "Data") in which the Government's use, modification, reproduction, release, performance, display or disclosure rights are restricted.

Those Data are identified in an attachment to this Agreement. In consideration for receiving such Data, the Recipient agrees to use the Data strictly in accordance with this Agreement:

(1) The Recipient shall-

(a) Use, modify, reproduce, release, perform, display, or disclose Data marked with government purpose rights or SBIR data rights legends only for government purposes and shall not do so for any commercial purpose. The Recipient shall not release, perform, display, or disclose these Data, without the express written permission of the contractor whose name appears in the restrictive legend (the "Contractor"), to any person other than its subcontractors or suppliers, or prospective subcontractors or suppliers, who require these Data to submit offers for, or perform, contracts with the

Recipient. The Recipient shall require its subcontractors or suppliers, or prospective subcontractors or suppliers, to sign a use and non-disclosure agreement prior to disclosing or releasing these Data to such persons. Such agreement must be consistent with the terms of this agreement.

(b) Use, modify, reproduce, release, perform, display, or disclose technical data marked with limited rights legends only as specified in the attachment to this Agreement. Release, performance, display, or disclosure to other persons is not authorized unless specified in the attachment to this Agreement or expressly permitted in writing by the Contractor. The Recipient shall promptly notify the Contractor of the execution of this Agreement and identify the

Contractor's Data that has been or will be provided to the Recipient, the date and place the Data were or will be received, and the name and address of the Government office that has provided or will provide the Data.

(c) Use computer software marked with restricted rights legends only in performance of Solicitation Number _________________. The recipient shall not, for example, enhance, decompile, disassemble, or reverse engineer the software; time share, or use a computer program with more than one computer at a time. The recipient may not release, perform, display, or disclose such software to others unless expressly permitted in writing by the licensor whose name appears in the restrictive legend. The Recipient shall promptly notify the software licensor of the execution of this

Agreement and identify the software that has been or will be provided to the Recipient, the date and place the software were or will be received, and the name and address of the Government office that has provided or will provide the software.

6 7

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(d) Use, modify, reproduce, release, perform, display, or disclose Data marked with special license rights legends

(To be completed by the contracting officer. See "http://www.acq.osd.mil/dp/dars/dfars/html/r20030821/227_71.htm#227.7103-7"(a)(2).

Omit if none of the Data requested is marked with special license rights legends).

(2) The Recipient agrees to adopt or establish operating procedures and physical security measures designed to protect these Data from inadvertent release or disclosure to unauthorized third parties.

(3) The Recipient agrees to accept these Data "as is" without any Government representation as to suitability for intended use or warranty whatsoever. This disclaimer does not affect any obligation the Government may have regarding Data specified in a contract for the performance of that contract.

(4) The Recipient may enter into any agreement directly with the Contractor with respect to the use, modification, reproduction, release, performance, display, or disclosure of these Data.

(5) The Recipient agrees to indemnify and hold harmless the Government, its agents, and employees from every claim or liability, including attorneys fees, court costs, and expenses arising out of, or in any way related to, the misuse or unauthorized modification, reproduction, release, performance, display, or disclosure of Data received from the Government with restrictive legends by the Recipient or any person to whom the Recipient has released or disclosed the Data.

(6) The Recipient is executing this Agreement for the benefit of the Contractor. The Contractor is a third party beneficiary of this Agreement who, in addition to any other rights it may have, is intended to have the rights of direct action against the Recipient or any other person to whom the Recipient has released or disclosed the Data, to seek damages from any breach of this

Agreement or to otherwise enforce this Agreement.

(7) The Recipient agrees to destroy these Data, and all copies of the Data in its possession, no later than 30 days after the date shown in paragraph (8) of this Agreement, to have all persons to whom it released the Data do so by that date, and to notify the Contractor that the Data have been destroyed.

(8) This Agreement shall be effective for the period commencing with the Recipient's execution of this Agreement and ending upon __________________. The obligations imposed by this Agreement shall survive the expiration or termination of the Agreement.

(9) To access TDP drawings, select the Download TDP link on the Open Solicitation Page to request authorization.

Recipient's Business Name _______________________________________________________________

Business Cage Code_______________ E-mail Address________________________________________

By__________________________________________ _________________________________

Authorized Representative Date

Representative's Typed Name ____________________________________________________________ and Title _____________________________________________________________________________

3. There is no monetary changes to this solicitation.

*** END OF NARRATIVE A0002 ***

7 7

SECTION A