Attachment_0012_aRFID V Software Functional Requirements.docx

Attachment_13 RFID-V Software Functional Requirements Version 5.0 15 June 2018 Introduction This document outlines the major functional requirements of the Active RFID software associated with DoD ISO 18000-7:2008 compliant equipment. PC software includes applications that write data to transponders over a hard-wire interface and over the air using an interrogator, applications that collect transponder data and forward it to a regional server, and applications used to set up and configure interrogators. Hand-held software includes applications to collect and query transponder data, to read bar codes, and to print shipping labels.

Normative references The following documents are applicable to this document:

ISO/IEC 18000-7:2008 Information technology — Radio frequency identification for item management — Part 7: Parameters for active air interface communications at 433 MHz

· DoD Over Air Interface Guidelines

· DoD Transponder Barcode Labeling Guidelines

· DoD Transponder Hardwire Electrical Interface and Data Protocol

· DoD Interoperability Guidelines for the Over Air Interface

· Description of DoD Table Manager Module (TMM)

· Table Manager Module Developer’s Guide

· DoD Active RFID Common Abstraction Interface Developer’s JavaDoc

· DoD RFID Common Abstraction Interface Developer’s Guide

· DoD Routing Code Guidelines

· Active RFID Tag Format and Data Specification JDTAV V2.5

· JD TAV 2-5 RF Tag Format Version 2.5 (ISO Tables)

· RFID-V ITV Server Interface Document

· RFID-V ITV Server Interface Addendum

Functionality Required of Active RFID Software

· Interrogator configuration utility, applies to both fixed and handheld interrogators (allows user programming of non-volatile interrogator configurable parameters)

· Allows for interrogator configuration parameters to be adjusted

· Settings shall be stored in non-volatile memory

· Configuration parameters shall include (minimally)

· Local RF regulated parameters (i.e. maximum transmit power, duty cycle, etc.)

· Vendor specific collection tuning parameters

· A GUI interface for viewing / setting configuration parameters

· PC Edge Applications (minimum requirements)

· Host PC single solution software

· Shall support all PD AMIS approved Host PC operating systems

· Registration to the proper Regional In-Transit Visibility (RITV) server

· Reference RFID-V ITV Server Interface Document (Note: This document is the authoritative document that provides the names and lengths of fields associated with data posted to the regional server).

· Shall use the Table Manager Module (reference DoD Table Manager Module) and use the CAI (reference DoD Active RFID Common Abstraction Interface, DOD RFID Common Abstraction Interface Developers JavaDoc, and DOD RFID Common Abstraction Interface Java Library) to access RFID hardware

· Transponder Write Station Application shall additionally support

· Both over-air and hardwire writes and reads of DoD ISO 18000-7:2008 active transponders

· Posting to the ITV network the associated shipment data and transponder unique ID following the successful writing of new data to a transponder. The posted data duplicates the data written to the transponder for the case where the transponder has sufficient memory to write the full data set. For the case where data written to the transponder is truncated due to insufficient memory, the full data set is posted to the ITV network.

· GUI (Graphical User Interface) that supports the following

· User input of Write Station registration information

· Write Station Type

· Site/Post Location (this text field is used to group all write stations and interrogators at a site to the Site/Post location)

· Latitude / Longitude

· Provide a means to determine this from the application (web link)

· Provide means to query GPS enabled interrogator for Lat/Long coordinates

· Interrogator Name and Description Listing (of all interrogators attached to this write station)

· Interrogator Name includes a name field, a 1 character type field (“R” for Read, “W” for Write), and a 1 to 3 character numeric Sequence Number (1-999)

· Interrogator Description is a text field with no punctuation marks (i.e. no commas, dashes, colons, semicolons, or periods). Space characters are allowed. The Interrogator Description shall be unique to the site.

· Unique Infrastructure Device Identifiers

· For a write station this is the MAC address of first network adapter, reported as a hexadecimal string prefixed with a “T”, for example:

· For an interrogator, its unique infrastructure device identifier shall be read by the application from the interrogator interface (Reference CAI documentation).

· POC Name (mandatory field)

· POC Telephone 1 (mandatory field)

· POC Email Address (optional field)

· User input for station registration data needed to upload data to the selected regional server (Refer to RFID-V ITV Server Interface Document and RFID-V ITV Server Interface Addendum)

· Identify regional server to upload data to

· Identify communication method to regional server (network / modem / stand alone)

· Dial-up configuration name for modem connection (connection settings)

· Protocol (HTTPS)

· User setup of upload interval (HH:MM:SS)

· Buffer transponder ID and associated write data for periodic batch upload to regional server

· Proxy information (user input is not mandatory)

· Host

· Port

· Domain

· Realm

· Authentication (user input is not mandatory)

· User name

· Password

· Listing of collected transponders with battery status

· Date / Time of collection

· Ability to turn on/off the beeper on a collected transponder

· Ability to read and display the contents of data fields described in Active RFID Tag Format and Data Specification JDTAV V2.0 and V2.5

· Allow editing / filling in of all fields

· Form-based data entry of all JDTAV data

· Input file selection

· Export of transponder data to TAV files

· Ability to erase and write user data to a transponder

· Ability to read and verify user data written to a transponder

· Maintain association of transponder ID with the lead TCN in the JDTAV data that has been written to it

· Shall not allow data associated with the same lead TCN to be written to multiple transponders.

· Provide a listing of shipment data and associated transponders

· Includes indicating upload status (which shipment data have been successfully uploaded)

· Provide user input to schedule automated posting of shipment data to ITV server

· Ability to perform a user directed posting of the shipment data to the ITV server

· Ability to select a read / write device (from all devices connected to the system) for interaction with transponders

· Ability to read and display GPS location coordinates from connected fixed interrogators that support this functionality

· Ability to select a printing format and print the following to the vendor offered printer

· Print Military Shipping Label (MSL)

· Print generic cargo labels

· Print 1387 labels

· Report generation

· Tabular reports

· Transponder Assignments Report

· Transponder ID, Container ID, and Lead TCN

· Transponder Status Report

· Transponder ID, Battery Status

· Pending Shipments Report

· Creation Date, Lead TCN, Format, Write Status, Transponder ID, Container ID

· Uploaded Shipments Report

· Upload Date, Lead TCN, Format, Transponder ID, Container ID

· ASCII report file generation

· Transponder-TCN report

· ASCII .rpt file (comma separated) generated that contains Transponder ID, Lead TCN, Container ID

· Ability to re-query for devices (interrogators / write devices) attached to the system

· Includes / uses the GOTS generic hardwire transponder driver

· Reference DoD Transponder Hardwire Electrical Interface & Data Protocol

· Ability to configure and read status and data associated with transponders with integrated sensors

· Reference RFID-V DoD Sensor Interface Guidelines

· User interactive operation

· Allow user to manually collect transponders and review transponder data collected

· Include GUI for generating and reviewing the results of queries

· Include count of number of transponders collected

· Shall have a GUI for the following:

· Listing of collected transponders with battery status

· Date / Time of collection

· Unattended Transponder Data Collection Application (Transponder Read Station)

· User input to enter site/interrogator registration details

· For each interrogator, capture the following data elements for registration / configuration:

· Location details (provide user input fields to enter strings for the following)

· Interrogator Location Name

· Interrogator Location Description

· Latitude / Longitude

· Provide a means to determine this from the application (web link)

· Application shall have ability to query GPS enabled fixed interrogators for GPS coordinates

· Unattended Collection Schedule (provide user input fields for the following)

· User configured number of collection retries after the last collect command where no transponders signals are detected (default of 3 with 0 being a valid value)

· For a simultaneous interrogator network

· Select schedule type for each interrogator on the network (one of the following)

· Periodic reads (specify frequency in HH:MM:SS)

· Default frequency—5 minutes (user settable)

· If the collection takes longer than the specified Periodic reads frequency then the next collection starts as soon as the previous collection is finished.

· Disabled

· For a sequential interrogator network

· Periodic reads (specify frequency in HH:MM:SS) this is the total period for all interrogators operating on a sequential network

· Default frequency—5 minutes (user settable)

· If the collection takes longer than the specified Periodic reads frequency then the next collection starts as soon as the previous collection is finished.

· Interrogator order is selected by the user. This is the order that the readers will perform their operations

· Disabled

· Select Interrogator Cycle Type

· Wakeup and Collect (default)

· Collect only

· Wakeup only

· User input for entering DODAAC List for Interrogators

· Ability to add to and delete from the list

· User input to enter strings for station registration information

· Interrogator listing (auto-populated)

· Site/Post Location

· POC Name

· POC Telephone

· POC Email Address

· User input for information needed to register with and upload data to RF-ITV server (Refer to RFID-V ITV Server Interface Document and RFID-V ITV Server Interface Addendum)

· Identify regional server for uploads

· Identify communication method (network / modem / stand alone)

· Dial-up configuration name for modem connection

· Protocol (HTTPS)

· Define schedule for upload interval (HH:MM:SS)

· Proxy information (user input is not mandatory)

· Host

· Port

· Domain

· Realm

· Authentication (user input is not mandatory)

· User name

· Password

· Select schedule type for posting data to regional server (one of the following)

· Periodic posts (specify duration in HH:MM:SS)

· Default frequency—30 minutes (user settable)

· Disabled (stand alone mode)

· Log activity for both collections and uploads

· Ability to view logs associated with collections and uploads to the site server

· Support a network of interrogators attached to workstation

· Only a single vendor’s interrogators shall exist in a given workstation’s network

· Each Interrogator on the network shall be able to be individually controlled by the application software

· Interrogators on the network shall be able to be configured:

· to send only wakeup signals.

· to send wakeup and collect commands

· to send only collect commands

· Interrogators on the network shall be able to perform operations either sequentially or simultaneously.

· Simultaneous operation means all commands shall be executed by all interrogators on the network at the same time.

· Sequential operation means that the interrogators will perform their operations in an order specified by the user (e.g. interrogator 1 performs a collect then after interrogator 1 has finished its operation, interrogator 2 performs a collect etc.)

· Ability to run as a system service (unattended mode)

· Can be configure d to automatically restart if the power to the host system is cycled

· Ability to collect and pass on routing code and sensor status data to the ITV network

Host System (Handheld)

· Operating System

· Uses a current IA compliant (supports CAC authentication) mobile operating system, Windows Mobile 6.5 or later

· Hardware requirements adequate for execution of all RFID related software

· Reference: See PWS “Active Hand-Held Interrogator” for further details on handheld hardware requirements

· SDK available from handheld manufacturer OEM for integrated 2D symbologies imager (barcode scanner) and accessing integrated GPS information. If integrated GPS information is not available from the handheld device, the vendor CAI compliant driver shall still implement the related call as defined in the CAI to inform the calling application.

· The HHI will support a Java Virtual Machine (JVM) that conforms to the Java Connected Device Configuration (CDC) 1.1 specification or higher.

· Handheld application

· Shall use the Table Manager Module and CAI to access RFID reader, 2D symbologies imager, label printer, GPS, and CAC card reader hardware. The vendor’s CAI compliant driver implementation shall provide the application software access to communicate with these integrated hardware devices. For example:

· To allow application to access results of bar code scans

· To allow application selection of RF transmit power

· To allow application access to current location coordinates

· Batch handling of interrogated transponders (allow for collection of transponder data in disconnected mode with delayed posting to the ITV server when device is later connected to a host PC)

· Delayed posting of transponder information to the ITV server will be a user initiated action

· Can communicate to a host PC or server via USB (ActiveSync or equivalent)

· Can communicate to a host PC or server via secure 802.11 (b/g) WiFi network connection, FIPS 140.2 (Security Requirements for Cryptographic Modules) compliant

· Write functions

· Shall support over-air transponder writes

· Posting shipment data to the ITV network (batch or direct) through host PC connection

· Delayed posting of transponder information to the ITV server will be a user initiated action

· For transponders with integrated sensors be able to write configuration files to the transponders

· For transponders with integrated sensors be able to send arm/disarm commands to the transponders and read/display current sensor status

· Shall have a GUI that performs the following

· Listing of collected transponders with battery status

· Date / Time of collection

· Ability to turn on/off the beeper on a collected transponder

· Ability to read and display the contents of data fields described in Active RFID Tag Format and Data Specification JDTAV Version 2.0 and 2.5

· Allow editing / filling in of selected fields

· Form-based data entry of selected JDTAV data

· Input file selection

· Export of transponder data to TAV files

· Ability to erase and write user data to a transponder

· Ability to read and verify user data written to a transponder

· Maintain association of transponder ID with the lead TCN in the JTAV data that has been written to it

· Shall not allow data associated with the same lead TCN to be written to multiple transponders.

· Provide a listing of shipment data and associated transponders

· Includes indicating upload status (which files have been successfully uploaded)

· Ability to perform a user directed posting of the shipment data to the ITV server

· Read functions

· Attended (user directed) operation

· Shall have a GUI for the following:

· Allow user to manually collect transponders and review transponder data collected

· Listing of collected transponders with:

· Battery status

· Date / Time of collection

· Ability to perform standard point to point / broadcast commands to collected transponders

· Ability to create, execute, and display the results of a query

· Ability to configure and read status and data associated with sensor transponders

· Reference DoD Sensor Interface Guidelines

· Read date, time, event descriptions from event logs on sensor and intrusion detection transponders (transponder arming, disarming, alarm, etc., events) and save these to a file for later upload to ITV Server

· Read histogram data from sensor and intrusion detection transponders and save to a file for later upload to ITV Server

· Shall integrate the functionality provided by the integrated 2D symbologies imager (barcode scanner) and integrated GPS hardware

· Hardware CAI driver implementation (vendor SDK) for PC (reference CAI documentation)

· Implement all ISO specific methods within the defined software interfaces

· Provide listing of any custom exception messages with descriptions

· Hardware CAI driver implementation (vendor SDK) for Handheld

· Implement all ISO specific methods within the defined software interfaces

· Provide handheld device preconfigured to use vendor driver

· Provide listing of any custom exception messages with descriptions

RFID-V Software Functional Requirements – Version 5.0