rfid v user guide - usarmyamis.army.mil · • rfid-tagged assets will be loaded or discharged from...

SAVI TECHNOLOGY 3601 Eisenhower Avenue, Suite 280, Alexandria, VA 22304 / T: 1.571.227.7950 · F: 1.571.227.7960

Revision v9 of 65

aRFID V User Guide Prepared by Savi Technology

July 2020

Contract # W52P1J-20-D-0034


Revision v8 of 65

Revision History

Date Revision Author Description

29-Jun-20202 V1 J Kendrick Initial revision.

1-July-2020 V2 M. Beyea Updated, HW ENG

2-Jul-2020 V3 J. Sarles Updated Ordering Process

6-Jul-2020 V4 J. Sarles Updated 2.1.2.1 to match ZQ520 models

7-Jul-2020 V5 E. Jones Updated formatting and graphics

9-Jul-2020 V6 M. Beyea Update SMR-650, Sat modem and printer sections

13-Jul-2020 V7 E. Jones Updated formatting and graphics

16-Jul-2020 V8 E. Jones Updated CLIN/SLIN tables

27-Jul-2020 V9 R. Johnston Updated to correct Government-noted discrepancies


Revision v8 of 65


Revision v8 of 65

Copyright and Trademarks

© 2020 Savi Technology, Inc. All rights reserved.

This document is confidential and proprietary information of Savi Technology, Inc.

Savi, Savi SmartChain, SmartChain, and the Savi logo are trademarks or registered trademarks of Savi Technology, Inc. in the United States and other countries.

Other product names mentioned in this guide may be trademarks or registered trademarks of their respective owners and are hereby acknowledged.

Please address any comments or requests for updates to:

Savi Technology, Inc.

www.savi.com


Revision v8 of 65

TABLE OF CONTENTS 1 RFID V User Guide Overview ................................................................................. 7

1.1 Introduction................................................................................................................. 7 1.1.1 Purpose ..................................................................................................................................... 7 1.1.2 Sections .................................................................................................................................... 7

2 Hardware .................................................................................................................. 8 2.1 Interrogators (Readers) .............................................................................................. 9

2.1.1 aRFID Fixed Interrogator .......................................................................................................... 9 2.1.2 aRFID Interrogator POD ......................................................................................................... 12 2.1.3 SatCom (Satellite) Modem (Iridium) ....................................................................................... 15

2.2 aRFID Transponders (Tags) ..................................................................................... 17 2.2.1 aRFID Transponders .............................................................................................................. 18 2.2.2 Other Affected Savi System Products .................................................................................... 26 2.2.3 Software Compatibility ............................................................................................................ 27 2.2.4 Market Segments and Use Cases .......................................................................................... 27 2.2.5 Market Segment: Shipment Tracking ..................................................................................... 27 2.2.6 Market Segment: Larger Sized High-Value Asset with Manifests - Tracking ......................... 28 2.2.7 General Use Cases ................................................................................................................ 29 2.2.8 aRFID Transponder Specifications ......................................................................................... 35

2.3 Portable Deployment Kit III ...................................................................................... 45 2.3.1 Portable Deployment Kits ....................................................................................................... 46

3 Hardware Cables ................................................................................................... 53 4 Software ................................................................................................................. 54

4.1 Software Desirable Features .................................................................................... 54 4.1.1 Edge Applications ................................................................................................................... 55

4.2 Security Features...................................................................................................... 56 5 User Ordering Procedures ................................................................................... 56

5.1 General Contract Information .................................................................................. 56 5.2 Delivery Order (DO) and Task Order (TO) Request Packages ............................... 57 5.3 Ordering Process through Contracting Office ....................................................... 57


Revision v8 of 65

5.4 Delivery Requirements ............................................................................................. 58 5.5 Inspection/Acceptance ............................................................................................. 58 5.6 Invoicing and Billing ................................................................................................. 59

6 Recommended Equipment Configurations ........................................................ 59 6.1 Technical Engineering Services (TES) .................................................................... 59

6.1.1 Approach to Providing Turn-Key Solutions ............................................................................. 60 6.1.2 Methodology and Process ...................................................................................................... 60


Revision v8 of 65

1 RFID V USER GUIDE OVERVIEW

1.1 Introduction

1.1.1 Purpose

This User Guide (UG) is designed to assist Government personnel in determining the system configuration that will best meet their aRFID V operational requirements. The UG is available to Users on Savi’s web site. The UG is a comprehensive tool that aligns with the Pricing CLIN structure to enable prospective Users to formulate a workable process as to potential solutions utilizing the CLINS within the Contract which best meets their operational requirements.

The UG is divided into logical sections for ease of use. The sections provide a User with a complete User list, with a detailed description of features and prices of all hardware, hardware cables, software, user procedures, recommended equipment configurations, technical engineering services (TES), training, warranty, CLIN price list, and any additional information to simplify the implementation of an aRFID-V solution. The UG is meant to be a simple, easy to understand document that allows Users to order and build configurations that meet their needs.

1.1.2 Sections

Each section of the UG is technically accurate and aligns with the Pricing CLIN structure and is complete with descriptions of the hardware (including pictures), software, and technical engineering services (TES). CLINs are used throughout the document to facilitate the User’s ability to properly identify and order the appropriate item(s). CLINs are clearly annotated on drawings, charts, product descriptions, specification sheets, etc. When a product requires additional equipment to make a complete workable product, the additional equipment and CLINs, if applicable, are clearly identified in the description. All references to a geographic area where products may, or may not, be used are clearly annotated in the UG and the CLIN description, if applicable. The UG includes the sections identified below.

1.1.2.1 Hardware

The hardware section is organized into sub-sections based upon the major types of equipment provided and includes a discussion of the main features of each piece of equipment, including physical dimensions, power requirements (wattage and voltage), and heat generated by equipment. Precautions such as the minimum distance between various devices, is provided. The UG contains instructions for the User to specify equipment destination to ensure the aRFID-V equipment is compatible with the commercial power supply and adapter plugs for the geographic area in which it will be operated.


Revision v8 of 65

1.1.2.2 Hardware Cables

This section lists all cables with Model Numbers provided and equipment cable requirements in a chart format that allows the User to identify the correct cables for connecting aRFID-V devices. CLINs are provided on the chart. All cable requirements for equipment installation are described in this section. This section clearly indicates the appropriate cables and interfaces for the various aRFID-V components and provides a reference to the applicable parts.

1.1.2.3 Software

This section provides a full description of all software provided. It includes a discussion of the primary function, minimum memory requirements, program capabilities, major features, and benefits. This section explains, in non-technical terms, the recommended software packages for specific applications.

1.1.2.4 User Ordering Procedures

This section contains ordering procedures that provide the User with all the necessary information required to order aRFID-V products and Technical Engineering Services (TES). Savi points-of-contact, telephone numbers, Help Desk access, and addresses are included here.

1.1.2.5 Recommended Equipment Configurations

This section addresses Savi’s recommended equipment configurations to meet various Users’ aRFID-V requirements with easy-to-understand, step-by-step directions including any physical or facility considerations. The recommended configurations represent the most economical hardware, software, and technical engineering services (TES) that meet possible User requirements. This section provides information to assist the Users with building an aRFID-V configuration that best meets their needs. The configurations include the appropriate CLIN numbers.

2 HARDWARE

The Savi Team has a rich and extensive history as the Government’s provider of innovative, state-of-the-art Radio Frequency In-Transit Visibility (RF-ITV) products.

Our team provides a broad array of hardware products that meet or exceed the RFID-V requirements. Our Interrogators, Transponders, and Portable Deployment Kits III (PDK IIIs) are key components of over 2,400 RF-ITV nodes throughout the world and continue to provide the reliability of reads that the U.S. Department of Defense (DoD), NATO, and partner coalition countries have come to rely on. We continue to innovate while maintaining the ISO 18000-7


Revision v8 of 65

standard on all new products.

Our products are certified to operate in 50 countries worldwide, including the U.S. and U.S. DoD Host Nation Countries. These products meet all required industry standards for the countries that they are deployed to with certifications covering electromagnetic radiation limits, consumer product safety requirements, and use around explosive devices and hazardous materials.

Savi’s products and solutions incorporate multiple hardware vendors such as the Panasonic ruggedized tablet and the Zebra mobile printer into our portable and deployable solutions. Since 1994, our equipment has been used in most major US military operations, including the current operations in Iraq and Afghanistan. Our equipment is designed to survive in the most rugged environments in the world across the complete spectrum of global climates, from the heat of Southwest Asia to the cold of the North Atlantic Treaty countries. Our lessons learned helped us make the necessary improvements to our equipment to handle the many types of environments where our troops must operate. For example, we have improved the seals of our interrogators and transponders in response to the variety of extreme conditions encountered. The internal design and battery design were changed to more adequately support the extended operational life of the transponders. These improvements have enhanced our products’ ability to survive the harshest conditions.

2.1 Interrogators (Readers)

2.1.1 aRFID Fixed Interrogator

RFID V CLINs, Fixed Interrogators

0001 Active RFID - Fixed Interrogators (ISO 18000-7:2008)

RFID V Unit Price

Inspection and Acceptance

0001 Model SR-650-101-WW-5 CN:ISO-GPS, Fixed Interrogator, GPS Enabled - Includes User documentation, bundled w/ installation CD for tag commissioning and read software applications, includes software development kit , Interrogator Configuration Tool and CAI compliant MS Windows Driver. Includes AC and DC power cords, RS 485 cable (100 foot) and CAT 5e cable (100 foot). 5-year warranty

EA $1,639.42 Destination


Revision v8 of 65

Savi interrogators can be mounted in diverse climates with exposure to weather extremes. They are industrially hardened and weatherproofed and comply with the IEC 60529 IP54 rating and are operable within the specified Government temperature range requirements. Our interrogators have a full range of alternating current (AC) and direct current (DC) power supplies. Our dual-mode fixed interrogators are omnidirectional, with a range of over 400 ft., which exceeds the 300-ft. minimum range using ISO 18000-7 protocol. The interrogators have built-in Universal Infrastructure Device Identifiers (UIDI) for unique node identification.

The over-the-air protocol we implemented based on the ISO-18000-7:2008 standard provides the capability to read 40 bytes of data from a transponder in a group of five transponders, traveling at speeds up to 25 mph in all environments. Our interrogators can collect 250 active transponders at distances greater than 300 ft. during a single collection cycle, and they can capture multiple transponder IDs.

Savi Fixed Reader (SR-650)

Features and Usage: • Monitors many aRFID tags over a wide area up to 400 feet from the reader (interrogator)

o Provides backbone for the US DoD RF-ITV Network o Collects location & status of aRFID tags

• Enables automatic data collection o Works with Site Manager, SmartChain, and TIPS

• RFID V version includes a GPS receiver and supports ISO 18000-7 tags • Includes worldwide power, 100’ Ethernet, 100’ RS-485 cables

Differentiators: • Actual maximum UHF Range longer than competitive products

Specs:

• Weight: 4.2 lbs (1.9 Kg) • Dimensions: 12 in. (30 cm)

x 5.5 in. (14 cm)


Revision v8 of 65

• Up to 400 feet on data sheet (up to 650 feet has been tested in an optimal environment) • GPS receiver makes this reader unique

Use Cases for RFID V aRFID Readers

aRFID UHF 433 MHz Readers • For asset and cargo tracking within customer-owned facilities and/or at specific locations

where fixed or mobile readers can be set up. o Yards, Warehouses, Gates, Doorways, Along roads at specific locations

• Used to read and write data from/to Savi aRFID tags (transponders) • Low data cost

o Readers are interfaced with your existing or new networks and systems

Figure 1: Savi’s Active Reader Technology

• See SR-650 Installation Guide for installation instructions.


Revision v8 of 65

2.1.2 aRFID Interrogator POD

RFID V CLINs, RFID Interrogator POD

0002 RFID Interrogator POD RFID V Unit Price


0002 Model Number SMR-650-218-5 CN:ISO, RFID POD with 9-foot USB cable, User documentation, bundled w/ installation CD for tag commissioning and read software applications, includes software development kit , Interrogator Configuration Tool and CAI compliant MS Windows Driver. 5-year warranty

EA $433.25 Destination

Savi Mobile Reader (SMR-650)

SMR-650 Features: • A smaller, lighter aRFID reader device than a fixed reader

Specs:

• Weight: 6.4 oz (181 g) • Dimensions: 6.25 x 2.5 x 1 in.

(15.9 x 6.3 x 2.5 cm)


Revision v8 of 65

• Used when portability and small size is most important • Often paired with a laptop or handheld tablet to:

o Perform spot checks o Commission tags

• Supports ISO 18000-7 tags for RFID V • 9-foot USB cable included

SMR-650 Usage: • Used in Portable Deployment Kits III (PDK IIIs) as a portable reader when paired with a

ruggedized laptop or tablet computer • Works with Savi SmartChain, Site Manager, ITV Server, and TIPS. • See SMR-650 Installation Guide for installation instructions

2.1.2.1 Portable Barcode Label Printer

RFID V CLINs, Portable Barcode Label Printer

0009 Portable Bar Code Printer RFID V Unit Price


0009AA Model # ZQ520-5, Portable Printer w/ Carrying Case and below accessories, 5 years warranty

EA $ 2090.67 Destination

0009AB Model # ZQ520 Carrying Case w/ Strap EA $ 86.46 Destination

0009AC Model # ZQ520-Batt-Chrg, Battery Charger, . Includes North American VAC Power and Plug


0009AD Model # ZQ520-Batt, Rechargeable Battery


0009AE Model # ZQ520-AC-Adapter, AC Adapter EA $ 77.18 Destination

0009AF Model # ZQ520-CBL, Interface Cable EA $ 30.30 Destination


Revision v8 of 65

0009AG Model # Roll of (enter # of labels per roll) Polyester Label Stock, Zebra Thermalock Labels, Model #4000D, Roll of (80 labels per roll) Polyester Label stock (4”x6”)



Revision v8 of 65

Portable Bar Code Label Printer (ZQ520)

Features: • Portable battery powered label printer • Built-in battery charger • Numerous accessories such as carrying case, extra batteries, AC adapter

Use Cases: • Print Military Shipping Labels (MSLs) or other bar code labels • Use with tablet or laptop and SmartChain Workstation or TIPs • Use with PDK III

2.1.3 SatCom (Satellite) Modem (Iridium)

RFID V CLINs, SatCom (Satellite) Modem (Iridium)

Specs:

• Weight: 1.81 lbs (0.82 kg) • Dimensions: 2.6 x 6.1 x 6.2 in.

(6.7 x 15.5 x 15.8 cm)


Revision v8 of 65

0007 RFID Satellite Communication Equipment RFID V Unit Price Inspection and Acceptance

0007AA Model # A3LA-RG-SVR-KIT-5, Satellite Iridium Modem w/ GPS , NAL Satellite Modem with 10-foot Serial Cable, NAL Omni-Directional Satellite Antennas with 5-foot Cable, and Connectors, 5-year warranty

EA $ 2846.03

Destination

0007AB Model # SAF5350A-SV, Mast Mount Antenna


0007AC Model # SAF5340-A-SV, Stationary Magnetic Mount Antenna


0007AD Model # SYN7391A-SV, Portable Magnetic Mount Antenna


0007AE Model # SAF5270G-SV, GPS Antenna EA $ 62.87 Destination

0007AF Model # LA-3098, AC/DC Power Adapter (if required for operation), Includes North American VAC Power and Plug

EA $ 206.80

Destination

0007AG Model # SYN-DC-936-SV, AC/DC Power Adapters and Cables (Vehicle)


0007AH Model# HRC-24-7XA , 10-foot Serial Cable


Iridium Satellite Modem (NAL A3LA-RG-SVR-KIT-5)


Revision v8 of 65

Features: • Iridium Satellite Connectivity (SBD, SMS, Data Switch, RUDICS) • Built-in GPS receiver • RS-232 interface

Use Cases: • Provides Iridium satellite network connectivity and GPS when used with a tablet

computer or laptop • Use with tablet or laptop and SmartChain Workstation or TIPs • Use with PDK III

2.2 aRFID Transponders (Tags)

Savi’s active transponders are omnidirectional, exceed the 300-ft. minimum range, and are fully compliant with ISO 18000-7 for air interface communications protocol. All transponders are industrially hardened and can operate beyond the temperature ranges specified for RFID-V. Our active transponders with replaceable batteries use the specified battery type (A) and have a battery life range of up to 5 years at two collections a day. The magnetic mounts, which are ordered separately, exceed the Government’s magnetic strength requirement for a Neodymium magnetic mount of a minimum N28 grade. The majority of our transponders offered under this contract were developed with our System on a Chip (SoC) technology, yielding longer battery life and greatly improved read ranges. In addition, all active transponders support our over-polling protection algorithm. Our patent pending over-polling protection algorithm protects and

Specs:

• Weight: 7.1 oz (201 g) • Dimensions: 4.0 x 2.43 x 0.95 in.

(10.2 x 6.1 x 2.4 cm)


Revision v8 of 65

adds to the battery life of all transponders in all operational environments.

2.2.1 aRFID Transponders

0003 Active RFID Transponders (ISO 18000-7:2008) RFID V Unit Price Inspection and Acceptance

0003AA Model ST-621-030, License Plate Transponder - Electronic Identification w/ no user writeable data memory

EA $ 27.92 Origin

0003AB Model ST-621-030 CN:MB, License Plate Transponder w/ bracket - Electronic Identification w/ no user writeable data memory

EA $ 28.35 Origin

0003AC Model ST-621-030 CN:MM, License Plate Transponder w/ magnetic bracket - Electronic Identification w/ no user writeable data memory

EA $ 39.23 Origin

0004 Asset Transponders RFID V Unit Price Inspection and Acceptance

0004AB Model # ST-618-030 CN:MM, Asset Transponder (2K memory) w/ magnetic bracket - Electronic Identification w/ user writeable data memory

EA $ 40.32 Origin

0005 Mounted Transponders RFID V Unit Price Inspection and Acceptance

0005AA Model ST-656-040, Door Mounted Data Rich Container Transponder (256 KB memory) - Electronic Identification w/ user writeable data memory

EA $ 108.94 Origin

0005AB Model ST-626-030, License Plate Transponder Door Mounted Container - Electronic Identification w/ no user writeable data memory

EA $ 106.18 Origin


Revision v8 of 65

0005AC Model ST-654-041, Data Rich Transponder (256 KB memory) Electronic Identification w/ user writeable data memory

EA $ 45.86 Origin

0005AD Model ST-654-041 CN:MB, Data Rich Transponder (256 KB memory) w/ bracket - Electronic Identification w/ user writeable data memory

EA $ 48.72 Origin

0005AE Model ST-654-041 CN:MM, Data Rich Transponder (256 KB memory) w/ magnetic bracket - Electronic Identification w/ user writeable data memory

EA $ 56.40 Origin

0006 Active Transponders w/ DLA Label RFID V Unit Price Inspection and Acceptance

0006AA Model # ST-621-030-NSN, License Plate Transponder w/ DLA label - Electronic Identification w/ no user writeable data memory

EA $ 28.32

Origin

0006AB Model ST-621-030-NSN CN:MB, License Plate Transponder w/ bracket w/ DLA label - Electronic Identification w/ no user writeable data memory

EA $ 29.40

Origin

0006AC Model ST-621-030-NSN CN:MM, License Plate Transponder w/ magnetic bracket w / DLA label - Electronic Identification w/ no user writeable data memory

EA $ 38.63

Origin

0006AD Model ST-626-030-NSN, License Plate Door Mounted Container Transponder w/ DLA Label - Electronic Identification w/ no user writeable data memory

EA $ 108.21

Origin

0006AE Model ST-618-030-NSN, Asset Transponder (2K memory) w / DLA label - Electronic Identification w/ user writeable data memory

EA $ 29.08

Origin

0006AF Model ST-618-030-NSN CN:MB, Asset Transponder (2K memory) w/ bracket w / DLA label - Electronic Identification w/ user writeable

EA $ 31.64

Origin


Revision v8 of 65

data memory

0006AG Model ST-618-030-NSN CN:MM, Asset Transponder (2K memory) w/ magnetic bracket w / DLA label - Electronic Identification w/ user writeable data memory

EA $ 41.82

Origin

0006AH Model ST-656-040-NSN, Door Mounted Data Rich Container Transponder (256 KB memory) w/ DLA Label - Electronic Identification w/ user writeable data memory

EA $ 109.34

Origin

0006AJ Model ST-654-041-NSN, Data Rich Transponder (256 KB memory) w/ DLA label - Electronic Identification w/ user writeable data memory

EA $ 47.17

Origin

0006AK Model ST-654-041-NSN CN:MB, Data Rich Transponder (256 KB memory) w/ bracket w/ DLA label - Electronic Identification w/ user writeable data memory

EA $ 48.40

Origin

Use Cases for RFID V Transponders aRFID Tags Under RFID V

For Asset Tracking in Yards, Warehouses, Gates, Doorways, along roads at specific locations

ST-654-041 and ST-656-040

Used in applications where writing tag data via USB cable is required, and/or large files (up to 256KB) are to be sent to the ITV Server during shipments. ST-656-041 includes ISO Dry Van Container Door Mounting Bracket

ST-621-030 and ST-626-030

Used in applications where no writing of tag data is required i.e. only an asset ID is required to tie the tag to an asset during shipping. ST-626-030 includes ISO Dry Van Container Door Mounting Bracket

ST-618-030

Used in applications where writing of minimal tag data (2KB max) is required, but not via USB (memory writing is performed via RF).


Revision v8 of 65

Asset Transponder: ST-618

Features and Usage: For customers managing a large fleet of assets

Rugged tag ideal for harsh environments

Provides asset & maintenance information

Large A-sized Li battery Less maintenance required with long, five-year battery life (based on 2 collections/day)

Provides memory 2KB for asset & maintenance information

Works with other ISO 18000-7 compliant products

Savi SoC based design enables greater UHF range, better overall performance, and battery life

SoC tests for the numbers of collects achieved without battery degradation has been in the 100s of thousands

SPECS: • Weight: 3.8 oz

(108 g) • Dimensions:

6.2 in. (15.8 cm) x 2.1 in. (5.4 cm) x 1.1 in (2.8 cm)

• Battery Life: ~5 yrs.


Revision v8 of 65

Consignment Transponder: ST-621 License Plate

Features and Usage: For customers needing quick tag deployment with less data required for commissioning

Only enough memory for a license plate (asset) ID

Requirement is for consignment (shipment) tracking, but not for maintaining manifest and other consignment details on the tag

Rugged tag ideal for harsh environments




SoC tests for the numbers of collects achieved without battery degradation has been in the 100s of thousands

SPECS: • Weight: 3.8 oz (108

g) • Dimensions: 6.2 in.

(15.8 cm) x 2.1 in. (5.4 cm) x 1.1 in (2.8 cm)



Revision v8 of 65

Consignment Transponder: ST-654 Data Rich

Features and Usage: Ideal for customers who need a high performance, data rich tag for performing asset shipments

Tag needs to store a lot of information Larger 256KB memory enables customer to associate shipping manifest data & asset information

Includes USB Port: Allows customer to connect to the tag via USB




SPECS: • Weight: 3.8 oz (108

g) • Dimensions: 6.2 in.

(15.8 cm) x 2.1 in. (5.4 cm) x 1.1 in (2.8 cm)



Revision v8 of 65

Consignment Transponder: ST-656 Data Rich, Container

Features and Usage: Same features as ST-654 in a different form for mounting onto a shipping container’s door

Tag needs to store a lot of information

Large 256KB memory enables customer to associate shipping manifest data & asset information

Provides additional tag security in terms of its mounting, when used on container

Tag is secured on the inside of container and cannot be removed from outside the container

External of tag only exposes a thin, flat antenna on the outside of container

Prevents damage and makes the tag less noticeable

C-clamp type door clamp ideal for monitoring ISO containers

SPECS: • Dimensions: 4.7 in.

(12 cm) x 5.2 in. (13.3 cm) x 2 in. (5 cm)



Revision v8 of 65

Savi Tag Designs

The ST-654 Data Rich Tag is the platform from which all cost-reduced SoC-based Savi Tag Designs are formed.

Consignment Transponder: ST-626 License Plate, Container

Features and Usage: Same features as ST-621 in a different form for mounting onto a shipping container’s door

Provides additional tag security in terms of its mounting, when used on container

Tag is secured on the inside of container and cannot be removed from outside the container

External of tag only exposes a thin, flat antenna on the outside of container

Prevents damage and makes the tag less noticeable

C-clamp type door clamp ideal for monitoring ISO containers

SPECS: • Dimensions: 4.7 in.

(12 cm) x 5.2 in. (13.3 cm) x 2 in. (5 cm)



Revision v8 of 65

This section provides an overview of the Savi aRFID Transponders and the associated use cases and specifications for the product.

Savi currently produces a high-end ‘data rich’ RFID tag (ST-654) with derivatives ST-618 and ST-621 (lowered memory), ST-656 and ST-626 (ISO container fitment. The ST-654 is well suited for tracking larger assets and shipping containers that hold many individual assets, and it is very popular within the DoD.

Figure 2: Savi Tags in Savi/DoD Network

2.2.2 Other Affected Savi System Products

The aRFID tag must support (and be supported by) existing RFID products and software that collects, reads and writes tags over ISO 18000-7. Therefore, the current Savi SmartChain software stack accepts the new tag, with any new tag enhancements and/or support for configuration of the tag’s new parameters implemented as transparent to the current stack. In terms of the software stack, any new tag parameters are handled by new software stack add-ins. Example: In the Savi Tag, Over-Polling Protection (OPP) shall be configured by Savi manufacturing in the ‘Off’ state as a default. OPP can then be turned on and off again using newer software stack, whereas the current older software stack shall use this transparent feature as configured by Savi manufacturing and won’t provide the option to turn on/off OPP.


Revision v8 of 65

2.2.3 Software Compatibility

The Savi Tag supports the current outbound integration points:

PL AMIS RF-ITV server

For the SmartChain Edge Software, the Savi tag behaves as an ISO 18000-7 Active RFID tag when encountering the existing RFID software and readers in the field. To existing software with no special knowledge of the Savi tag, the tag remains interoperable with the DOD’s existing infrastructure. For Savi software, support for the Savi tag model numbers over RFID is addressed.

Existing Software

Edge Software Serial/USB ISO 18000-7

FDF 1.5.4.x (including third-party applications such as TIPS Read/Write)

Y Y

SmartChain Site Manager 6.1 Y Y

SmartChain Workstation 6.1 Y Y

Table 1: Savi Tag Edge Software Compatibility

2.2.4 Market Segments and Use Cases

2.2.5 Market Segment: Shipment Tracking

The Savi tag allows users to track shipments from its origin to the destination, with manifest information potentially loaded into user memory. The tags are associated with the shipment prior to its journey and then tracks the location of the shipments.

Consignors initiate shipments via Assets, inter-modal shipping containers or trailers, or the shipment may consist of the vehicles themselves (military Unit Moves). Each shipment is addressed to a consignee at a specific destination. The content of the Asset or container, if provided, is captured in a manifest. Each manifest describes the contents of the container and provides users (either consignee or consignor) with ability to query its contents. The Savi tag will provide memory sufficient to support large manifests.

Users have existing procedures for preparing shipments and the associated documentation. For example, the US DOD prepares MIL-STD 129P shipping labels as part of all shipments, and for


Revision v8 of 65

shipments with OCONUS destinations, an Active RFID tag is applied to the shipment.

Shipments are often subject to theft or pilferage during the course of its journey. This risk is especially acute when the shipment travels through specific areas. In cases where pilferage occurs, users are frustrated because they do not know where and how the pilferage occurred and this absence of knowledge makes it hard for users to take actions to prevent future occurrences.

Business Problem

• Users want to know where the contents of their shipment are. It allows them to know when they can expect the contents. Users desire that they have a single interface to tracking their shipment status (for example, the ITV server).

• Users want to minimize any additional processes required to track shipments – adding a new complex commissioning process will slow the process of shipping and introduces potential inaccuracies.

2.2.6 Market Segment: Larger Sized High-Value Asset with Manifests - Tracking

The Savi tag can be used to track larger assets (sometimes containing manifests of smaller commodities) that are deployed for operations such as emergency relief, military exercises, movement of commodities, or part of a project such as construction.

These assets are mobile and may be deployed in locations without communications or network infrastructure. These deployments will vary in duration from weeks to months and up to a year. These assets may be moved by different parties and sometimes will change custody during deployment. There is a single organization who owns these assets and who has interest in tracking their location.

When being deployed, assets are stored in yards, parking lots (for vehicles) or warehouses (indoors). During storage, these assets are ‘usually’ (although not always) not required to be tracked. Assets in storage are typically reconciled on regular intervals (1-2 times a year). Assets are typically processed prior to deployment as well as after deployments.

Typical assets include vehicles (trucks, engines, construction vehicles) or other mobile Assets such as power generators, heavy equipment, or other larger items such as containers incorporating manifests of smaller commodities.

Assets may be self-propelled (vehicles), wheeled (towed or hauled by another vehicle or conveyance) or a generic chassis not designed for movement (shipping container) which requires special material handling equipment to be moved.

Key Business Problems • Time required for locating missing assets:

o For assets that are unmanned, and where custody changes hands in an ad-hoc


Revision v8 of 65

basis, the location of these Assets are often unknown. Manpower is spent locating these Assets including contacting possible parties that might have moved or used the assets last and culminating in a physical search over a wide area.

• Poor asset utilization: o High-value assets or specialized assets often have few substitutes. Urgent

requests for the assets require on-the-fly reallocation and repositioning of these assets that can only be done effectively if up-to-date information is available.

• Get status on assets in a yard: o Assets in a yard may be equipped with tags or sensors (such as environmental

sensors to monitor/track temperature, humidity, shock, or a door open/closed conditions) or other devices that report status such as providing time-based alarms for asset expiration dates, inspection dates, maintenance dates, etc. Getting this status back to an application in a cost-effective way will be advantageous to customers who can then continue tracking assets in a yard.

2.2.7 General Use Cases

2.2.7.1 Use Case: Install Tag

The installation use case is performed by Field Service Engineers (TES) who affix the Savi tag on shipments or assets.

UCNo UC-DRTAG-001

Priority Mandatory

Actors Field User - Local user who installs Savi on a container or asset and assigns the related information to the tag.

Precondition For shipments, the Savi tag is used to track containers - typically an ISO Shipping Container or similar container with large vertical or horizontal surfaces.

For assets, the Savi tag is used to track mobile assets such as vehicles, heavy equipment, power generators or any other large assets that can be moved and deployed.

The user must not require special tools to install the Savi tag. The tag is typically adhered with automotive tape, cable (zip) ties, or pop rivets. Sleeves or brackets are also used: plastic or magnetic mount.


Revision v8 of 65

Assumptions The technician or FSE (Field Service Engineer) is trained on installing the Savi tag.

Normal Course

1. The container (if used) is stuffed with contents, and the doors are locked and sealed, if required.

2. The technician installs the battery in the Savi tag and checks the tag via beep sequence and/or a software indicator via SmartChain Edge software to confirm if the tag is operational and that the battery is in good condition.

3. The user receives a preconfigured Savi tag from Savi, or the user has to configure the Savi tag before deployment (UC-DRT-002)

4. The Savi tag is affixed to the asset or the container using adhesive tape, or simply placed inside of polycarbonate, wood, or cardboard containers since RF propagation can take place through walls of these types of containers.

5. The Savi tag is commissioned with the contents of the shipment (see UC-DRT-003)

OR

The Savi tag is commissioned with the Data Rich data (see UC-DRT-003) 1. The Savi tag is now enabled for tracking.

Extensions Assets or Containers may include cargo such as ammunition and explosives, and the tag must support required certifications.

Exceptions None

Post Condition

Location update events from the tag are now supported through the ISO readers.

2.2.7.2 Configure Tag (RFID)

The configuration of the Savi tag is performed by the field user to prepare the tag for use.

UCNo UC-DRT-002

Priority Mandatory

Actors Field user

Precondition Savi tag has been installed and is operational.

The user either has 1) Active RFID software and readers (e.g., SmartChain Workstation and Savi


Revision v8 of 65

Mobile Readers) and access to the Savi tag.

The Savi tag must be provided with a factory default configuration so that this step is optional if the user chooses to deploy with factory configuration.

Assumptions None

Normal Course 1. User performs an RFID collection using either LF or UHF or performs a barcode scan on the Savi tag to pick up its TagID.

2. The RFID software reads the tags’ configuration parameters and presents them on the user interface.

3. User makes the changes to the tag’s parameters as required and saves these changes to the tag.

4. The user receives confirmation of the successful update of the Savi tag.

Exceptions None

Post Condition The Savi tag is now ready with the updated configuration.

2.2.7.3 Commissioning Tag

The commissioning of the Savi tag associates the tag with the manifest of the shipment or the Data Rich.

UCNo UC-DRT-003

Priority Mandatory

Actors Field user

Precondition Savi tag has been installed and is in working condition.

The user is equipped with SmartChain Workstation, and optionally Active RFID software and readers (e.g. Savi Mobile Readers).

The Savi tag memory is in the factory default condition (empty) or has been previously commissioned with prior data (reused)

There is no asset or shipment associated with the Savi tag in the ITV or SmartChain.

Assumptions None

Normal Course

1. Using SmartChain Workstation, the user performs an RFID collection using either LF or UHF or performs a barcode scan on the Savi tag to pick up its


Revision v8 of 65

TagID.

OR

Using SmartChain Workstation, the user performs a barcode scan to pick up the TagID of the Savi tag.

2. The user assigns a preloaded shipment manifest (such as a TAV file) or a Data Rich attributes file.

3. The user reviews the shipping manifest or asset attributes and ensures that it matches the contents.

4. If the user is using RFID, SmartChain Workstation will write the contents of the shipment or the asset to the tag.

5. Once the contents are written successfully, the contents are uploaded to the RF-ITV server and the tag ID is associated with the shipment or asset information.

Extensions Extensions of this use case include the ability to read, modify and commission the tag with updated contents.

Reading Contents from tag 1. Reading Contents using Active RFID: using SmartChain Workstation or third-

party applications and an ISO 18000-7 RFID reader, the user can retrieve the contents of a shipment or view the Data Rich attributes.

Third-Party Applications using ISO 18000-7

The commissioning can be performed with third-party products such as TIPS Write using Active RFID (SMR) and integration with the ITV server.

Wake From Hibernation

The Savi tag can also be put into hibernation state where the RFID is put into a low power state for storage purposes with the battery still in place. They do not respond to regular UHF activity. In order to “wake” these tags from this mode, the SmartChain Workstation “Hibernation” feature is used.

Exceptions None

Post Condition

The Savi tag container in the Server (ITV) is now updated with content level details.


Revision v8 of 65

2.2.7.4 Location Update via RFID

UCNo UC-DRT-010

Priority Mandatory

Actors Server – Either the ITV Server

Precondition The RFID infrastructure has been registered and reporting to the RF-ITV server and is operating ISO 18000-7 collection modes.

Assumptions There may be other tags within the vicinity of the Savi tag. The system shall support at least 250 tags within the collection range of an RFID reader.

Normal Course

Fixed Reader

The fixed reader is configured to perform regular RFID collections – either at 10-30 sec intervals for gates and chokepoints or 15-60 minutes for inventory / yard polling modes.

The Savi tag upon receiving the collections respond with the ISO 18000-7 Tag ID which is reported to the ITV server.

The RFID collections do not carry location information – instead, the RFID infrastructure as part of their registration includes location information that the tag is then identified with.

If the Savi tag is in a storage yard within coverage of an RFID reader for an extended period of time. The system will already have location information for the Savi tag from the RFID infrastructure.

Exceptions Low Battery

If the Savi tag has a low battery condition, this shall be reported through the RFID network during a location report.

Device Diagnostics

The Savi tag shall provide an alert to the server if any major subsystem of the tag is not responsive.

Post Condition

The asset or shipment that has been assigned to the Savi tag will have its location updated to that of the nearest RFID reader.


Revision v8 of 65

2.2.7.5 Decommissioning Tag

UCNo UC-DRT-020

Priority Mandatory

Actors Server – (ITV)

Savi tag user – user who tracks the tag.

Precondition The Savi Tag has been commissioned and is operational.

Assumptions None.

Normal Course

• The Savi tag will automatically update its end-of-journey via the following means:

a. RFID: the Savi tag is read by an RFID reader and the reader is registered as the destination of the shipment. The ITV server will generate a close-out message that will mark the shipment as completed.

Extensions Manual Decommissioning

The decommissioning of the Savi Tag is performed explicitly using SmartChain Workstation and uploaded to the Server.

See below (UC-DRT-021) for un-installation and reverse logistics for the Savi Tag.

Exceptions If the Savi tag is not decommissioned at the end of its journey, the servers (ITV) will display the current location of the tag although it is no longer tracking the shipment or Asset.

Users must manually decommission the tags using the processes defined by the ITV for decommissioning tags.

Post Condition

The Asset or shipment that has been assigned to the Savi tag be closed in the server – indicating that it has either arrived or is no longer active.

The Savi tag does not report its location.

The Savi tag is ready for reuse through a configuration or a commissioning use case (UC-DRT-002 / UC-DRT-003).


Revision v8 of 65

2.2.7.6 Uninstall Tag

UCNo UC-DRT-021

Priority Mandatory

Actors Field user

Precondition The Tag is installed on the Asset or container and has been decommissioned.

Assumptions None

Normal Course If required, the user removes the Savi Tag from the Asset or container.

Extensions None

Exceptions None

Postcondition The Savi Tag does not report its location.

2.2.8 aRFID Transponder Specifications

2.2.8.1 Regulatory

ID Description

DRT-REG-001

HERO

Equipment shall undergo Hazards of Electromagnetic Radiation to Ordnance (HERO) environment testing (MIL-STD-464). Active Tags shall be safe to use at least as close as one inch from unshielded munitions that contain 10 mA no-fire current, electro-explosive devices (EEDs).

DRT-REG-002

RoHS

Products shall comply with the (RoHS) Directive 2002/95/EC of the European Parliament and of the Council of 27 January 2003 on the restriction of the use of certain hazardous substances in electrical and electronic equipment.

DRT-REG-003

Radio Regulatory

Savi RFID products must meet applicable regulatory guidance to permit their use by the following nations:


Revision v8 of 65

• United States and Possessions • Canada, Mexico, Central America • European Union (EU) and NATO countries (including Denmark, Netherlands,

Poland, Spain, United Kingdom) • Australia • Asian Countries (Hong Kong, China, Singapore) • Pakistan, Saudi Arabia, Kuwait • South America (Brazil, Argentina, Chile, Colombia, Venezuela) • India

DRT-REG-004

DOD 4650.01 and 5000.01

Radio frequency dependent components of the proposed system shall comply with applicable DoD, national, and international spectrum management policies and regulations to include spectrum certification in accordance with DoD Directive 4650.01, " Policy and Procedures for Management and Use of the Electromagnetic Spectrum " and DoD Directive 5000.1, "The Defense Acquisition System". Frequency allocation shall be documented with a DD Form 1494 (Application for Equipment Frequency Allocation) and/or a "Note to Holder" as appropriate.

2.2.8.2 Environmental

ID Description

DRT-ENV-001

Operating Temperature

The product must operate normally in temperatures ranging from -30° C to +70° C.

Acceptable Test procedures are:

Low Temp: MIL-STD-810 Method 502.4 Procedure II for 4 hrs. at -30° C

High Temp: MIL-STD-810 Method 501.4 Procedure II for 168 hrs. between 30°C and 70° C

DRT-ENV-002

Storage Temperature

The product must be able to survive storage conditions (non-operational) between -40° C to +70°.

Acceptable Test procedures are:

Low Temp: MIL-STD-810 Method 502.4 Procedure I for 4 hrs. at -40° C


Revision v8 of 65

High Temp: MIL-STD-810 Method 501.4 Procedure I for 168 hrs. between 30°C and 70° C

DRT-ENV-003

Random Vibration

The Savi tag shall meet the Random Vibration Test per MIL-STD-810 Method 514.5 Procedure I at 2 x gravity (Root Mean Squared)

DRT-ENV-004

Loose Cargo Test

The Savi tag shall meet the Loose Cargo Test per MIL-STD-810 Method 514.5 Procedure II at 5Hz to 20Hz dwell with 1-inch vertical displacement for 20 minutes per axis.

DRT-ENV-005

Transit Drop Test

The Savi tag meets the Transit Drop Test per MIL-STD-810 Method 516.5 Procedure IV on a single unit at a 48-inch drop height with one drop on each side, edge, and corner for a total of 26 drops.

DRT-ENV-006

Humidity Test

The Savi tag meets the Humidity Test per MIL-STD-810 Method 507.4 Procedure I for 5 cycles (10 days) at 30° C to 60° C and 85% to 95% non-condensing.

DRT-ENV-007

Altitude Test

The Savi tag meets the Altitude Test per

MIL-STD-810 Method 500.4 Procedure I (Storage) (pressurizing at 10m/sec and depressurizing at 10M/sec) at 40,000 ft for 60 minutes. MIL-STD-810 Method 500.4 Procedure II (Operation) at 15,000 ft for 60 minutes

DRT-ENV-009

Salt Fog

The Savi tag meets the Salt Fog Test per MIL-STD-810, Method 509.4 Procedure 1.

DRT-ENV-010

IP Ratings 1) When battery is mounted into the tag, tag and battery cap meets IP 64 2) When battery is removed, tag meets IP 40 and no circuitry should be visible

when battery cap is removed


Revision v8 of 65

2.2.8.3 Other Hardware Requirements

ID Description Comments

DRT-HW-001

Labels and Markings

Per RFID V contract, Labeling Requirements meet Attachment 2, DoD Transponder Barcode Labeling Guidelines.

Tags shall provide the following labels and markings:

• Savi Name and Logo • Product Model Number • Product Serial Number (see

separate requirement for ISO 18000-7 labels)

• HERO label • Regulatory compliance labels • Battery Polarity

Savi Name, Logo, Model Number, and Serial Number must be visible when tag is mounted to an asset or container.

Savi Name and Logo may be embossed or stamped on the tag.

HERO label is visible when tag is mounted on an Asset or container.

Regulatory compliance labels must be placed on the tag.

DRT-HW-002

ISO 18000-7 Tag ID Label and Barcode

Tags are delivered with a barcode and label encoded with an ISO 18000-7 ID in accordance with DoD Transponder Barcode Labeling Guidelines Version 3.0, 25 June 08


Revision v8 of 65

DRT-HW-003

Battery Life

The Savi tag is supplied with sufficient power to meet the minimum requirements:

1. 5 years at 2 standard RFID collections / day at 20 degrees C

DRT-HW-004

Power Indicator

Power indication shall be provided in software readouts and as beep sequences when battery is replaced.

If the condition of the battery is low, the Savi tag must provide, via software readout and beep sequences a discernable indicator that will caution the user that the battery source should be replaced.

DRT-HW-005

Replaceable Batteries

Supports standard ‘A’ size Lithium/Thionyl Chloride (Li-SOCl2) 3.7 VDC battery.

The Savi Tag is supplied with user-replaceable ‘A’ size Lithium batteries that can be sourced from multiple third-party suppliers.

The Savi Tag uses a standard A size battery in a tag-resident housing, with a battery cap same as current ST-654 is designed (cap can be improved as required).

The batteries is replaceable without need for special tools, or the need to remove the tag from the asset or container.

DoD RFID-V Compliant Active Transponders shall use a replaceable battery as their primary power source. The battery shall meet or exceed the following specifications:

Format untapped and sleeved ―A‖ cell

Length 50.3 +/- 0.2 millimeters

Diameter 16.85 +/- 0.15 millimeters

Nominal Voltage 3.6 volts

Nominal Capacity 3.4 amp-hours

Maximum Continuous Current 20 milliamps

Maximum Pulse Current 60 milliamps

Operating Temperature -40 to +70 degrees Celsius


Revision v8 of 65

** The Savi Tags support the storage of batteries in a reversed polarity for shipment and reverse logistics per RFID V contract Attachment.

Maximum Storage Temperature +30 degrees Celsius

Weight 25 grams

The replaceable battery shall comply with the altitude simulation, free fall, vibration, and mechanical shock tests referenced by the following safety standards:

Underwriters Laboratories Inc.

Standard for Lithium Batteries" – UL 1642 – Third Edition – 1995

Secretariat of the United Nations

"Model Regulations on the Transport of Dangerous Goods"

Ref. ST/SG/AC.10/1 – Revision 12 – 2001

+ "Manual of Tests and Criteria"

Ref ST/SG/AC.10/11 – Revision 3 – 1999, amended per

ST/SG/AC.10/27 – Addendum 2 – Annex 4 – 2001

International Electrotechnical Commission

International safety standard for lithium batteries

"IEC-CEI 86-4" – 1st Edition – 1996…‖

DRT-HW-006

External Interfaces

RF (433MHz and 123 KHz) for RFID, Tag Reads, and Tag Writes.

USB 1.1/2.0 write cable connector (mini-USB) support shall be provided on the following tag:


Revision v8 of 65

ST-654 only. ** The USB chip used is based upon the FTDI brand FT232R chip, as reflected in Attachment DoD Transponder Hardwire Electrical Interface and Data Protocol - Version 3.0 for USB Guidelines, RFID V contract. ** Tag is operable and powered via USB when battery removed, per Attachment_DoD Transponder Hardwire Electrical Interface and Data Protocol - Version 3.0 to RFID V contract.

Tags with no USB support are:

ST-618, ST-621

DRT-HW-007

Beeper

A beeper shall be included in all Savi versions and shall provide a consistent output over time @ 2700 HZ +/-300HZ @ 60 dB or better with constant HZ response, ‘A’ weighted and measured @ 3 feet in free space.

DRT-HW-008

Database Memory – per ST-654, ST-618, and ST-621 derivatives on RFID V contract:

ST-654 = 256KB User Memory

ST-618 = 2KB User Memory

ST-621, ST-626 = No User Memory (License Plate Only, i.e. the ST-621 tag shall have sufficient writeable memory for users to write a Routing Code (e.g., KUS000).)

DRT-HW-

Plastic Housing Material

Polycarbonate (PC), or other suitable


Revision v8 of 65

009 material, designed and tested to meet:

Flammability: Plastic selected must meet UL94 V0 Flammability Rating. Savi tag is planned to be used by the DoD and commercial markets around flammable materials such as gasses and petrochemicals, and around and potentially in aircraft.

UV Protection: Plastic selected must have gone through testing in accordance with UL 746C F1, the Standard for Safety of Polymeric Materials, or has gone through testing in accordance with MIL STD 810G Method 505.5 Solar Radiation Procedure II. Savi tag must last for up to 5 years in direct sunlight outdoors when mounted onto containers or assets.

DRT-HW-010

Tag Color = same as current :

ST-654 = Dark Green

ST-618 = Dark Green

ST-621 = Black

ST-626/656 = Black

DRT-HW-011

Battery Change Robustness

The tag housing, battery contacts, and battery cap and cover mechanical and electrical parts shall support up to 100 battery changes, so as to ensure robustness over a potential 10-year tag life.

The tag’s battery may be changed every 6 months to 1 year, or a nominal 10 to 20 times in a possible 10 years of tag life. In some conditions the battery might be changed more often. To ensure a robust design, capability for up to 100 battery changes shall be supported by the Savi tag.

DRT- TAA-Trade American Act support Must be supported for all government


Revision v8 of 65

HW-012

contracts.

2.2.8.4 RFID Requirements

ID Description

DRT-RF-001

ISO 18000-7 Support

The Savi tag shall be compliant with ISO 18000-7 including the DoD Over Air Interface Guidelines - Version 3.0 to the ISO/IEC 18000-7:2008 specification and adhering to the DoD Interoperability Guidelines for the Over Air Interface - Version 3.0.

DRT-RF-002

UHF Line of Sight (LOS) Operational Read / Write Range of 500 feet

The UHF operational read / write range of the Savi tag to an SR-650 in an outdoor, non-obstructed environment shall be 500 feet. This 500-foot range shall be measured with the tag at a height of 4 feet from the ground mounted vertically either a non-metal surface or metal surface and reader at a height of 25 feet from the ground.

DRT-RF-003

Hibernation Mode (Disable UHF)

The EchoPoint "Enable/Disable UHF Wake Up Strobe" command shall be changed as follows:

A tag that receives the Write Enable/Disable UHF Wake Up Strobe command (command code 0xC3) with the DISABLE parameter value shall not respond to any UHF commands until it receives the Write Enable/Disable UHF Wake Up Strobe command with the ENABLE parameter value. This mode of operation will be called Hibernation Mode.

A tag in Hibernation mode will only respond to two LF commands: the Read Enable/Disable UHF Wake Up Strobe command (command code 0x43) and the Write Enable/Disable UHF Wake Up Strobe command with ENABLE/DISABLE parameter values (command code 0xC3). The tag will respond to both the point-to-point and broadcast versions of those commands.

A tag in Hibernation mode shall not respond to non-command LF messages (i.e., LF messages that do not contain a command code). Shall be supported by FDF.

DRT-RF-004

Firmware Repair over RFID and Write Cable

The Savi tag shall support the ability to update its firmware (for recall/repair purposes)


Revision v8 of 65

over RFID and/or write cable (write cable USB support on ST-654 only) using FDF (Fixed Device Framework). The firmware update shall cover the RFID modules.

DRT-RF-005

Configuring Savi Tag Parameters over RFID and Write Cable

The Savi Tag shall provide an interface for configuring the RFID V specified (ISO 18000-7) tag parameters including the tag operation modes over RFID and/or write cable (write cable USB support on ST-654 only) using FDF (Fixed Device Framework).

DRT-RF-006

Switchable Over-Polling Protection Algorithm (OPP): Turn OPP On or Turn OPP Off

The Savi Tag shall provide an interface to FDF (Fixed Device Framework) for configuring the OPP to include tag OPP On or OPP Off operation modes over RFID and USB (USB write cable on ST-654 only). (See also Appendix B for further details) 1 Tag Default = OPP Off: Support Over-Polling (Fast Polling) Protection Algorithm

as defined in the ‘Requirements Document_ST-616-031 ISO Fixes.doc’ 2 Supports Command for Configuring Tag for either OPP Off or On

2.2.8.5 Savi Software Requirements Regarding Tags

2.2.8.5.1 Edge Software Requirements for aRFID Transponders

ID Description

DRT-EDG-002

Configuring Savi Tag Parameters using SmartChain Workstation or Genesis

SmartChain (SC) Workstation (operating via FDF, over RFID and USB cable) shall provide the following functionality:

- Collect and identify Savi Tags

- Display the current Tag parameters including any diagnostic fault information

- Configure Tag parameters, including turning the OPP (over-polling protection) ON/OFF [GAP], and Hibernation Mode

SC Site Manager (operating via FDF, over RFID and USB cable) software shall


Revision v8 of 65

ID Description provide an interface to be able to

- collect and identify Savi Tags over RFID, - display the current tag parameters including any diagnostic fault information

using command line interface.

2.2.8.5.2 Documentation and Training Requirements for aRFID Transponders

ID Description

DRT-DOC-001

Installation, Configuration and Commissioning Documentation and Training

The Savi tag is provided with documentation and /or training that describes how a user can

- Specifications - Labels - purposes and placements - Install and uninstall the Savi tag - Commission the Savi tag with consignment or Data Rich attributes - Reader Placement, Fast and Over Polling Guidelines

2.2.8.6 aRFID Transponder Upgradeability

The aRFID tags are firmware upgradeable over RF or write cable using a standalone upgrade utility. This is targeting repair of firmware bugs and other upgrades as required. FW upgrades over RFID and write cable will always be supported.

2.3 Portable Deployment Kit III

The Savi mobility suite of products includes the Portable Deployment Kit III (PDK III) that support multiple configurations of hardware products that exceed the requirements. Savi’s deployable solutions continue to evolve to reflect the user community requirements to refine and update those features necessary to support the warfighter. Improved computer displays, communications and power connections, and easy-to-use software are a few of the enhancements we incorporated over time. We build all of our systems with portability in mind. Moving these components into the major operational theaters throughout the world requires the equipment to be rapidly deployed and able to survive vibration and shock during air and ground


Revision v8 of 65

transportation and rugged use while in operation. Our extensive knowledge related to deployable active Radio Frequency Identification (aRFID) hardware solutions is unmatched in the industry.

2.3.1 Portable Deployment Kits

2.3.1.1 PDK III

RFID V CLINs, Portable Deployment Kit

0008 Portable Deployment Kit (PDK III) RFID V Unit Price


0008AA PDK III Model LITE-PDK III-RI002-002-5, Portable Deployment Kit with ruggedized tablet w/read/write software applications, w/barcode scanner, RFID pod interrogator (150 feet) w/9’ USB cable, satellite modem w/GPS, power adaptors, 4 port USB 3 hub, in Transit Case, 5-year warranty. 90 day Deliver Required

EA $ 13,556.67 CLIN X008AA IS RESERVED: NOT AVAILABLE FOR ORDER AT THIS TIME

0008AB PDK III Model LITE-PDK III-RI002-001-5, Portable Deployment Kit w/Printer - ruggedized tablet w/read/write software applications, w/barcode scanner, RFID pod interrogator (150 feet) w/9’ USB cable, satellite modem w/GPS, power adaptors, Thermal transfer portable printer, 4 port USB 3 hub, in Transit Case, 5-year warranty. 90 day Deliver Required

EA $ 15,770.74 Destination

0008AC Ruggedized Panasonic Tablet w/read/write software applications, w/barcode scanner. 90-day Deliver Required

EA $ 4,570.43 Destination

0008AD RFID pod interrogator (150 feet) Model SMR-650-218-5 CN: ISO. 90-day Delivery



Revision v8 of 65

Required

0008AE Power Adaptors Model PDK III-AC-02, Power Adapters. 90-Day Delivery Required


0008AF Model PDK III-AC-06, Cables. 90-day Delivery Required


Portable Deployment Kit (PDK III)

Features and Usage: • For customers who need to support manned remote operations in austere environments

o Allows customers to set up temporary chokepoint Alternative to using fixed infrastructure

• Allows users anywhere in the world to provide ITV Server with RFID information o Iridium SatCom modem, 2D bar-code scanner, and ruggedized Panasonic tablet


Revision v8 of 65

included, along with SMR, AC and DC power cables, and optional Zebra 4” thermal transfer label printer

• Used when fixed infrastructure cannot be installed or accessed • Used when location of collection device needs to be mobile. • Used when satellite modem is required for data communications vs. LAN • Pre-configured as an easily deployable RFID node

o Rugged & portable • Supports ISO 18000-7 tags and LF • Complete RFID system in a single transit case • SmartChain Workstation pre-installed

o Additional software applications can be installed and used

Differentiators: • Turn-key operation – all components mounted and wired into the chassis in the

operational position; competitor’s product requires setup every time it is used

2.3.1.2 Association with Solutions

This product fits in to the DoD ITV and International Military Consignment Management Solutions as a portable asset tracking application/system.

2.3.1.2.1 Solution Description

See PDK III Solution Diagram below. For DoD, the PDK III product is a packaging of the standard Savi DoD ITV Solution including Savi SmartChain 6.1. For the U.S. Army, TC AIMS


Revision v8 of 65

and/or CMOS software developed by DoD is used for global cargo movement tracking is optionally to be used by customers in addition to the PDK III as an aftermarket application.

2.3.1.2.2 Hardware Solution Diagram – Complete PDK III System

In the below Figure 3, tablet, SMR Iridium SatCom Modem, Power supplies, and optional printer are to be interconnected so as to realize a turn-key system after the user connects power and antennas. All components also include an internal Li battery except for the Iridium modem.

PDK III: Tablet PC replaces laptop and handheld, with no additional handheld or label printer supplied.

Figure 3: The Savi Portable Deployment Kit III (PDK III) system


Revision v8 of 65

Hardware Software Compatibility

PDK III Computing Device Tablet

SmartChain 6.1 Workstation

This software must communicate with the SatCom modem and Savi Mobile Reader (SMR) to collect RFID tags and then forward data to the server via SatCom modem.

Table 2: PDK III Software Compatibility 2.3.1.2.2.1 Use Cases

Please refer to the above diagram. Following is a list of the standard use cases that are applicable to this product. The following Use Cases fall under the high-level ITV DoD Consignment Management Shipping Use Cases.

2.3.1.2.2.2 Chokepoint Read on Tablet

Set up and perform chokepoint operations using the tablet. This use case requires that a PDK III unit is set up in an austere location, possibly with no network connectivity (i.e. use Iridium modem). The operator configures the PDK III software to register the site in the SmartChain Workstation software and performs chokepoint operations using the SMR (used as a short-range fixed reader) that is provided. Chokepoint reads are uploaded to the server (ITV for PDK III). The operator (who is manning the PDK III at all times during PDK III use) is able to track movement of consignments and assets using server reports.

2.3.1.2.2.3 Tag Read/Write on Tablet

Tag Read/Write operations using the tablet. This use case allows the operator to read consignment information from the tag (in TAV format (DoD) via SmartChain Workstation using the SMR, update the data and write this back onto the tag via either via RF (SMR). These changes are then uploaded to the ITV server and the user can review the updated consignment information on the ITV server report.

2.3.1.2.2.4 Messaging Capability

The user may use the email capability of the PDK III’s browser by using a web-based email account such as Gmail in order to be able to send and receive email from other users. Emails will primarily consist of short text messages. The email capability of the PDK III is most likely to


Revision v8 of 65

be used over WIFI only if the user’s IT department and facility is able to enable this function. The PDK III shall also have the Microsoft email program installed, but this function shall not be tested by Savi.

2.3.1.2.2.5 Application Platform

The PDK III may be used for other applications that use its capability for deployment in austere environments. It’s capability to provide a Windows OS and satellite wireless connection makes it a suitable platform for running third party applications in remote locations. Known applications are CMOS and TC-AIMS II.

Third-party application support will not be provided by Savi, except when it pertains to restoring the PDK III to its original configuration.

2.3.1.2.2.6 CAC (SmartCard) Reader Authentication

The PDK III includes a SmartCard Reader to connect to the DoD ITV network. The operator will be required to insert a CAC card into the tablet’s on-board SmartCard Reader while logging on to the ITV network. The operator is to enter a PIN during the log-on process that will be used by the installed middleware to process authentication.

2.3.1.2.2.7 Deployment Environments

2.3.1.2.2.8 PDK III Used in Austere Environments

• PDK III will be operated in areas that are not developed and may have the following characteristics:

o No pavement or buildings o No electricity o Deserts o High temperature o High humidity o Windy o Dusty

• PDK III is normally used under cover such as under tarp or in filtered sunlight. • PDK III is sometimes used in direct sunlight. • PDK III is generally operated under cover when rainy. • PDK III is operated with care in dusty or sandy areas. • PDK III is deployed in a hazardous environment and may be sometimes dropped. • PDK III is transported with lid closed via military vehicles on bumpy roads.


Revision v8 of 65

• PDK III is sometimes operated on a table or other surface such as a crate or container, when in the back of a Humvee (HMMWV) or other vehicle, and sometimes (less frequently) even placed and used on the front seat of a vehicle.

• The PDK III may be operated in close proximity with ordnance.

2.3.1.2.2.9 Shore Operations

• Military sends a team with a PDK III and they set up a mobile chokepoint next to the discharge ramp of a ship. The ramp is approximately 40 feet wide.

• The PDK III will sometimes be operated via DC power of a vehicle and will sometimes be operated via AC power (using external AC/DC converter).

• RFID-tagged assets will be loaded or discharged from the ship via the ramp. RFID tagged equipment, cargo and vehicles which roll on and off the ramp are collected via the SMR reader attached to the PDK III.

• RFID tags which are read and stored in the Workstation Mobile Chokepoint software will be uploaded into the ITV server right there using the satellite modem in the PDK III.

2.3.1.2.2.10 Fixed Port Operations

• Sometimes Fixed Infrastructure (e.g. SR-650 reader) is installed at a Port and sometimes it is not. It is usually an “immature environment.” The PDK III will often be used to establish the port operations before infrastructure is installed

• If there is some Fixed Infrastructure, the Workstation software in the PDK III may be used to collect tag reads from the Fixed Infrastructure and send to the ITV server via the satellite modem.

• If there is no Fixed Infrastructure, the use case is the same as “Shore Operations.”

2.3.1.2.2.11 Aerial Port Operations

• The PDK III will be used for Military purposes at Commercial Airports and/or Military Air Bases. These can be austere and unimproved environments as described previously.

• RFID-tagged equipment, cargo and vehicles which are Loaded/Unloaded on C130, C141, C5, C17 and other cargo aircraft are collected via the SMR reader attached to the PDK III.

• The PDK III will be set up next to aircraft ramp on the tarmac. • The PDK III tablet will be used in a co-located staging area to create cargo manifests. • The PDK III will be under cover when raining.


Revision v8 of 65

2.3.1.2.2.12 Tactical Air Lift Control Team Operations

• Note: this use case is only applicable for the U.S. DoD and has not been validated for the International Military.

• The TALC locations will be harsh (mountainous), austere and unimproved environments as described previously. The TALC teams may be air-dropped into the location. The PDK III may be air-dropped in a pallet or delivered in a tactical vehicle.

• The PDK III will be used for receiving and manifesting passengers and cargo using existing tag user memory and PDK III software operations. The manifest information will be uploaded to the ITV server.

• The PDK III will be used to create Manifests with Passengers, Cargo and assets and associate these with the number on the tail of an aircraft using standard tags and PDK III software.

2.3.1.2.2.13 PDK III Air Transport

• The PDK III is usually shipped the same as other cargo assets. It is palletized, netted and tagged.

• The PDK III is sometimes transported as checked commercial or military baggage. • The PDK III may be transported via commercial or military passenger or cargo carriers. • The PDK III may be checked-in or shipped via couriers (FedEx, UPS ). • The PDK III must be shipped with all foam intact • We recommend retaining the original shipping foam crate and exterior packaging in the

event the PDK III will be shipped by courier

3 HARDWARE CABLES

0007 RFID Satellite Communication Equipment (Iridium Modem)

RFID V Unit Price


0007AF Model # LA-3098, AC/DC Power Adapter (if required for operation), . Includes North American VAC Power and Plug


0007AG Model # SYN-DC-936-SV, AC/DC Power Adapters and Cables (Vehicle)


0008AH Model# HRC-24-7XA , 10-foot Serial Cable EA $ 139.10 Destination


Revision v8 of 65

Destination

0008 Transit Cases RFID V Unit Price


0008AE Model PDK III-AC-02, Power Adapters, International, PDK III. 90-day Delivery Required


0008AF Model PDK III-AC-06, All Cables, PDK III. 90-day Delivery Required


0009 Portable Bar Code Printer RFID V Unit Price


0009AC Model # ACC-1319-1, Battery Charger, Includes North American VAC Power and Plug


0009AE Model # ACC-1313-2, AC Adapter, Includes North American VAC Power and Plug


0009AF Model # ACC-1314, Interface Cable, Serial EA $ 30.30 Destination

4 SOFTWARE

RFID V Software

Savi’s established history of successfully partnering with the DoD has led to an integrated COTS software offering that speaks directly to the supply chain and asset tracking needs of the DoD.

The Savi Team’s extensive and unique background in Military logistics, AIT, and the Radio Frequency In-Transit Visibility (RF-ITV) network sets the stage for a commercially competitive software solution that exceeds the requirements of RFID-V. DoD began using Savi software in 1997, starting with an industrial computer running our Retriever software. The application was the original COTS standalone, unattended aRFID transponder data collection and interrogator control system deployed by the US Army, supporting the first ITV server in Germany.

4.1 Software Desirable Features


Revision v8 of 65

Our software addresses the additional features the DoD requested for their RFID-V applications, and these features are ready now. The SmartChain® products proposed under the Software (CLINs) include various characteristics to support all of the DoD’s desirable features. These products are integrated seamlessly and transparently for the user or application developer.

4.1.1 Edge Applications

Savi provides a suite of Edge Applications that work directly with the hardware provided as part of our offering.

Common Application Interface (CAI) Driver is provided with all interrogators. Software developers can use the CAI interface to access the basic ISO 18000-7 features specified by the Government. The drivers also interface with the Total Asset Visibility (TAV) Table Manager Module (TMM) to provide a common format for writing data to the transponder.

SmartChain® Workstation supports reading and writing of shipment manifest and asset attribute information to an ISO 18000-7:2008 and INCITS 256 transponder using a tablet or PC. In conjunction with SmartChain® Site Manager, this product fulfills the requirement for the PC Edge software defined in PWS, Attachment 12. It supports both hardwire and interrogator interfaces, including the compact SMR-650 with USB. For DoD operation, it provides full TAV data management capabilities and is capable, out-of-the-box, of interfacing with the RF-ITV server. SmartChain® Workstation is also designed to operate as a simple application development tool using custom business logic. This product comes pre-installed on the PDK III tablet computer and can run on any other Windows PC.

SmartChain® Site Manager provides AIT Edge capabilities for configuring, managing, collecting, and routing transponder information through a network of interrogators. For DoD operation, this COTS product supports TAV and is capable, out-of-the-box, of interfacing with the RF-ITV server. Site Manager is a middleware component that handles input from multiple AITs including barcodes and pRFID/aRFID transponders. SmartChain® Site Manager is also designed to operate as a simple application development tool using custom business logic. Both SmartChain® Site Manager and Workstation are designed to complement each other and can operate on the same machine. Site Manager also provides the capability to manage and configure the RFID devices and operates as a configuration utility for the interrogator as specified in Attachment 12.

Product Firmware is downloadable to all active transponders and interrogators allowing for full flexibility. Through firmware changes the Government is ensured that their investment evolves with the ever-changing military mission. All products will be delivered with the current version of firmware.

The functional requirements specified by the Government in Attachment 12, Active RFID-V


Revision v8 of 65

Software Functional Requirements, include reading and writing data to transponders using the over-the-air protocol and the defined hardwire interface. The document also describes the data collection, query, and barcode functionality requirements for mobile device platforms. Savi software meets all these requirements, along with the data input, validation, and file transfer features. Our software solutions are deployable on Day 1 of the contract.

4.2 Security Features

The information below provides the Government with our understanding and compliance with the security directives discussed in the Statement of Work (SOW).

Security Standards: Savi’s products fully comply with the applicable standards required by the DoD.

Our software works with approved DoD products that meet the IA requirements.

DoD Wireless Device and Army Wireless Device Security Requirements: Savi is providing software and hardware products that support the DoD and Army wireless policies where required. Our proposed devices meet the DoD requirements, including the FIPS-140-2 Level 2 security certification standard where applicable.

Software Warranty: Savi software warranty support includes defect repairs required to maintain the software in an operational state as sold. This warranty does not include new features, nor does it guarantee compatibility with future versions of Operating Systems, third-party software, or newer hardware products. Defect repairs are delivered to customers as either a revision to the product or as a new product that is functionally equivalent. The original product warranty entitlement transfers to the new product and lasts for the original warranty period. The new product may have updated system requirements such as support for newer operating systems that may require customers to update their systems.

5 USER ORDERING PROCEDURES

5.1 General Contract Information • aRFID-V is a De-centralized IDIQ Contract

o All Federal Contracting Officers have delegated procurement authority to place Task Orders/Delivery Orders against this aRFID-V FFP IDIQ contract; includes: Contracting Officers Authorized Government credit card holders

• Contract Number: W52P1J-20-D-0034


Revision v8 of 65

• Contractor o Name: Savi Technology, Inc. o Address: 3601 Eisenhower Ave, Suite 280, Alexandria, VA 22304-6457 o CAGE Code: 0J463 o NAICS: 3344111, Small Business o Program Manager: Rosemary Johnston, [email protected]; 571-227-7918 o Credit Card Orders POC: Jennifer Sarles, [email protected]; 571-227-7920 o Customer Service and Support: 1-888-994-7284, [email protected]

• Ordering Periods o Base Year: 17 July 2020 to 16 July 2022 o Option Year 1 (if exercised): 17 July 2022 to 16 July 2023 o Option Year 2 (if exercised): 17 July 2023 to 16 July 2024

• Per Order Limitations (Unless accepted by Savi) o Minimum: $50 order for product, $300 order for Service o Maximum: $5 million order for a single item, $10 million for combination of items

• Orders must comply with Terms and Conditions of the Base Contract

5.2 Delivery Order (DO) and Task Order (TO) Request Packages • Packages should include:

o Funding Document o Service Contract Approval Form (SCAR), if required o Independent Government Cost Estimate (IGCE)

Based on Contract Pricing o Description of Required Supplies and/or Services

For TES, must include SOO, PWS, or SOW o AT/OPSEC Coversheet, if required

5.3 Ordering Process through Contracting Office

mailto:[email protected]


Revision v8 of 65

Figure 4: The ordering process through contracting office

5.4 Delivery Requirements • Hardware

o Normal: Within 60 days after date of order, unless later delivery is identified on the order, except for items under CLIN 0008. CLIN 0008 within 90 days after date of order, unless later delivery is identified on the order.

o Expedited: Within 7 (CONUS) or 14 (OCONUS) after date of order; Note: prior approval required

• TES o Period of Performance (PoP) to be defined in Task Order o PoP cannot extend beyond 12 months from contract expiration without ACC-RI

PCO approval

5.5 Inspection/Acceptance • Inspection/Acceptance (I/A) for CLINs 0003, 0004, 0005 and 0006 is to be performed at

Origin by Defense Contract Management Agency (DCMA) by DCMA Manassas (S2404A)

• All other orders: Inspection/ Acceptance to be performed at Destination by using activity representative named in order.


Revision v8 of 65

5.6 Invoicing and Billing • The use of Wide Area Workflow (WAWF) is required • Orders shall be awarded per the Appropriate CLIN/SLIN listed in the Contract • Prices are FOB Destination • Designated Pay Office

o DFAS Columbus Center South, DoDAAC HQ0338 is the designated Pay Office o An alternate DFAS Pay Office can only be used if the Government Ordering

Contracting Officer authorizes the use on an individual order

6 RECOMMENDED EQUIPMENT CONFIGURATIONS • aRFID

o Used for assets within customer-owned facilities and/or at specific locations where readers can be set up Yards Warehouses Gates Doorways Along roads at specific locations

o Used for cargo tracking between specific facilities where readers can be set up Fixed infrastructure at customer facilities Fixed infrastructure at ports Mobile capabilities at chokepoints

o Low data and usually lower tag cost but higher install cost Interfaced with customer’s networks and systems Longer battery life than alternatives

o Familiarity of RFID by user base Users understand benefits Users are familiar with hardware used

6.1 Technical Engineering Services (TES)

RFID V CLINs, TES


Revision v8 of 65

0011 Technical Engineering Services (TES): To include Research, Design, Planning, Integration and implementation of a project from "cradle to grave". Technologies interfacing w/ Active RFID could include: Bar coding, UID, Passive RFID, and memory buttons. Cost will be based on extent of project. - Individual TES CLINs/SLINs to be assigned at Task Order Level. TES projects may include a combination of the listed Labor Categories.

Project Manager--Contractor Site HR $ 131.07

Senior Programmer--Contractor Site HR $ 131.07

Systems Analyst--Contractor Site HR $ 93.27

Software Systems Engineer--Contractor Site HR $ 93.27

Programmer/ Analyst--Contractor Site HR $ 109.73

Junior Programmer--Contractor Site HR $ 88.61

Senior Systems Engineer--Contractor Site HR $ 139.23

Data Comm/Network Specialist--Contractor Site

HR $ 115.22

RF Technical Radio Specialist--Contractor Site

HR $ 104.24

Technical Writer--Contractor Site HR $ 49.38

6.1.1 Approach to Providing Turn-Key Solutions

The Savi Team couples our highly knowledgeable Services and Support organization with our team members’ use of industry standard methodologies and lessons learned from the deployment of AIT worldwide to deliver effective and efficient Turn-key Solutions to the warfighter. We are pleased to present our methodology and the Technical Engineering Services (TES) required—delivering a complete solution.

6.1.2 Methodology and Process

Proven Processes and Methodologies • Lowest risk, best value solution • Retention of current RFID-III staff • Highly refined Integrated Project Lifecycle

Management methodology • Use of SDLC principles and CMMI standards • Use of templates and tools to ensure

repeatable, efficient solution deployment • Ready now, turn-key solution out of the box


Revision v8 of 65

The Savi Team delivers a mature implementation methodology, supported by proven processes and highly refined consulting tools. Figure 5 represents our Integrated Project Lifecycle Management (IPLM) methodology, developed through hundreds of implementations around the world, and centered on generating business value and mission success. In addition to our IPLM, based on IEEE/ISO/IEC 12207, the Savi Team uses System Development Lifecycle (SDLC) principles and CMMI standards for implementation and integration of aRFID, pRIFD, GPS, and GPRS solutions. This methodology creates procedures, templates, techniques, and tools for repeatable, efficient solution deployment. This solid combination allows our customers to realize maximum benefit from their infrastructure investment, with system deployment in the shortest possible time at the most reasonable cost, and with the least amount of risk.

Figure 5: Our Delivery Methodology

Savi uses a process that has been repeated on hundreds of projects.

The Savi process is straightforward and consists of seven building blocks described in the following sections.

Project Initiation is the kickoff for the overall project. Upon award of the task order, the Project Manager begins to implement the internal structure for management of the project along with execution of the initial customer facing activities. The key activities are:

• Customer Project Kickoff: The Project Manager meets with the customer to identify the customer’s key participants and stakeholders in the solution development activities. For a successful project, customer participants need to include those who are directly responsible for each type of activity in the processes to be impacted by the solution.

• Project Planning: The Project Manager develops a detailed project plan, project schedule (work breakdown structure using MS Project), and a cost breakdown. Based on the work breakdown structure, the Project Manager identifies the internal and external (partner) resources required to support the project.

The Business Analysis phase is where the detailed As-Is and To-Be states are defined. This analysis encompasses both the process activities and the infrastructure required to support the customer’s end goals.


Revision v8 of 65

The key activities in the Analysis and Design phase are:

• Business Process Analysis & Functional Requirements Definition: The project team works with key customer users to understand the current business processes, both normal and surge modes. This is done to communicate the Savi Team’s understanding of the current As-Is processes and is used as the baseline to develop the desired To-Be processes. Our Senior Information Systems Engineers use the Business Value Assessment and Functional Requirements Definition templates to support the capture of As-Is processes and resultant requirements. During this process analysis, the use of any current customer applications that replace and/or interface between the new solution and any customer applications are discussed and incorporated into the Functional Requirements Document (FRD). Detailed interface requirements are elaborated in a subsequent Interface Control Document.

• Initial Site Survey: The Senior Information Systems Engineer, RF Technical Radio Specialist and/or Field Service Engineer work with key customers to assess the site locations where the solution is going to be implemented to determine the correct hardware and software to be used. Some of the above information is pertinent to the business process analysis and is documented using Savi’s Site Survey template, which includes site preparation specifications. From the Site Survey, the project team creates a Site Checklist to be used prior to installation of equipment to ensure all necessary site preparation work is completed.

• Server Sizing Discussions: The Software Systems Designers and Senior Software Systems Engineers work with the customer and the customer’s IT department to determine how the new software is to be integrated into the customer’s IT infrastructure. Savi’s Server Sizing Questionnaire is used to discuss and decide on a range of factors that all depend on the size and scope of the solution and is used as the basis for discussions to gather necessary information for the project team to make a recommendation. The information in the questionnaire is input into a sizing model that provides an initial projection of server size requirements.

The Design phase provides the framework to support the detailed solution design activities that are conducted in this phase. The key activities are:

• Solution Design: The conceptual design, finalizing the hardware, software, and general configuration of the overall solution is documented using Savi’s Concept Design Document template. Inherent to the solution design is an Information Assurance Plan that lists the activities that must be conducted to get the solution approved for implementation.

• Interface Control Document: The project team works with the necessary customer organizations to develop the detailed requirements and approach for the system interface(s) and document these requirements using Savi’s Interface Control Document


Revision v8 of 65

template. • Server Sizing Recommendation: A Server Sizing Recommendation is created based

on Savi’s Server Sizing Recommendation template. The recommendation identifies what Savi software is to be implemented and the hardware and third-party software that is required.

• System Design: After the customer accepts the documented results of the above three activities, the project team develops and documents the system design using Savi’s System Design Document template. The system design pulls together the components of the solution and describes the design in detail, including the system architecture. If custom development is required for add-ons to the Savi COTS product(s) and/or for interfaces to external systems, those detailed designs are included.

• Test & Acceptance Planning: After the customer accepts the System Design Document, the project team develops the System Test Plan and Acceptance Test Plan documents based on Savi templates.

The Solution Configuration phase begins with implementation of the To-Be state as documented in the Concept Design Document. The key activities are:

• Solution Configuration: For software projects, the software engineers install in the Savi Solution Center, located in Lexington, KY, an environment replicating (as closely as possible) the customer environment for solution configuration (hardware and software), custom software development, and testing. The software engineers begin the System Configuration document, which describes how the system is to be configured.

For projects requiring custom development, software development begins based on the FRD and Design documents. For custom development requiring a user interface (for example, changes to hand-held user screens), a user interface prototype design is developed iteratively with customer demonstrations to communicate approach and get validation. Frequent meetings are held with key customer participants during all solution configuration and extension activities to prototype and demonstrate solutions (in field trials, where possible) in an iterative fashion to refine requirements and mitigate risk.

• Internal Solution Testing: Prior to implementing at the customer site, the project team tests the solution in the Solution Center to verify it meets the customer requirements and is ready to implement. Testing utilizes the Test Plan Document developed in the prior phase, results are documented, and adjustments are made as necessary until the Test Plan is successfully completed.

• Training Development: The project team develops a draft outline of concepts to cover with each type of user, which typically fall into one of the following categories: users, super users, administrators, and hardware maintainers. If it is a customer requirement as a part of the SOW, Quick Reference sheets and/or User Training Guides with detailed instructions are developed on how to perform necessary tasks. All training


Revision v8 of 65

documentation is in a draft format at this phase, to be finalized after the solution is installed in the customer environment.

• Customer Environment Preparation: The project team works with the customer to ensure the environment that hosts the solution (both the IT infrastructure requirements and site preparations) is ready for implementation. Our staff travels to the customer site and does a physical walkthrough with the customer using the Site Survey Checklist to validate all required site prep work is complete.

The project enters the Installation and Integration phase when the solution (hardware, software, and interfaces) is installed at both the customer facility and the sites in order for the solution to proceed through installation verification testing and user acceptance testing which ends with customer acceptance. The key activities are:

• Solution Installation and Alpha Testing: The project team goes to the customer site to install and configure the software and hardware. The initial installation is done on the staging environment. During installation, the solution analyst, software engineer, and hardware engineer complete the System Configuration Document and make any necessary changes to the Test Plan. The team uses the Test Plan to test the solution to ensure proper operation of the system in the staging environment.

Testing is when the solution (hardware, software, and interfaces) proceeds through installation verification testing and user acceptance testing and ends with customer acceptance. The key activities are:

• Integration Testing: The project team ensures proper operation of the system prior to integration testing. The Test Plan includes a section specifically for integration testing. The team works with the customer organization responsible for the AIS to test the integration capabilities according to the Test Plan in the staging environment. A test is conducted in the AIS test environment and demonstrated to the appropriate key customer participants to ensure the solution meets the requirements.

• User Training and Acceptance Testing: Savi conducts training with the identified users. A final set of tests from the Test Plan are conducted with the customer who does the final acceptance. Results are documented and presented to the customer for acceptance of the delivered solution. Both parties concur on the Go Live date.

Roll Out and Go Live Support begins after the solution finishes Customer Acceptance and is ready to Go Live. Our staff is onsite to provide support by assisting users, answering questions, and troubleshooting, as required.

Transition to Support is when the Savi project team begins a roll off and a formal transition to the Savi Customer Support organization occurs. The Savi Project Manager, Savi Customer Support team lead, and the customer meet to finalize the transition. Savi uses a Customer


Revision v8 of 65

Support Transition Checklist to ensure consistent project transition to the Customer Support team.

Summary

The Savi Team has the requisite experience and essential skills to design, deliver, and sustain Turn-key Solutions for the Government. Our methodology and constantly evolving processes are honed through years of experience with RFID and AIT. The Savi Team understands the value of employing various RFID technologies that meet the needs of the warfighter towards improving asset visibility, providing more reliable logistics information, and enhancing supply chain situational awareness.

rfid v user guide - usarmyamis.army.mil · • rfid-tagged assets will be loaded or discharged from...

Documents