Amendment 0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

2. AMENDMENT/MODIFICAITON NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicble)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICIATION NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 11)

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 amendment; (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 your 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 APPROPIRATION DATA (If required)

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

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) 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 date, 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.

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.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

NSN 7540-01-152-8070

Previous edition unusable

SP3300-21-Q-0003

AMENDMENT 0001

Amendment 0001 is hereby incorporated into Solicitation SP3300-21-Q-0003 and shall become part of any contract issued.

The purpose of this amendment is to answer a contractor question and incorporate a revised Amendment 0001 Exhibit 1 – CDRL.

1. Question/Answer

Question #1: The CDRLs contained in the RFQ are overly broad and drawn to cover a wide range of various equipment and systems. We require clarification to ensure our compliance.

There is reference to a Paragraph 3.1.18 in the Government’s Statement of Work. No such paragraph exists in the solicitation. Furthermore, there are multiple references to network connections. The VLMs being procured are stand-alone devices that are not connected to any network. There is no software or programming being provided. Our equipment uses a closed operating system via a self-contained touch screen controller to stow and retrieve trays. We have no software documentation manual since we are not providing any software. We have no data to control. We keep no inventory of the machine contents. We ask that the CDRLs be redefined to more closely match the equipment being provided. The CDRLs should reflect this specific requirement. References to software and networks should be removed since neither are being provided.

Answer #1: All of the CDRL items listed in the solicitation are applicable to this VLM solicitation. It fundamentally does not make a difference if this system connects to our network or not. If it is an AMHE capability procured by DLA, regardless of connectivity to our enterprise network, and has a computing device with an underlying OS, then all of the stated CDRLs apply.

Furthermore, there are some challenges with the detail and rationale provided in the query.

Given that an Operating System (OS) is in fact “software,” and one of the most common and exploited types of software, stating that your system has an OS, but you don’t include software is contradictory. Additionally, commercial software OSs such as Windows CE that is specifically called out in device manuals do not inherently have the capability to control devices like VLMs.

As highlighted above, there is clearly a need for software documentation and well as a software baseline listing. Additionally, as this software must reside on a physical device, the need for the hardware deliverables should be apparent as well. This would include information like make, model, serial number, MAC address etc. The HW and SW baselines may in fact be short lists, but still much needed artifacts to ensure the capability can be Accredited & Authorized to be in the DLA production environment. As we have demonstrated, there is clearly hardware and software being delivered, the need for a test plan to exercise these elements should be clear. Moreover, the list of roles and accounts on the device, with descriptions and privileges, should be codified as well. Each login, whether a typical “operator” level or an account with increased privileges such as the ability to configure and troubleshoot the system should be called out along with a methodology on how

SP3300-21-Q-0003

AMENDMENT 0001

to access it. Again, these account are device specific and irrespective of any network connectivity.

2. The attached Exhibit 1-CDRL has been revised to correct Block 5 Contract Reference from Specification Paragraph 3.1.18 to Specification Paragraph 3.1.17.

All other terms and conditions remain unchanged.

END OF AMENDMENT 0001

Amend 0001 Page 2

Acquisition Operations, J-7 Mifflin Avenue, Bldg 430 New Cumberland, PA 17070

717-770-5390 (P) Benjamin.Bailey@DLA.MIL