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 

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.

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

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

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 SOLICITATION 

NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

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. 

12. ACCOUNTING AND APPROPRIATION DATA (If required)

copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

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)

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
ACTIVE RADIO FREQUENCY IDENTIFICATION (aRFID) TAG REQUIREMENTS FOR 

OCONUS SEA VAN SHIPMENTS 

The Contractor shall prepare and affix Government-furnished Active Radio Frequency Identification 

(aRFID) tags to shipment containers, for all OCONUS destined shipments via ocean transport in sea 

containers in accordance with the following RADIO FREQUENCY (RF) TAG REQUIREMENTS:

I. DEFINITIONS

A. "Radio Frequency Identification (RFID)” A method of automated identification using electronic 

tags capable of receiving/storing and/or transmitting digital information by means of, and in 

response to, radio frequency (RF) energy.

B. Radio Frequency Identification (RFID) Tag: A small radio transmitter or transceiver that can 

store user defined data in nonvolatile, read/write memory, and can be monitored and controlled 

by other devices. Radio Frequency Identification tags may be "active" (aRFID) which produce 

their own radio signal with their own power source or "passive" which receive their power from 

an interrogator by radio frequency (RF) transmission.

C. aRFID Laptop Write Station Computer: A "laptop" computer configured to "write" aRFID tags.

D. aRFID Write Software: The Government-owned software used in conjunction with aRFID 

equipment to gather ID tag data on military-sponsored shipments and report information for 

compilation in Government databases on regional servers for In-Transit Visibility.

II. GENERAL INFORMATION

A. It is the objective of the Government to use aRFID Technology for all Chemical and Packaged 

Petroleum sea containers going to OCONUS locations in order to maintain Total Asset Visibility 

(TAV) of these products on the battlefield. The Army has incorporated RFID Technology into its 

Joint Vision 2010 Focused Logistics Program.

B. The objective described in paragraph A above supplements DFARS clause 252.211-7006, Radio 

Frequency Identification, which requires the Contractor to prepare and affix EPC Class 1 passive 

RFID tags at the case and palletized unit load packaging levels, for shipments of items that are 

being shipped to any of several Defense Distribution Depots or Air Mobility Command 

Terminals.

C. The aRFID application software to be used for aRFID tagging of OCONUS shipments is 

Government-owned. The Government shall provide the RF Write software and technical services 

required to facilitate implementation of RF tagging of shipments. This includes surveying the 

Contractor site for RF site preparation, installation and testing of software, installation of 

communications software interfaces to Government servers, and training vendor personnel to use 

the integrated software and hardware composing the RF tag "write" capabilities. The 

Government points of contact (POC) for acquiring the aRFID software and technical services 

are: DLA Distribution Transportation, oceancontainers@dla.mil or Phone number: 800-456-

5507.

I. RF EQUIPMENT AND EQUIPMENT SUPPORT 

A. HARDWARE:
The contractor will furnish all aRFID equipment. The Contractor shall contact and coordinate with the 

Government POCs for the delivery of the initial software and for any other assistance or advice required. 

1. aRFID Tags:

The aRFID Tag model include ST 654/656 "active" tag with its own database engine and file 

system. It features 128 bytes of read/write memory and supports tag-initiated communication 

triggered by system sensors. It is hermetically sealed, waterproof, and able to withstand the 

shock and vibration of transportation. One (1) aRFID Tag model ST-656-1 is required for 

each container shipment.

2. Data cables:

The Contractor shall purchase the cables from a GSA Schedule (Savi Write Adapter for the 

SaviTag 654 & Savi ISO Container Door Tag or Government-approved substitute) 

B. SOFTWARE

The Government will furnish all application software, and perform all actions required to install and test 

software, and then train Contractor personnel to use software and equipment to perform required ID tag 

activities.

C. aRFID INFRASTRUCTURE SUPPORT

The Government shall test aRFID equipment after the Contractor has received all necessary software. 

The Contractor shall provide assistance to facilitate the download/testing and to insure access at aRFID 

equipment locations.

IV. PROCEDURES

A. The Contractor shall input data or "write", one aRFID tag for each OCONUS container load, , 

and affix the aRFID tag to the Container by the most secure method available, behind the locking 

bars. Each aRFID tag shall be written to contain the data attached, formatted as specified by the 

data definition for the 128k aRFID tag. The Government will provide training for contractor 

personnel to "write" the data to tags. The Vendor Shipping Module (VSM) will be used along 

with the Java Automated Manifest System (JAMS) software.

B. The Contractor shall be responsible for replenishing and maintaining its inventory of aRFID tags. 

C. When the Contractor writes data to the aRFID tag the Contractor is responsible for verifying that

the data successfully writes to the tag using the data write verification feature included with the 

JAMS software.

V. TRANSPORTATION

The Contractor shall be responsible for all shipment of products and in accordance with 49 CFR 170-

178, International Maritime Organization – International Maritime Dangerous Goods (IMO-IMDG), 

International Civil Aviation Organization – International Air Transport Association (ICAO-IATA), and 
Military Aircraft (MilAir) [Air Force Manual (AFMAN) 24-204]. The Contractor shall be responsible 

for shipment of materials from its facility to the customer within CONUS; to the customer or designated 

Container Consolidation Points (CCPs) or Point-of-Embarkations (POEs) for OCONUS; or to freight 

forwarders for FMS orders. The Contractor shall email delivery@dla.mil for tentative destination 

instructions for FMS delivery orders. The Contractor shall also be responsible for transporting customer 

material returns and discrepant orders from both CONUS and OCONUS customer sites to the 

Contractor’s facility (see Section 3.4.8.1).

Bulk Shipments: The Contractor shall coordinate delivery of bulk shipments with the recipient. Bulk 

shipments may require multi-model transportation and shipping when seasonal transportation lanes are 

available (e.g. barges to Alaska). Orders for bulk shipments may be for quantities that exceed a 

recipient’s capacity to receive and store at one time. 

Vendor Shipping Module (VSM): The Contractor shall establish a VSM account. To create an

account, contact the DLA Distribution New Cumberland, J3 OS Transportation Operations (1-800-456-

5507) which will assign a unique User Name and Password to access the website at 

https://vsm.distribution.dla.mil/. Once assigned an account in VSM, the contractor will be able to access 

their current open purchase orders. By entering the weight and dimensions of packed ready to ship 

orders in VSM, Military Shipping Labels (MSL) and carrier documentation will be available to print 

from the website. Small parcel shipments will be available immediately; freight shipments will be 

available based on contractor’s submission to VSM. Contractor will pack according to the mode of 

transport selected by the Government. Containers shall be loaded, blocked, and braced with WPM wood 

suitable for overseas transportation. 

FMS orders may remain at the contractor’s facility for an extended period of time (30 days or longer)

pending foreign country clearances.

The Contractor shall:

• Submit Non-Hazardous and Hazardous OCONUS EDI 850 orders in an automated format to 

VSM WebServices

• Utilize VSM-generated MSLs; screen labels for incorrect and missing data (e.g. invalid delivery 

addresses, blank required fields, quantity/weight/cube discrepancies, missing labels); coordinate 

updating with correct, required data

• Retain VSM transaction time stamps to substantiate Government processing and response time 

adjustments to delivery times and correcting the ship dates of all FSL orders (see 3.4.5.2(D)).

• For OCONUS orders, screen and flag VSM responses for instructions to ship HazMat to New 

Cumberland or Calcium Hypochlorite to Norfolk, instructions to ship packages and containers in 

excess of 30,000 lbs, instructions to ship to PO Boxes, and responses with incomplete ship-to 

address information

• Request ocean container shipments through the DLA Distribution New Cumberland, J3 OS 

Transportation Operations at oceancontainers@dla.mil

• Provide adequate warehouse space to accommodate VSM hold material at no additional cost to 

the Government