OAT Asset Tracking. Installation and Configuration Guide. Document Number: OAT_AT_ICG_51

Transcription

1 OAT Asset Tracking Installation and Configuration Guide Version 5.1 May 2010 OATSystems, Inc Document Number: OAT_AT_ICG_51

2 Copyright 2010 OATSystems Inc. All Rights Reserved. This document contains proprietary information that is owned by OATSystems. Copying or reproduction of any material from this site to any other location for further reproduction or redistribution is expressly prohibited. Any reproduction or redistribution of the files not in accordance with the terms of the License Statement is a violation of copyright law. OAT and Senseware are registered trademarks of OATSystems, Inc. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. OATSystems is independent of Sun Microsystems, Inc. IBM is a registered trademark of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trade names and trademarks are the property of their respective owners. OATSystems makes no warranties, express or implied, with regards to its products in this document. Support Information You can contact the OAT Support Center (OSC) for technical support at: OATSystems, Inc. OATSystems, Inc. 309 Waverley Oaks Road, Suite 306 Waltham, MA Phone: 877-OAT-SUPPORT or Fax: info@oatsystems.com Web site: OAT Asset Tracking Installation and Configuration Guide ii

3 Table of Contents Chapter 1 Pre-requisites OAT Asset Tracking Distribution Contents Installation Overview...8 Chapter 2 Installing the Asset Tracking OAR Files Deploying OAT Asset Tracking Logging on to the OATxpress Web Application...9 Chapter 3 Configuring Scenarios and Reports The OATtrack Scenario OATtrack Configuration s OATtrack Directionality OATtrack Directionality Configuration s OATtrack Mobile OATmobile Configuration s OATpack OATpack Configuration s Advance Shipping Notice (ASN) ASN document Properties VisibleEdge Attribute capture/ validation Reconcile Acknowledgement ASN Scenario Configuration s OATship OATship Features OATship Configuration s Label Print Scenario Label Print Scenario Configuration s Configuring Reports...67 Chapter 4 Configuration for Zoning and Visualization Introduction Pre-requisites Map Configuration Types of Calibration...73 OAT Asset Tracking Installation and Configuration Guide 3

4 4.4.1 Pre-calibrated CalibrationByExample Zone Configuration Attributes on <Zone> tag Navigation Tag ZoneConfig Tag BusinessLocationHierarchy Tag RPMapping Tag Visualization Properties Configuration...78 Chapter 5 Installing and Configuring on a Handheld Device Pre-requisites Installing OAT Asset Tracking s handheld application Configuring OAT Asset Tracking Handheld Application Message Information...90 OAT Asset Tracking Installation and Configuration Guide 4

5 Preface The OAT Asset Tracking Install Guide describes the requirements and procedures for installing OAT Asset Tracking, and the procedures for configuring additional software as needed. Assumptions The OAT Asset Tracking Install Guide assumes the following: All software and hardware requirements for installing OATxpress have been met. The user has administrative privileges on the local host machine. Additional Documentation OAT, Inc. customers and partners can log on to to access product release notes, hardware configurations for supported devices, and other information related to OAT products Document Conventions Following are the formatting conventions used in this document: Code Examples Examples from an actual file or a sample command line appears as follows: cd /oat_install_dir/ofs/schema Navigation The 'greater than (>)' sign separates the navigation controls in a sequence to be performed. For example Admin > Users Admin > Users Notes Indicates that you need to click the Admin tab and then the Users icon. Notes convey important information. Following is an example NOTE: In the user interface of the OATxpress Web application, fields with asterisks (*) are mandatory and require users to supply a value OAT Asset Tracking Installation and Configuration Guide 5

6 Cross-references A cross-reference directs you to another location in the document for information. For example: See.Pre-requisites Click the red text, to traverse the link to the referenced location. OAT Asset Tracking Installation and Configuration Guide 6

7 Chapter 1 Pre-requisites This chapter describes the required platform on which you must install OAT Asset Tracking. Before installing OAT Asset Tracking solution, do the following: Install OATxpress on the system in which you want to add Asset Tracking, using one of these supported stacks: o o o Apache Tomcat with MS SQL Server 2005 Express Apache Tomcat with Oracle 11g IBM Websphere Application Server with IBM DB2 Ensure that the OATxpress installation has a valid license key and is working. See the OATxpress Installation and Configuration Guide for details. Login as a user with administrative rights to the local machine. NOTE: The scope of the Install Guide is to explain specific additional steps required to install the OAT Asset Tracking functionality on the OATxpress platform. 1.1 OAT Asset Tracking Distribution Contents The OAT Asset Tracking distribution consists of the following: OATxpress (as mentioned above, you need to have installed this product as described in the OATxpress Installation and Configuration Guide prior to installing Asset Tracking functionality) Microsoft SQL Server 2005 Express (required to be installed before OATxpress, if using this stack) The Asset Tracking OAR files: o o prod-c-assettracking.oar prod-a-primitives.oar The installer file for handheld device(s) specific to each supported handheld cpy,.reg and.lnk files are packaged within the.cab file and are not distributed separately o OAT Asset Tracking.cab A samples.zip file provides examples for OAT Asset Tracking distribution. OAT Asset Tracking Installation and Configuration Guide 7

8 Pre-requisites 1.2 Installation Overview After installing SQL Server 2005 Express and OATxpress, copy the license key and deploy the OAR files. Optionally (if you re using a handheld device) install the handheld Asset Tracking application on each handheld device used. OAT Asset Tracking Installation and Configuration Guide 8

9 Chapter 2 Installing the Asset Tracking OAR Files This chapter explains the procedure to deploy OAT Asset Tracking by installing the relevant OAR files. 2.1 Deploying OAT Asset Tracking To deploy OAT Asset Tracking solution, following steps are to be followed: 1. Stop OATxpress and OATTomcat (or Websphere Application Server) services. 2. The required.oar files are: o o proj-assettracking.oar c-primitives.oar Copy these files to the following location: <OAT_install_dir>\ofs\ext (for example, C:\OATxpress\ofs\ext) 3. In a Command Prompt window type: cd <OAT_install_dir>\ofs\bin (for example, cd C:\OATxpress\ofs\bin) deploy.bat 4. Once the files have been deployed, the message Finished deploy appears. 5. Close the Command Prompt window and start the OATxpress server. 2.2 Logging on to the OATxpress Web Application 1. To open the OATxpress Log In page, in the Start menu click All Programs > OATxpress> OATxpress Server Manager, or type the URL of the OATxpress server in a browser window 2. The initial login username and password for the OATxpress Web application are: Username: oat_test Password: apollo 3. After logging in for the first time, change the password. Create other accounts as required. See the OATxpress User Guide for information on creating users and roles. OAT Asset Tracking Installation and Configuration Guide 9

10 Chapter 3 Configuring Scenarios and Reports A scenario implements a process that is defined as a series of activities and wait states. It specifies a potential or actual sequence of events in the workplace wherever OATxpress is used, and whenever the events involve tagging objects or identifying tagged objects. 3.1 The OATtrack Scenario The OATtrack scenario contains the core functionality to track assets. It allows you to: identify an asset using its EPC or its attributes validate the asset capture and modify asset attributes validate the attribute values of the asset. NOTE: An instance of OATtrack can be used to track only a single Asset Type OATtrack Configuration s Use the following sections to configure parameters prior to running the OATtrack scenario. s listed below correspond to the fields displayed in the configuration user interface. Section 1: Identify Asset How is the asset identified? Specify asset type Choose Search parameters (if identifying asset by search) Select one of the following: RFID reader Barcode scanner UI entry Search - to identify the tag. Select the asset type to be tracked Use the popup window to configure search attributes. This is applicable only if the Search option is selected for the parameter, How is the asset identified? OAT Asset Tracking Installation and Configuration Guide 10

11 Section 2: Link Tags to Assets Specify tag encoding scheme for asset tags Does an asset have multiple tags? Specify multi-tag mask indices Ignore duplicate tag reads, if read within (sec) Send digital output when more than one asset is in the field of the reader Send digital output when EPC mask is invalid (only for multi-tagged assets) Specify the EPC encoding scheme Select Yes if the asset has multiple distinct tags If multiple tags are used, select values allowed in the last hexadecimal digit of the EPC.. If multiple tags are used, more than one tag for the same asset may be read. Configure a time window within which a subsequent read of the same asset will be ignored. Select digital output point and value in the popup window, if tracking multiple assets should cause an alert. Select digital output point and value in the popup window, if an EPC with the wrong mask should cause an alert. Section 3: Define Devices RFID antenna readpoint location Choose from a list of configured read points Barcode scanner for reading asset EPC (if used) Select the barcode scanner to scan EPCs. This is applicable only if you select the Barcode Scan option for the parameter, How is the asset identified? Barcode scanner for capturing attributes (if used) Specify the digital input device for starting and stopping multi asset movement Select the barcode scanner to scan attributes, if attribute capture through barcode is defined. This can be either the same as or different from the barcode scanner that would be used for scanning EPCs. Choose the digital input device that signals the start and end of a batch of assets. The actual signal states for starting and ending the batch are configured in the next section. OAT Asset Tracking Installation and Configuration Guide 11

12 Section 4: Specify Handling of Multiple Assets Configuring Scenarios and Reports Alert if there is more than one asset in reader field Is a photocell or motion detector used to start the scanning process? Specify the digital input trigger state to stop scanning Specify the digital input trigger state to start scanning Stop scanning after a period (configured below)? Stop scanning after the configured time (ms) (if yes is selected above) Scanning will be stopped if a specified number of assets are read Stop scanning if configured number of assets are read (if yes is selected above) User confirmation is required after scanning for all assets Select Yes, if only one asset can be placed before the reader at a time. Select No, if multiple assets can be placed before a reader. All of them are tracked. The default setting is Yes. The default setting is Yes The default setting is On The default setting is On The default setting is No The default setting is 10,000 milliseconds. The default setting is No. The default setting is 1. The default setting is No. Section 5: Specify Location to Assign Asset Should the asset be assigned to a location when validation succeeds? Asset association location when validation succeeds Should the asset be assigned to a location when validation fails? Asset association location on validation failures The default setting is Yes. Select a location to assign when asset validation is successful. The default setting is Yes. Select a location to assign when asset validation fails. This is optional. If no location is selected, the asset location remains unchanged when validation fails. OAT Asset Tracking Installation and Configuration Guide 12

13 Section 6: Actions to Perform on Reading an Asset Tag Reset all asset attributes Alert if the asset has not been seen by the system previously Alert if the asset does not match the specified product Asset SKU (if alert needed on product) Asset Stylecode (if alert needed on product) Asset UOM (if alert needed on product) Alert if the asset has not previously visited the specified location Mandated previous location of asset (if alert needed on previously visited location) Alert if the asset attributes do not match this rule Send digital output signal when EPC is invalid Send digital output signal when product does not match Send digital output signal when asset did not visit previous location Select Yes to reset values of all attributes to null. Select Yes to fail tracking if the EPC is unknown. Select Yes to fail tracking if the EPC does not belong to a specific product. Specify the SKU of the product. This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Specify the style code of the product This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Specify the UOM of the product. This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Select Yes if validation should succeed only if the asset has visited the specified location. Specify the location to check for (if the earlier parameter is Yes) In the popup window, specify attribute validation rules on the asset's current state. In the popup window, select digital output point and value, if an invalid asset EPC should cause an alert. In the popup window, select digital output point and value, if an asset EPC with invalid product should cause an alert. In the popup window, select digital output point and value, if asset EPC not visiting a required previous location should cause an alert. OAT Asset Tracking Installation and Configuration Guide 13

14 Section 7: Define Attribute Modifications Configuring Scenarios and Reports Want to capture attributes every time an asset is read? Specify timeout for attribute capture through UI and Barcode (ms) specifying 0 disables timeout Capture these attributes every time an asset is read Alert if the captured (by UI) attributes do not match this rule Alert if the captured (by Barcode) attributes do not match this rule Alert if the captured (by External system) attributes do not match this rule Modify these attributes for every asset Select Yes to capture attributes for every asset. Specify the timeout in milliseconds within which attributes via user interface or barcode should be captured. Configure attributes and mode for capture in the popup window. In the popup window, validate attributes after capturing them through the user interface. In the popup window, validate attributes after capturing them through a barcode scan. In the popup window, validate attributes after capturing them through an external system. Specify values for the constant attributes (attributes that need to be applied with a specific value for every asset). Section 8: Validate Modified Attributes Alert if the modified attributes do not match this rule Send digital output when validation fails Send digital output when validation succeeds Validate attributes after obtaining all attributes, including constant attributes. In the popup window, select digital output point and value, if attribute validation failure causes an alert. In the popup window, select digital output point and value, if attribute validation success causes a signal. OAT Asset Tracking Installation and Configuration Guide 14

15 Section 9: Define External System Integration s Specify location identifier to be sent to external system Specify the value to be sent as identifier to external system Target end point for SOAP service Action URI for SOAP service Specify timeout for SOAP service (ms) Send digital output when web service fails Choose from the location name as configured in OFS, the Location EPC as configured in OFS, or any user-defined value (defined in the next setting). Type a value to be sent to the external system, if a user-defined value has been selected above. Select the end point address for the SOAP service, for example, Service This value is currently not used and need not be configured. Type a value to enable scenario execution to continue if the SOAP service does not respond within the set number of milliseconds. When the SOAP server fails to respond, it delays scenario execution significantly. In the popup window, select digital output point and value, if web service failure should cause an alert. Section 10: Define User Interface Look and Feel Select the attributes to display on the screen Does the operator need to confirm after changing asset attribute? Action before clearing the screen for next asset In the popup window, select attributes to be displayed on the screen. Select yes for a confirm button to appear for the operator, before committing changes. Select No delay required - to reset the user interface after an asset is tracked. Select Wait for user acknowledgment - to click a button that resets the user interface. The scenario then expects the next asset. OAT Asset Tracking Installation and Configuration Guide 15

16 Select Pause for a configured time - to introduce a time delay. The user interface resets after the specified time delay. The scenario then expects the next asset. Specify pause time before clearing screen for next asset (ms) Specify a value here, if you have selected pause in the previous parameter. Section 11: Miscellaneous Send digital output on unknown error In the popup window, select digital output point and value, if any unhandled error should cause an alert. 3.2 OATtrack Directionality The OATtrack Directionality scenario is an extension of the OATtrack scenario without user interface. This scenario is generally deployed at locations where bi-directional movements of assets (such as shipping/receiving dock doors and portals) are expected OATtrack Directionality Configuration s This section lists the parameters to be configured for running the OATtrack Directionality scenario. Section 1: Determine Asset Movement Direction Specify parameters for direction inference Ignore multiple reads of same asset, if read within (sec) Configuration is through a popup window. See Section 1.1: Directionality Algorithm and Rules Configuration for details. The asset may be read more than once depending on reader position and speed at which the asset moves. Specify the time in seconds within which the subsequent read of the same asset will be ignored. OAT Asset Tracking Installation and Configuration Guide 16

17 Section 1.1: Directionality Algorithm and Rules Configuration Direction inferred by Default Direction Select one of the following: Reader Previous location of tag Reads at multiple readpoints Motion Sensor Assigns a direction to an EPC that is either new to the system or if the direction inference algorithm is unable to decide the direction. NOTE: Selecting UNKNOWN prompts the user for direction of assets, if the algorithm is unable to determine the direction during execution. Since the current OATtrack Directionality scenario intends to avoid all user interaction steps, selecting UNKNOWN as the default direction should be avoided as well. If the asset direction inference algorithm chosen is Reader If the asset direction inference algorithm chosen is Previous location of asset If the asset direction inference algorithm chosen is Reads at multiple antennas If the asset direction inference algorithm chosen is Motion Sensor See Section 1.1.1: Rules Configuration for Reader based Directionality Algorithm. See Section 1.1.2: Rules Configuration for Previous location of asset based Directionality Algorithm. See Section 1.1.3: Rules Configuration for Reads at multiple readpoints based Directionality Algorithm. See Section 1.1.4: Rules Configuration for Motion Sensor based Directionality Algorithm. Section 1.1.1: Rules Configuration for Reader based Directionality Algorithm Direction Device Direction IN and OUT; will be the inferred direction. Device event for direction inference. The event OAT Asset Tracking Installation and Configuration Guide 17

18 name is based on the device. Section 1.1.2: Rules Configuration for Previous location of asset based Directionality Algorithm Direction IN and OUT; this will be the inferred direction. Previous Location Select one or more locations to be considered as previous locations. NOTE: If a parent location consisting of multiple child locations is selected, all child locations are to be considered as previous locations. Previous Location for IN and OUT cannot be the same. None; cannot be selected as it does not imply any location. Section 1.1.3: Rules Configuration for Reads at multiple readpoints based Directionality Algorithm Direction First Read IN and OUT Select Read Point 1 or Read Point 2. The actual read point will be configured later in Section 3 Define Devices. If the First Read was Read Point 1 then the next has to be Read Point 2 and Vice Versa. They cannot be same for both IN and OUT. Next Read Select Read Point 1 or Read Point 2. The actual read point will be configured later in Section 3 Define Devices. OAT Asset Tracking Installation and Configuration Guide 18

19 NOTE: If the First Read was Read Point 1 the next has to be Read Point 2 and Vice Versa. They cannot be same for both IN and OUT. Min. time diff Specify the minimum time in milliseconds to move from First Read to Next Read. NOTE: Reader device has to be configured correctly for this to work. A reader in polling mode should have a Time between reads (ms) value lesser than this parameter s value. Please refer to OATxpress User Guide for configuring devices. Max. time diff Specify the maximum time in milliseconds to move from First Read to Next Read. NOTE: Timeout event is created as soon as the first tag is read. This timeout logically groups the tag reads in case of multiple asset reads into a batch. If other timeouts/ batch quantity is configured then this event will affect them. Section 1.1.4: Rules Configuration for Motion Sensor based Directionality Algorithm Direction Motion Sensor IN and OUT Select Motion Sensor 1 or Motion Sensor 2 for IN and OUT direction. NOTE: They cannot be same for both IN and OUT. State Timeout Select ON or OFF Specify the timeout in milliseconds to wait for the event. The EPC read event is expected within this time. NOTE: Timeout event is created as soon as the first tag is read. This timeout logically groups the tag OAT Asset Tracking Installation and Configuration Guide 19

20 reads in case of multiple asset reads into a batch. If other timeouts/ batch quantity is configured then this event will affect them. Section 2: Link Tags to Assets Specify asset type Select the Asset type to be tracked. NOTE: Select ALL if the attributes of the asset need not be captured. Specify tag encoding scheme for asset tags Does an asset have multiple tags? Select the EPC encoding scheme. Select Yes, if the asset has multiple distinct tags NOTE: Multiple tags on asset are used in the case where there is a possibility that a single tag may or may not be read. Specify multi-tag mask indices Ignore duplicate (multi-tagged) tag reads, if read within (sec) Send Digital output when EPC mask is invalid (only for multi-tagged assets) In the popup window, select the tag indices. If multiple tags are used, select values allowed in the last hexadecimal digit of the EPC. If multiple tags are used, it is possible that more than one masked tag for the same asset is read. Specify the time in seconds, within which a subsequent reads of the same asset will be ignored. In the popup window, select digital output point to which the scenario sends signal for asset with invalid EPC mask. Section 3: Define Devices RFID antenna read point Select from the list of configured read points. This read point is mandatory for all the direction inference algorithms. NOTE: In case of Reads at multiple read points OAT Asset Tracking Installation and Configuration Guide 20

21 algorithm, this is the first Read Point. Second RFID antenna read point (if using multiple read points) Select from the list of configured read points. This read point is necessary only for Reads at multiple read points algorithm, and is the second Read Point. NOTE: This parameter has to be configured only if there are multiple read points. Specify the digital input device for starting inbound asset movement Select from the list of digital input points. This is mandatory for Motion Sensor based direction inference. NOTE: This is Motion Sensor 1 Specify the digital input device for starting outbound asset movement Select from the list of digital input points. This is mandatory for Motion Sensor based direction inference. NOTE: This is Motion Sensor 2 Section 4: Specify Handling of Multiple Assets Track multiple assets? Alert if there is more than one asset in reader field (valid only if above is No ) Send digital output when more than one EPC is in the field of the reader Is a photocell or motion detector used to start the scanning process? Select Yes to track multiple assets in a batch. Select No to track single asset. Select Yes to alert the operator and defer tracking until the other assets are removed from reader field. Select No if it is ok for multiple assets to be present. They will be tracked one after the other and each will be considered as a single asset. The default value is No In the popup window, configure the digital output. This is valid only if Track multiple assets? is set to Yes. The default setting is Yes. NOTE: This is the Digital trigger Batch Processing OAT Asset Tracking Installation and Configuration Guide 21

22 Method. Specify the digital input device for starting and stopping multi asset movement Select from the list of digital input points. NOTE: Used only if Is a photocell or motion detector used to start the scanning process?" is set to Yes. Specify the digital input trigger state to start scanning The default setting is on. NOTE: This specifies the state (on/off) that starts the scanning process. This also helps in grouping the assets read into the batch. Specify the digital input trigger state to stop scanning The default setting is on. NOTE: This specifies the state (on/off) that starts the scanning process. This concludes the batch. Stop scanning after a period (configured below)? The default setting is Yes. NOTE: This is the Time-out Batch Processing Method. Stops scanning after the configured time (ms) (if yes is selected above) Scanning will be stopped if a specified number of assets are read The default setting is 10,000 milliseconds. NOTE: Assets read in the configured time, are grouped in a batch. Select Yes to stop scanning after the specified number of assets is read. Select No to continue reading the assets. The default setting is No. NOTE: This is the Target Quantity Batch Processing Method. Stop scanning if configured number of assets are read ( if yes is selected above) Specify the number of assets to be read before scanning is stopped. The default setting is 1. NOTE: Only configured number of assets will be read and grouped in the batch. Turn on the reader only while scanning for assets The default setting is Yes. OAT Asset Tracking Installation and Configuration Guide 22

23 Section 5: Multiple Assets - Direction Inference Configuring Scenarios and Reports If some of the assets are detected as inbound and others outbound Select one of the following options: Apply the direction of the majority of the assets - direction is inferred by the majority of assets being inbound or outbound. Apply the direction of each asset to consider the direction of each asset. Stop processing to stop the process if both the inbound and outbound assets are detected. Section 6: Specify Location to Assign Asset Specify inbound location to assign Specify outbound location to assign Specify inbound location to assign on validation failures Specify outbound location to assign on validation failures Select the actual location to which the asset needs to be assigned when it is inbound. Select the actual location to which the asset needs to be assigned when it is outbound. Select the inbound location to which the asset needs to be assigned when validation fails. Select the outbound location to which the asset needs to be assigned when validation fails. Section 7: Inbound - Actions to Perform on Reading an Asset Tag Reset all asset attributes Alert if the EPC has not been seen by the system previously Alert if the EPC does not match the specified product Asset SKU (if alert needed on product) Select Yes to set values of all attributes to null. Select No to retain its values. Select Yes to alert and stop tracking, if the EPC is unknown. Select Yes to alert and stop tracking, if the EPC does not belong to the below specified product. Specify the SKU of the product to check for. OAT Asset Tracking Installation and Configuration Guide 23

24 This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Asset Stylecode (if alert needed on product) Asset UOM (if alert needed on product) Alert if the asset has not previously visited the specified location Mandated previous location of asset (if alert needed on previously visited location) Alert if the asset attributes do not match this rule Specify the style code of the product to check for. This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Select the UOM of the product to check for. This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Select Yes to alert, if the asset has visited the current location without visiting the specified previous location. Select the location, if the earlier parameter is Yes. In the popup window, validate the attribute based on the asset s current state. Section 8: Outbound - Actions to Perform on Reading an Asset Tag Reset all asset attributes Alert if the EPC has not been seen by the system previously Alert if the EPC does not match the specified product Asset SKU (if alert needed on product) Asset Stylecode (if alert needed on product) Asset UOM (if alert needed on product) Select Yes to set values of all attributes to null. Select Yes to alert and fail tracking if the EPC is unknown. Select Yes to alert and fail tracking if the EPC does not belong to a specific product. Specify the SKU of the product Specify the Style Code of the product. Select UOM of the product from the list. OAT Asset Tracking Installation and Configuration Guide 24

25 Alert if the asset has not previously visited the specified location Mandated previous location of asset (if alert needed on previously visited location) Alert if the asset attributes do not match this rule Select Yes to alert, if the asset has visited the specified location for the first time. Select the location to check for (if the earlier parameter is Yes). In the popup window, specify attribute validation rules on the asset s current state. Section 9: Actions to Perform on Reading an Asset Tag Send digital output signal when EPC is invalid In the popup window, configure the digital output, to which the scenario sends signal for every asset tag that has failed EPC validation. NOTE: This configuration is applicable to both inbound and outbound assets. Send digital output signal when product does not match In the popup window, configure the digital output, to which the scenario sends signal for every asset EPC with invalid product NOTE: This configuration is applicable to both inbound and outbound assets. Send digital output signal when asset did not visit previous location In the popup window configure the digital output, to which the scenario sends signal for every asset EPC not visiting a required previous location. NOTE: This configuration is applicable to both inbound and outbound assets. Section 10: Inbound/Outbound - Common Actions Specify timeout for SOAP service (ms) The default setting is 60,000 milliseconds. NOTE: This value enables scenario execution to continue if the SOAP service does not respond within the set number of milliseconds. When the OAT Asset Tracking Installation and Configuration Guide 25

26 SOAP server fails to respond, it delays scenario execution significantly. Section 11, 12: Define Attribute Modifications (Specified Independently for Inbound and Outbound Assets) Want to capture attributes every time an asset is read? Capture these attributes every time an asset is read Select Yes to capture attributes. Select No to ignore. In the popup window, select the attributes to be captured. NOTE: User interface and Barcode modes of capture are disabled, since the scenario should run with no user interaction. Only supported mode of attribute capture is via external integration. Alert if the captured (by External system) attributes do not match this rule Modify these attributes for every asset In the popup window, configure validation rules for attributes captured through an external system. In the popup window, select the attributes and enter the value. NOTE: This is the fixed value for selected attributes and can be modified by stopping the scenario and reconfiguring them. Section 13: Validate Modified Attributes Inbound alert if the modified attributes do not match this rule Outbound alert if the modified attributes do not match this rule Send digital output when validation fails In the popup window, validate inbound attributes after obtaining all attributes, including constant attributes. The alert is generated only when modified values are not equal to the values defined. In the popup window validate outbound attributes after obtaining all attributes, including constant attributes. In the popup window, configure the digital OAT Asset Tracking Installation and Configuration Guide 26

27 output, to which scenario sends signal when validation fails. NOTE: Applies to both inbound and outbound assets. Send digital output when validation succeeds In the popup window, configure the digital output, to which scenario sends signal when validation succeeds. NOTE: Applies to both inbound and outbound assets. Section 14, 15: Define External System Integration s (Specified independently for inbound and outbound assets, unless specified otherwise) Specify location identifier to be sent to external system Select one of the following ID values that is sent to the external system: Location name - as configured in OATxpress Location EPC - as configured in OFS User-defined value (below) NOTE: This ID is used by the scenario to identify itself to the Service, which in turn will use it to respond with the appropriate attribute values. Specify the value to be sent as identifier to external system Target end point for SOAP service Specify a value to be sent to the external system, if User defined value is selected above. Specify the end point address for the SOAP service, for example, Service Action URI for SOAP service This value is currently not in use. OAT Asset Tracking Installation and Configuration Guide 27

28 Section 16: Inbound/Outbound Define Common External System Integration s Send digital output when web service fails In the popup window, configure the digital output, to which the scenario sends signal, when web service fails NOTE: Web service may fail due to the following reasons. o o o If service URL is wrong. If service is down. If there is time out. Applies to both inbound and outbound assets. Section 17: Define UI Look and Feel (Configurations apply to both inbound and outbound assets) Select the attributes to display on the screen In the popup window, select the attributes of the asset, to be displayed on the screen. Section 18: Miscellaneous Send digital output on unknown error In the popup window, configure the digital output to which the scenario sends signal for any unhandled error. 3.3 OATtrack Mobile Asset Tracking helps track assets using handheld devices. Operators use the handheld devices at different stations. Operations at the stations are carried out by interfacing with a thick client provided on the handheld device. For mobile track scenarios, just as with OATtrack, a set of business rules is configured in OAT Asset Tracking Installation and Configuration Guide 28

29 OATxpress. The handheld device communicates with the OATxpress server to execute the validations OATmobile Configuration s All configurations are common between Single asset and Multi asset scenarios, except where specified. Section 1: Link Tags to Assets Specify asset type Specify tag encoding scheme for asset tags Select the asset type to be tracked Select the EPC encoding scheme Section 2: Handheld setup Message identifier from mobile device Attributes to be sent from handheld application Specify a User-defined value to identify the message from a handheld device. The same value should be specified in the handheld device configuration file. Specify attribute values captured on the handheld device and sent to the scenario instance. Section 3: Specify location to assign asset Asset association location on validation failures Asset Readpoint location (typically, location created for handheld device) Specify the Location to assign when validation fails. This is optional. If no location is selected, then asset location remains unchanged when validation fails. Specify the readpoint location or station at which this scenario is used. Section 4: Actions to perform on reading an asset tag Do the assets have attributes? Select Yes, if attributes are to be captured at OAT Asset Tracking Installation and Configuration Guide 29

30 Reset all asset attributes Alert if the EPC has not been seen by the system previously Commit only if all EPCs pass validation Alert if the EPC does not match the specified product Asset SKU (if alert needed on product) Asset Stylecode (if alert needed on product) Asset UOM (if alert needed on product) Alert if the asset has not previously visited the specified location Assets previous location (if alert needed on previously visited location) Modify these attributes for every asset Alert if the asset attributes do not match this rule this station. Set values of all attributes to null. Select Yes to fail tracking, if the EPC is unknown. Applicable only for OATtrack mobile in the Multiple Assets scenario. Specify No which ensures that after successful validation, the asset is associated with attributes and location. Select Yes to fail tracking if the EPC does not belong to a specific product. Specify the SKU of the product. This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Specify the style code of the product. This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Specify the UOM of the product. This is applicable only if Yes is selected for Alert if the asset does not match the specified product. Select Yes, if validation should succeed only if the asset has visited the specified location Specify the location to check for (if the earlier parameter is Yes). Specify constant attributes to be applied with a specific value for every asset. Obtain all the attributes and validate them. Validation is done before constant attributes are applied to the currently changed state. During the execution of online-only station, if OATxpress becomes unavailable, the controls which require connectivity to OATxpress are disabled. While running online-only single asset station the Update button and the icon which gets the asset attributes are disabled and the operation is discontinued. For multi-asset station, the Submit button is disabled and clicking on EPC does not display the OAT Asset Tracking Installation and Configuration Guide 30

31 attribute. It reverts back to the main page. In case of Cycle counting, the Search button is disabled. 3.4 OATpack The OATpack scenario allows - grouping or packing process, additions to the pack or group, tracking movement of the group or containees, and the rework of the container. The requirements for enabling the packing and the grouping process are rarely similar. In case of grouping, one entity (e.g. chassis on assembly line) may be considered as container to which other components are added. The packing process can be conducted based on order information using ASN document. Container attributes are also assigned as part of deploying this scenario. The ability to generate and print a label for the container is also supported OATpack Configuration s The configuration parameters for the OATpack scenario are listed in the following tables: Section 1: Identifying Container EPC Specify container asset type Select the asset type from the drop down list. NOTE: Select ALL if attributes need not be captured. Specify the SKU of the container Specify the UOM (unit-of-measure) of the container Specify the Style Code of the container Container EPC encoding scheme Select the SKU from the list to identify the aggregation entity. Select the UOM from the list for the aggregate entity, for example, a pallet. Specify the Style Code for the aggregate entity, for example, a pallet. Select an encoding scheme from the list. NOTE: This is used for a unique EPC to be generated for each container. For pre-encoded EPCs, this is used to validate the EPC and identify it as a container EPC. Should the container EPC be commissioned? If container EPC is pre-encoded, how is the container EPC identified? Select Yes to commission the container EPC. Select No (pre-encoded) to ignore. Select one of the following if No is selected for Should the container EPC be commissioned? : EPC Read to identify the container EPC OAT Asset Tracking Installation and Configuration Guide 31

32 through EPC read Bar code Scan- to identify the container EPC through Barcode scan UI Entry to identify the container EPC through UI entry. NOTE: The appropriate reader/scanner should be configured, if EPC Read or Barcode Scan is selected. If container EPC will be read, select when to read it Select one of the following: In the beginning - to signify that the container EPC is the first EPC and it should be explicitly input, read or barcode-scanned. Anytime during the containee EPC scan - to let the container be either read or inferred from containees any time during the scan cycle. NOTE: This option can work only with EPC input method of EPC Read. At the end - to read a container EPC to signify the end of scan cycle. Once the container EPC is scanned no more EPCs will be scanned. Enter percentage of containees to be read for inferring container EPC (If container not identified at start) Clear existing containees when container is identified? (WARNING: Use Cautiously.) Enter the percentage of containees required to identify the container. Select Yes to unpack all the existing containees that may be present in the container. NOTE: Unpacking refers to database operations within OFS and not physical unpacking of the container. This should be used for pure packing scenarios only, and not for repacking or additions to the existing containers. Section 2: Restricting Containees in Container Specify containee asset type (If you select ALL you won't be able to capture attributes) Select from the list of asset types. Select ALL, if the attributes need not be captured. OAT Asset Tracking Installation and Configuration Guide 32

33 Containee EPC encoding scheme Matching containee EPC to a product How is the containee product identified? (If Matching containee EPC to a product? has the value Match Specific Product ) Specify containee SKU Specify containee UOM Specify containee style code Alert if the containee belongs to another container? Should the operator be allowed to decide at execution which containees to add/remove? If operator is not allowed to decide (No is chosen above), should new containees be added to container? If operator is not allowed to decide, should missing containees be removed from container? Select an encoding scheme for containee EPCs. Select one of the following: Match Specific Product Match Any Product No Product Match Required Select one of the following options: From configured static product - to validate containee product against the product configured below. From product selected at execution - to let the operator choose a containee product at the time of execution. The containee product is validated with the product chosen by the operator during process execution. From first containee EPC - to derive the containee s product information from the EPC encoding of the first tag read. Select a SKU for the containee. Select a UOM for the containee. Specify the Style Code for the containee. Select Yes to generate alert if a read containee is of another container. Select No to ignore. Select Yes to let the operator decide the containees to be added/ removed at execution. Select Yes to add new containees to the container. Select Yes to remove the missing containees from the container. OAT Asset Tracking Installation and Configuration Guide 33

34 Section 3: Starting and Stopping the Process Is a photocell or motion detector used to start the scanning process? Specify the digital input device for starting and stopping scanning process Specify the digital input trigger state to start scanning Specify the digital input trigger state to stop scanning Stop scanning after a period (configured below)? Stop scanning after the configured time (ms) (if yes is selected above) Turn on the reader only while scanning for assets User confirmation is required after scanning for all assets Alert if more containees are added to the container than permitted? Select Yes to have a digital input device configured to start the process. Select No to display Start Process button for the operator to proceed Select the digital input device used to start the aggregation process, from the list. This trigger starts the reader, for the duration of the aggregation. Select on or off to specify if the aggregation process starts at an on or off signal. Select on or off to specify if the aggregation process stops at an on or off signal. Select Yes or No. Enter the duration of the timeout in milliseconds. Select Yes or No. Select Yes or No. Select Yes to generate an alert. Select No to ignore and continue anyway. NOTE: This parameter is applicable only if a containee target quantity is specified. Containee Target Quantity Enter an expected number of containees for this container. Section 4: Actions While Adding/Removing a Containee to a Container Alert if the container/containee has not been seen by the system previously? Select Yes to generate alert, if the container/containee is unknown Select No to ignore. OAT Asset Tracking Installation and Configuration Guide 34

35 Digital output when a valid EPC is read Digital output when an invalid container/containee is read Digital output when a container is identified Digital output when verification threshold met Digital output if no container is identified but container is closed (manually or by timeout) Digital output if no containees are identified but container is closed (manually or by timeout) In the popup window, configure the digital output to which the scenario sends a signal for every asset tag that has valid EPC. In the popup window, configure the digital output to which the scenario sends a signal for every asset tag that has failed EPC validation. For example, if the GTIN of the EPC does not match the expected GTIN. In the popup window, configure the digital output to which the scenario sends signal when a container is identified. In the popup window, configure the digital output to which scenario sends signal when verification threshold is met. In the popup window, configure the digital output to which the scenario sends the signal when container is not identified. In the popup window, configure the digital output to which the scenario sends the signal when containee is not identified. Section 5: Container Attributes Pre-validation Define pre-validation checks Configure the pre-validation checks in the popup window. Section 6: Containee Attributes Pre-validation Choose which containees to pre-validate Select one of the following: No pre-validation required - to skip this step. Containees added to container in this session - to pre-validate only added containees. Containees removed from container in this session - to pre-validate only removed OAT Asset Tracking Installation and Configuration Guide 35

36 containees (useful in unpacking use-cases). Containees currently present in container (after added/removed in this session) - to prevalidate only present set of containees. Define pre-validation checks Action to perform if pre-validation of a containee fails Configure pre-validation checks in the popup window. Select one of the following: Reject the whole container Ignore the error Section 7: Capturing Attributes for Container Reset all container asset attributes Capture these attributes for every container Specify timeout for attribute capture through UI and Barcode (ms) specifying 0 (zero) disables timeout for container Alert if the captured (by UI) attributes do not match this rule Alert if the captured (by Barcode) attributes do not match this rule Alert if the captured (by External System) attributes do not match this rule Modify these attributes for every container Select Yes to clear existing attributes of the container. In the popup window, specify attributes to be captured for every aggregation session. Enter a timeout value in milliseconds. In the popup window, configure validation rules for attributes captured through user interface. In the popup window, configure validation rules for attributes captured through barcode. In the popup window, configure validation rules for attributes captured through an external system. In the popup window, select the attributes and enter the value. Alert if the modified attributes do not match this rule In the popup window, configure validation rules for all attributes, including constant attributes OAT Asset Tracking Installation and Configuration Guide 36

37 Section 8: Capturing Attributes for Containees Reset all containee asset attributes Choose which containees attributes to capture Capture these attributes for containees Specify timeout for attribute capture through UI and Barcode (ms) specifying 0 (zero) disables timeout for containee Alert if the captured (by UI) attributes do not match this rule Alert if the captured (by Barcode) attributes do not match this rule Alert if the captured (by External System) attributes do not match this rule Modify these attributes for every containee Alert if the modified attributes do not match this rule Select Yes to clear existing attributes of container. Select No to ignore. Select one of the following Containees currently present in container (after added/removed in this session). Containees removed from container in this session. NOTE: The latter option is useful for unpacking use-cases. In the popup window, specify attributes to be captured for every containee and its mode of capture. Enter a timeout value in milliseconds. In the popup window, configure validation rules for attributes captured through user interface In the popup window, configure validation rules for attributes captured through barcode. In the popup window, configure validation rules for attributes captured through an external system. In the popup window, select the attributes and enter the value. In the popup window, configure validation rules for all attributes, including constant attributes OAT Asset Tracking Installation and Configuration Guide 37

38 Section 9: Actions While Validating Container or Containees Action to perform if validation of container/containee fails Digital output when container/containee passes validation Digital output when container/containee fails validation Select one of the following: Reject the container to remove the containee from the container. Ignore the error to override the validation failure. Prompt operator to ignore error, remove the containee or reject container - to let the operator override the validation failure or remove the containee from the container. In the popup window configure the digital output to which scenario sends signal when the container/ containee passes validation. In the popup window configure the digital output to which scenario sends signal when the container/ containee fails validation. Section 10: Location Association Container Build location Business location where container is at the time of building it Business location where container will be released after building Business location for rework if container failed to meet threshold Should the container be assigned to a location when validation fails? Select the location where the RFID reader is configured. This is a Readpoint location. Select the location where the container is being built. Select the location where each pallet is placed after completion. Select the location at which the pallet is placed, if the number of asset tags read during the aggregation session is below the threshold defined as part of the product configuration. Select Yes to associate container to configured location (above) even if attribute validation fails. OAT Asset Tracking Installation and Configuration Guide 38

39 Section 11: Define Devices Barcode scanner for capturing attributes (if used) Specify the optional barcode scanner device. Section 12: Define External System Integration s for Attribute Capture of Container and Containees Specify location identifier to be sent to external systems Select one of the following: Location EPC Location Name User defined value (below) NOTE: This value is sent along with the EPC to the external system and can be used by that system to determine attribute values to be sent back. Specify the value to be sent as identifier to external system Target end point for SOAP service Action URI for SOAP service Specify timeout for SOAP service (ms) If User defined value is selected above, specify the value to be sent to external system for every EPC Specify SOAP service URL. Specify Action URI. Default is 60000, or 60 seconds. Section 13: Printing Configuration Generate an RFID label for each container? Choose a Label Printer Should the printer status be verified before writing the tag? Select Yes, to generate the label for the aggregate entity, even if it is precommissioned. Select No, if you do not want to generate the label. Select a printer for printing the pallet label. Select Yes to ensure the printer status (ONLINE/ OFFLINE) is checked before sending a write command. OAT Asset Tracking Installation and Configuration Guide 39

40 Should the tag be verified after writing? Should a tag be printed for an incomplete group (container)? Should the group (container) be closed if the print fails? Specify the digital input device to notify printer on Specify the digital input trigger state to notify printer on Digital output when print starts Digital output when print succeeds Digital output when print fails Digital output when printer comes online when print failed Select Yes to ensure that the printer reads the printed tag and it has been correctly encoded. Select Yes to ensure that a RFID tag for the asset grouping is printed, even if the grouping does not fulfill the aggregation plan. Select Yes to close/complete the pallet if printing fails. Select No to let it remain incomplete if printing fails. Select the digital input device from the drop down list. Select on or off. In the popup window, configure the digital output to which the scenario sends a signal when label printing starts. In the popup window, configure the digital output to which the scenario sends a signal when label printing succeeds. In the popup window, configure the digital output to which the scenario sends a signal when label printing fails. In the popup window, specify the digital output to which the scenario sends a signal when printer comes online when print failed. Section 14: Label Configuration Specify the path for label template Specify product parameters to be printed on labels (multiple items) Select the ZPL template for printing a pallet label. Specify product-related information (for example, SKU, MANUFACTURER or GTIN) to be printed on the label. OAT Asset Tracking Installation and Configuration Guide 40

41 Section 15: Define UI Look and Feel Select the container attributes to display on the screen Select the containee attributes to display on the screen In the popup window, select attributes to be displayed during attribute capture. In the popup window, select attributes to be displayed during EPC scan and attribute capture. NOTE: During EPC scan, the attributes will be displayed via a popup window, on holding the mouse cursor on the EPC. Does the operator need to confirm after changing asset attributes? Select Yes to let the operator confirm attributes. Section 16: Shipment Should packing to be done against shipment? Shipment Search s Container attributes to be sent as part of ASN document Containee attributes to be sent as part of ASN document Select Yes to pack the shipment against the plan. In the popup window select the attributes to be used as search parameters. In the popup window select the container attributes which will be sent as part of updated ASN document. In the popup window select the containee attributes which will be sent as part of updated ASN document. Section 17: Send ASN document to External System Target end point for SOAP service Specify the end point address for SOAP service to send the updated ASN document. For example, websvc.mycompany.com /axis/services/asnimportservice OAT Asset Tracking Installation and Configuration Guide 41

42 Specify timeout for SOAP service (ms) Specify a timeout in milliseconds. NOTE: If the SOAP server fails to respond, it delays scenario execution significantly. This configurable timeout enables scenario execution to continue if the SOAP service does not respond within the set number of milliseconds. Send digital output when web service succeeds Send digital output when web service fails In the popup window, specify the digital output to which the scenario sends a signal when web service succeeds. In the popup window, specify the digital output to which the scenario sends a signal when web service fails. 3.5 Advance Shipping Notice (ASN) An Advance Shipment Notice (ASN) is an electronic notification of pending deliveries that provides information to the buyer about the contents of the shipment. ASN lists the contents of a shipment as well as additional information like attributes, date etc. related to the shipment. ASN generally includes the following information: Ship-To address to which the shipment is being sent to. Expected arrival date and time of the shipment. Orders included in the shipment. There can be multiple orders referenced in a shipment. The goal of the ASN is to provide information to the destination's receiving operations well in advance of delivery. An ASN provides a list of all of the barcode ID numbers of the shipping units and the contents of each. The bar code label typically contains information which can be verified against the ASN ASN document Properties The asn_doc.properties file is configurable. The asn_doc.properties uses xpath expressions to describe the ASN document. The asn document in XML format should strictly follow the structure described in the asn_doc.properties file, but the details are optional. For example; the Container need not have Packs, but can have Items directly under it. This would still be a valid ASN document as long as the Container Item hierarchy is followed. The xpath expression is written based on the XML hierarchy separated by a / (forward slash). The xpath is represented as follows: To access a node - /rootnode/node OAT Asset Tracking Installation and Configuration Guide 42

43 To access an precedes the attribute name - /rootnode/node/@attrname For example, a node (asn) is represented as /shipment/asn the attribute (asnnumber) as /shipment/asn/@asnnumber in the given XML: <shipment shipmentno="s1"> <asn asnnumber="asn01" > </asn> </shipment> ASN Document Property List: Property Mandatory asn.prop List of ASN level properties Y container.prop List of Container level properties N Container.attributes List of Container attributes N pack.prop List of Pack level properties N pack.attributes List of Pack attributes N item.prop List of Item level properties N Item.attributes List of Item attributes N order.prop List of Order level properties N order_li.prop List of Order line level properties N NOTE: Either container.prop or pack.prop has to be mandatory. NOTE: container.prop or pack.prop has to be mandatory. oat.asn.orderstatus Order status in the plan document. For example : PACKING Y oat.asn.shipstatus Shipment status in the ASN Y OAT Asset Tracking Installation and Configuration Guide 43

44 Property Mandatory document. For example: SHIPPING oat.asn.receivestatus oat.asn.dateformat ASN level Properties Receiving status in the ASN document. Example: RECEIVING The date format can be configured using the property oat.asn.dateformat. The default format for date is yyyy-mm-dd HH:mm:ss. Y N Following are the ASN level properties: Property Mandatory asnnumber ASN Number Y documentissuedate Document Issue Date N shipmentdate Shipment Date N bolnumber shipment number Y SupplierNumber Supplier Number N SupplierName Supplier Name N shipfromidentifier Ship From Identifier N shipfromlocationname Ship From Location Name N shiptoidentifier Ship To Identifier N ShipToLocationName Ship To Location Name N ShipmentStatus Status of ASN Y Assigning ASN level properties for data extraction: asn.props=asnnumber,documentissuedate,shipmentdate,bolnumber,suppliernu mber,suppliername,shipfromidentifier,shipfromlocationname,shiptoidentif ier,shiptolocationname,shipmentstatus Each field listed in the asn.props should have xpath defined. ASN Level properties OAT Asset Tracking Installation and Configuration Guide 44

45 asn.shipmentstatus=/shipment/asn/shipmentstatus Container Level Properties Following are the Container level properties in ASN document: Container Property Mandatory numberofpackages Number of Packages N Epc EPC N product_identifier Product description (SKU) N ShipmentStatus Shipment status Y Assigning Container level properties for data extraction: NOTE: Either EPC or product_identifier is mandatory. NOTE: Either EPC or product_identifier is mandatory. container.props=numberofpackages,product_identifier,epc,shipmentstatus Each field listed in the container.props should have xpath defined. Container Level properties container.attributes=lotno container.numberofpackages=/shipment/asn/container/@numberofpackages container.epc=/shipment/asn/container/@epc container.product_identifier= container.lotno=/shipment/asn/container/lotno container.shipmentstatus=/shipment/asn/container/shipmentstatus OAT Asset Tracking Installation and Configuration Guide 45

46 Pack Level Properties Following are the Pack level properties in ASN document: Pack Property Mandatory epc EPC of the item N product_identifier Item/Part Number N ShipmentStatus Shipment status Y Assigning Pack level properties for data extraction: pack.props=epc,product_identifier,shipmentstatus Each field listed in the pack.props should have xpath defined. NOTE: Either EPC or product_identifier is mandatory. NOTE: Either EPC or product_identifier is mandatory. Containee Level properties (2nd level) pack.attributes=hazardous pack.epc=/shipment/asn/container/package/@epc pack.product_identifier= pack.hazardous=/shipment/asn/container/package/hazardous pack.shipmentstatus=/shipment/asn/container/package/shipmentstatus Item Level Properties Following are the Item Level properties in ASN document: Item Property Mandatory epc EPC of the product N product_identifier Item/Part Number N uom UOM N Quantity Shipped Quantity N ordernumber Order Number Y NOTE: Either EPC or product_identifier is mandatory. NOTE: Either EPC or product_identifier is mandatory. OAT Asset Tracking Installation and Configuration Guide 46

47 Item Property Mandatory Linenumber Line Number Y The order number and the order line number can also be configured. But they are not mandatory. Assigning Item level properties for data extraction: item.props=epc,product_identifier,uom,quantity,ordernumber,linenumber If the items are associated at the pallet level, then the properties pack and pack.props need not be defined. If the items are associated to the carton level and are not contained within the pallet, then the properties container and container.props need not be defined. If all the three levels of containment are present, then the properties at all the levels should be mentioned. Each field listed in the item.props should have xpath defined. Item Level properties (3rd level) item.attributes=weight item.product_identifier=/shipment/asn/container/package/item/@itemnumbe r item.uom=/shipment/asn/container/package/item/@uom item.quantity=/shipment/asn/container/package/item/@shippedquantity item.epc= item.weight=/shipment/asn/container/package/item/weight item.ordernumber=/shipment/asn/container/package/item/ordernumber item.linenumber=/shipment/asn/container/package/item/linenumber Order and Line Order Properties Following are the Order Level properties in ASN document: Order Property Mandatory ordernumber Order Number Y orderstatus Order Status Y Assigning Order level properties for data extraction: order.props=ordernumber,orderstatus Each field listed in the order.props should have xpath defined. order.ordernumber=/shipment/asn/order/@ordernumber Following are the Order line level properties in ASN document: Order Line Property Fields Mandatory Linenumber Order Line number Y Quantity Order Quantity N OAT Asset Tracking Installation and Configuration Guide 47

48 Order Line Property Fields Mandatory UOM Order s UOM Y ItemNumber Item Number Y Assigning Order line level properties for data extraction: order_li.props=linenumber,itemnumber,orderlinestatus,uom,quantity Each field listed in the order_li.props should have xpath defined. Order Line Level properties order_li.linenumber=/shipment/asn/order/orderline/@linenumber order_li.itemnumber=/shipment/asn/order/orderline/@itemnumber order_li.orderlinestatus=/shipment/asn/order/orderline/@orderlinestatus order_li.uom=/shipment/asn/order/orderline/@uom order_li.quantity=/shipment/asn/order/orderline/@quantity VisibleEdge VisiblEdge is an RFID fork lift package which helps identify and track the status and location of goods and assets. It determines and verifies fork lift locations, pickup status and location of loads, without any operator assistance. Messages move from VisiblEdge to OAT with a unique message identifier. Messages thus received can be configured in Asset Tracking. See Section 6, VisibleEdge Setup for details Attribute capture/ validation Attributes are captured for the outer/inner level Handling Units (pallets, cartons) during the Shipping or Receiving process. Attributes may be captured by UI or external system integration or barcode scan or from ASN document which is uploaded into OATxpress. Validation is done against the rules configured in the scenario during the deployment Reconcile To reconcile RFID reads against the expected quantities, operators can resolve any discrepancies between the quantities determined using RFID reads against the quantities specified in Advance Shipment Notification. For example: When a pallet is unloaded, 38 cases are read. But, the shipment notification lists 45 cases for the pallet. The operator is alerted of the discrepancy and instructed to reconcile the difference by physical inspection of the pallet. If discrepancy results, an alert message is displayed to the operator giving him the option to accept the undetected handling units which are actually part of the shipment but not read by the RFID process. OAT Asset Tracking Installation and Configuration Guide 48

49 3.5.5 Acknowledgement Post shipping confirmation or Acknowledgement, allow monitoring the Shipping process on different levels. Once the shipping process is complete (handling unit level or shipment level) OATxpress sends a confirmation to the ERP system which is used by the ERP system to post Goods Issue ASN Scenario Configuration s The following sections describe the parameters of the scenarios to be configured. Section 1: General Mode of Operation Select the mode of operation as Shipping or Receiving. Section 2: Identify Shipment How is the shipment identified? Select one of the following procedure to identify the shipment: Search by UI- to search shipment by ASN number, Shipment number or shipment attributes or in combination. Automatic Detection- Shipment detection will be done using EPC read automatically. Once the Shipment is detected, then that will be the target shipment for that session. New Shipment To let the operator enter the Shipment Number in the UI. This indicates that all shipments will be treated as a New Shipment External System To let the scenario to receive the Shipment Number and details from an External System. Shipment Search s In the pop up widow select the attributes used OAT Asset Tracking Installation and Configuration Guide 49

50 for shipment search. Section 3: Identify ASN How is the ASN identified? Select one of the following procedure to identify the ASN: UI Entry- to search shipment by ASN number, Shipment number or shipmentattributes or in combination. External System- To retrieve the ASN number from the External System along with the shipment details. NONE - User will not be prompted for the ASN number. ASN Number will be assigned a dummy constant value like Section 4: Starting and Stopping the Process Specify the session start mode Select the one of the following to start session: UI To start the session on Active mode EPC Read- to automatically start session by reading EPC - To start the session on Passive mode Photocell or Motion detector - input trigger to start the session. Specify the digital input device for starting the session Select one of the digital input devices for starting the session. This is applicable only if Photocell or Motion detector is selected. OAT Asset Tracking Installation and Configuration Guide 50

51 Specify the digital input trigger state to the session Is a photocell or motion detector used to start the scanning process? Time Delay after motion detect signal (allow time for data collection in ms) Specify the digital input device for starting scanning process Specify the digital input trigger state to start scanning Is a photocell or motion detector used to stop the session? Select on or off to specify the trigger state. Select Yes to use photocell or motion detector to start the scanning (RFID reads) process. Enter time in millisecond to specify a delay. If motion sensor is used to start the scanning process, scenario will wait for the specified time to collect all the EPCs in the fields before starting the association/ validation process. Select one of the listed digital input devices to start scanning. Select on or off to specify the digital input trigger state to start Select Yes to select photocell or motion detector to stop the session. NOTE: There are three ways to stop the session Using photocell Specifying Time out, if there are no EPC is read in the specified period of time UI based stop Specify the digital input device for stopping the session Specify the digital input trigger state to stop the session Turn on the reader only while session is in progress Select one from the list of digital input trigger to stop the session, If Yes is selected in the previous question. Select on or off to specify the digital input trigger state to stop. Select Yes to turn the reader on, only after the session started. At the end of the session, reader will be turned off. NOTE: Cannot start the session based on EPC Read if Yes is selected. Stop session after a period (configured below)? Stop session if no EPC is read after the Select Yes to stop the session time based. Enter the time in millisecond, to stop the session if no EPC is read for the entered time. OAT Asset Tracking Installation and Configuration Guide 51

52 configured time (ms) ( if yes is selected above) NOTE: This is valid only if Yes is selected above. Initialize stack light on start In the popup window, configure the digital output, when the session starts. Alert on session completion In the popup window, configure the digital output, after the session is completed. Section 5: Tag Observations Select the list of EPC encoding schemes to be ignored while processing tags Select the EPC encoding schemes to be ignored while processing, to speed up the process. NOTE: Multiple selections are possible. Is VisiblEdge enabled? Select Yes to specify that VisiblEdge is enabled. Default is No. See VisibleEdge for more information. Section 6: VisiblEdge Setup VisiblEdge Message Type Select any of the following: Pick up Put Down Location Update Device Status VisiblEdge message identifier Is SGLN Location? Location Attribute Name (Valid only if above Enter VisiblEdge Message identifier to get EPC information through webservice. Select Yes if it is a SGLN location. Enter location attribute name. OAT Asset Tracking Installation and Configuration Guide 52

53 is Yes. Leave as blank for using EPCIS ID) Allow EPCs in the past to be processed? Display movement message details? Display EPCs in the movement message? Display device status? Display device status in the event tile? Allow session closure? Allow session cancellation? Select Yes to process the past EPCs. Default is Yes Select Yes to show EPCs in UI Default is Yes. Select Yes to display details of each EPC movements. Default is No. Select Yes to display status of the device in UI as green or red. Default is No. Select Yes to display status of the device in event tile. Default is No. Select Yes to allow closure of session. Default is Yes. Select Yes to allow cancellation of session. Default is Yes. Section 7: Identify Container Specify container asset type Enter percentage of containees to be read for inferring Handling Unit EPC (If Handling Unit is not identified at start) Select one of the container asset types from the dropdown list. Enter the percentage of containees to be read to infer the container. Section 8: Container Attributes Pre-validation OAT Asset Tracking Installation and Configuration Guide 53

54 Define pre-validation checks Configure the pre-validation checks in the popup window. Section 9: Capturing Attributes for Container Reset all container asset attributes Want to capture attributes every time an asset is read? Capture these attributes for every container Specify timeout for attribute capture through UI and Barcode (ms) specifying 0 (zero) disables timeout for container Alert if the captured (by UI) attributes do not match this rule Alert if the captured (by Barcode) attributes do not match this rule Alert if the captured (by External System) attributes do not match this rule Modify these attributes for every container Select Yes to clear existing attributes of the container. Default is No. Select Yes to capture new set of attributes every time an asset is read. Default is No. In the popup window, specify attributes to be captured for every aggregation session. Enter a timeout value in milliseconds. In the popup window, configure validation rules for attributes captured through user interface. In the popup window, configure validation rules for attributes captured through barcode. In the popup window, configure validation rules for attributes captured through an external system. In the popup window, select the attributes and enter the value. Alert if the modified attributes do not match this rule In the popup window, configure validation rules for all attributes, including constant attributes Section 10: Capturing Container Attributes from ASN Document Want to capture attributes from the ASN document for every Container? If ASN document is not found for a Select Yes to assign attributes to every container from ASN document. Default is No. Select one of the following: OAT Asset Tracking Installation and Configuration Guide 54

55 Container Absence of ASN document is an error to report error on absence of ASN document. Ignore the absence of ASN document to ignore. Select the attributes to capture from ASN document Alert if the attributes from ASN document do not match this rule In the popup window, check attributes to be captured from ASN document. In the popup window, configure validation rules for attributes captured from ASN document. Section 11: Identify Containee Specify containee asset type Select one of the containee asset types from the dropdown list. Section 12: Containee Attributes Pre-validation Define pre-validation checks Configure the pre-validation checks in the popup window. Section 13: Capturing Attributes for Containee Reset all containee asset attributes Want to capture attributes every time an asset is read? Capture these attributes for every containee Specify timeout for attribute capture through UI and Barcode (ms) specifying 0 (zero) disables timeout for containee Select Yes to clear existing attributes of the containee. Default is No. Select Yes to capture new set of attributes every time an asset is read. Default is No. In the popup window, specify attributes to be captured for every containee. Enter a timeout value in milliseconds. OAT Asset Tracking Installation and Configuration Guide 55

56 Alert if the captured (by UI) attributes do not match this rule Alert if the captured (by Barcode) attributes do not match this rule Alert if the captured (by External System) attributes do not match this rule Modify these attributes for every containee Alert if the modified attributes do not match this rule In the popup window, configure validation rules for attributes captured through user interface. In the popup window, configure validation rules for attributes captured through barcode. In the popup window, configure validation rules for attributes captured through an external system. In the popup window, select the attributes and enter the value. In the popup window, configure validation rules for all attributes, including constant attributes. Section 14: Capturing Containee Attributes from ASN Document Want to capture attributes from the ASN document for every Containee? If ASN document is not found for a Containee Select Yes to assign attributes to every containee from ASN document. Default is No. Select one of the following: Absence of ASN document is an error to report error on absence of ASN document. Ignore the absence of ASN document to ignore. Select the attributes to capture from ASN document for Containee Alert if the attributes from ASN document do not match this rule In the popup window, specify attributes to be captured from ASN document. In the popup window, configure validation rules for attributes captured from ASN document. Section 15: Location Association Readpoint location Business location Select the location where the RFID reader is configured. Select the business location for association. OAT Asset Tracking Installation and Configuration Guide 56

57 Section 16: Actions While Validating Container or Containees Digital output when container/containee passes validation Digital output when only some container/containee passes validation Digital output when container/containee fails validation In the popup window configure the digital output to which scenario sends signal when the container/ containee succeeds validation. In the popup window configure the digital output to which scenario sends signal when only some of the container/ containee passes validation. In the popup window configure the digital output to which scenario sends signal when the container/ containee fails validation. Section 17: Reconcile Is reconcile allowed if required? Select Yes to reconcile the containers/ containees if there are discrepancies. Default is No. Reconcile handling level? Reconcile without EPC reads? Select the level of handling units for reconciliation Select Yes to review the ASN document and reconcile without reading EPC. No otherwise. Section 18: Acknowledgement Send Session level (for all ASNs) acknowledgement to external system? Select Yes to send acknowledgement after shipping or session is complete. Sent Container level acknowledgement to external system? Select Yes to send acknowledgement at Container level, when the session is in progress. OAT Asset Tracking Installation and Configuration Guide 57

58 Target end point for SOAP service Specify timeout for SOAP service (ms) Specify the end point address for SOAP service. For example, /axis/services/asnimportservice Specify a timeout in milliseconds. NOTE: If the SOAP server fails to respond, it delays scenario execution significantly. This configurable timeout enables scenario execution to continue if the SOAP service does not respond within the set number of milliseconds. Send digital output when web service succeeds In the popup window, specify the digital output to which the scenario sends a signal when web service succeeds. Send digital output when web service fails In the popup window, specify the digital output to which the scenario sends a signal when web service fails. 3.6 OATship The OATship scenario reads pallets, verifies their validity and marks them as shipped. OATship is used after a pallet has been created using OATpack OATship Features Capture Pallet EPC The shipping process is performed on the selected Asset Type and the encoding scheme. The scenario validates if the contents of the pallet conform to the specified Asset Type and Product. The units of measure of the container and contained items are also specified to satisfy the above requirements. Only RFID devices are supported for capturing EPCs. Starting and Stopping OATship Use one of the following methods to start OATship: Motion sensing: This uses a digital Input/Output device. A motion sensor alerts the scenario regarding movements near a shipping station, at which point the scenario asks the RFID device to look for tags. EPC detection: When the scenario starts, the RFID device looks for tags. OAT Asset Tracking Installation and Configuration Guide 58

59 Manual Start: An operator can start the scenario manually through the user interface. Use the following methods to stop the scenario: Time-out based: The shipping session can be stopped based on specified time periods. At the end of a specified time period, the shipment is closed. Manual: An operator can stop the scenario manually through the user interface. Shipment Validations Containee detection validations: The container and/or its containees are used to identify the pallet. A threshold value is set to identify a container based on the number of contents identified by RFID reads. The scenario waits until the threshold has been met, before moving to the next. Alerts are sent to provide feedback to operators when a container is identified, or in the case of an exception. Container state validations (attribute validations): Besides validating a shipment based on the containees, rules are defined based on the attributes of the container. Alerts are defined to signal validation success/failure. Note that the attributes of the containers, not the containees are validated. Location association Based on the success and failure of the shipment, the container is associated with a location OATship Configuration s Section 1: Link Tags to Assets Specify asset type Encoding scheme Select the Asset type to be shipped Select the EPC encoding scheme. Section 2: Define Container Structure Specify the unit-of-measure for the container Specify the unit-of-measure for the containee Specify the unit of measure for the aggregate entity/pallet. Specify the unit of measure for the contents of the pallet. OAT Asset Tracking Installation and Configuration Guide 59

60 Section 3: Define Devices Specify the read point for the RFID antennas Specify the digital input device for starting and stopping the shipping process Select the locations at which reader antennas have been configured for the shipping process Select the SNAP/digital input device used to trigger the start or stop of the shipping process. Section 4: Starting the Shipping Process Is a photocell or motion detector used to start the shipping process? Specify a digital input trigger state to start shipping Select Yes to indicate that a digital input device will be used to start the process. Specify whether the shipping process starts at an ON signal or an OFF signal. Section 5: Identifying a Container Is container identified as soon as container tag is read Is container identified by reading its contained assets What % of assets in a container need to be read to identify a container Send digital output when a container is identified Send digital output when there is a read exception Specify YES, to use a pallet tag read to identify the pallet to be shipped. Specify Yes to identify a pallet by detecting the tags of the contained assets. Specify the percentage of assets to prevent the scenario from using stray reads to identify a container. A threshold percentage of containee reads is used for positive identification of the pallet. Specify the digital output points to which the scenario sends a signal when a pallet/ container are identified. Specify the digital output points to which the scenario sends a signal when an invalid tag is detected (for example a tag not belonging to the container being shipped). OAT Asset Tracking Installation and Configuration Guide 60

61 Section 6: Stopping the Shipping Process Is a photocell or motion detector used to stop the shipping process Should the shipping process stop if no tags are read for a length of time Specify the length of time after no tag is read that a shipment should stop Select Yes to indicate that a digital input device will be used to stop the process. Specify YES to indicate that if no tags are detected for a specified duration, OAT closes the shipping session. Specify duration in milliseconds. The default setting is 60,000 milliseconds. Section 7: Validating a Shipment Is a shipment valid if an asset is read that is not known to be part of the container What % of assets in a container need to be read for the shipment to be valid Specify the rules to validate a container Send digital output when threshold % is reached Send digital output if all assets in a container are successfully read Digital output if the container succeeds validation Specify No to indicate that the scenario invalidates a shipment if an asset tag not marked as belonging to the pallet being shipped is read. Specify a threshold % of containee reads to process a shipment successfully. If the number of containee reads is more than the threshold %, the scenario marks the pallet as successfully shipped. Configure a validation expression using asset attributes. If validation fails for the pallet being shipped, the shipping process fails. Specify the digital output point to which the scenario sends a signal when the threshold percentage of containee tags have been detected. Specify the digital output point to which the scenario sends a signal when ALL containee tags belonging to the pallet being shipped are detected. Specify the digital output point to which the scenario sends a signal when the OAT Asset Tracking Installation and Configuration Guide 61

62 container/pallet EPC has been successfully validated (because its attribute values satisfy the logical rule specified). Digital output if the container fails validation Specify the digital output point to which the scenario sends a signal when the container/pallet EPC has NOT been successfully validated (because its attribute values do NOT satisfy the logical rule specified). Section 8: Container Association Container Association location when a shipment is successful Container Association location when a shipment fails Specify the location at which the pallet is placed if the shipment process is successful.. Specify the location at which the pallet is placed if shipment fails (for example, if the number of containee tags read during the shipment session is below threshold, or if the container EPC fails the logical rule validation) 3.7 Label Print Scenario The Label Print scenario commissions new EPCs, associates attributes to these EPCs and prints labels with the attributes. The scenario comes in two flavors. One is a standard/user interface based scenario administered through OATxpress Administration UI pages. The other is a callable version which has to be invoked programmatically, typically using the scenarios web service. In the user interface version of the scenario, attributes are input through an external message, barcode scan or user interface and validated against configurable validation rules. Whereas, the callable version accepts attributes only through an external message Label Print Scenario Configuration s The following sections describe the parameters of the scenarios to be configured. Callable scenario parameters are set programmatically and not through a user interface. s are marked as follows: User interface parameters are marked with a (U) (without quotes) Callable scenario parameters are marked with a (C) (without quotes) OAT Asset Tracking Installation and Configuration Guide 62

63 Those available on both are marked with a (U/C) (without quotes). Section 1: Link Tags to Assets Specify tag encoding scheme for asset tags (U/C) Specify asset type (U/C) Select the EPC encoding scheme. Select the asset type for which labels should be printed. Section 2: UI (User Interface) Configuration Display dropdown list for SKU (U) Maximum number of line items (U) Maximum number of labels allowed per line (U) Select Yes to display the SKU (of the object/asset for which a label must be printed) in the drop down list. Enter the maximum number of line items for a single print run. One line item corresponds to one set of values of the SKU, UOM, Style Code and Quantity of labels to be printed. Only one line item is specified to an instance of the callable scenario, using the Asset SKU, Asset UOM and Asset Style Code configuration parameters (above). Enter the maximum number of labels (Quantity) allowed per line item. If more number of labels are needed for a particular product (combination of SKU, UOM and Style Code), two (or more) separate line items are specified for the same product, such that the sum of Quantities across these line items matches the required number of labels to be printed. Number of labels per EPC serial number Enter the number of labels required per EPC serial number. Maximum number of labels per EPC serial number Enter the maximum number of labels allowed per EPC serial number. Section 3: Reprinting Asset Label OAT Asset Tracking Installation and Configuration Guide 63

64 Choose Search parameters (if identifying asset by search) In the popup window select the attributes to be searched by, for the asset. Section 4: Encoding and Printing Configuration Printers to Load (U/C) Print template path (U/C) In the popup window, configure the printer used for printing the labels Select the label template for the labels to be printed. Verify printer status before writing (U/C) Select Yes to check the printer status (online/offline) before printing. Select the attributes to print on the label (U/C) Verify tag after writing (U/C) Digital output on print failure (U/C) Digital output on print start (U/C) Digital output on print succeeded (U/C) In the popup window, select the list of attributes whose values are to be printed on the label. Select Yes to verify the tag after printing. Configure to show digital output signal when printing fails. Configure to show digital output signal when printing starts. Configure to show digital output signal when printing succeeds. Section 5: Specify Location to Assign Asset Label Asset association location when validation succeeds (U/C) Select the location with which the asset has to be associated when printing and attributes validation operation succeeds. Asset association location on validation failures (U/C) Select the location with which the asset has to be associated when printing and/or attribute validation operations fail. OAT Asset Tracking Installation and Configuration Guide 64

65 Section 6: Define Devices Barcode scanner for capturing attributes (if used) (U) Select Barcode scanner to scan attributes, if attribute capture through barcode is defined. Section 7: Define Attribute Modifications Specify timeout for attribute capture through UI and Barcode (ms) Specify the time within which attributes have to be captured using the UI (user interface) or Barcode. If attributes are not entered within the specified period of time, the scenario proceeds without capturing attributes. NOTE: Specify 0 to disable timeout. Capture attributes every time a label is printed? Select Yes to capture attributes for every label printed. NOTE: If specified, constant attribute values are associated with the label. Capture these attributes for every asset Alert if the captured (by UI) attributes do not match this rule Alert if the captured (by Barcode) attributes do not match this rule Alert if the captured (by External system) attributes do not match this rule Modify these attributes for every asset Values for the configured attributes are captured for every asset. Attribute validation rule to be applied after capturing attributes through the user interface. Attribute validation rule to be applied after capturing attributes through a barcode scan Attribute validation rule to be applied after capturing attributes from an external system. Specify constant attributes (attributes that need to be applied with specific values for every asset) Section 8: Validate Modified Attributes OAT Asset Tracking Installation and Configuration Guide 65

66 Alert if the modified attributes do not match this rule Send digital output when validation fails Send digital output when validation succeeds Attribute validation rule to be applied after capturing all attributes, including those for which constant values are specified. Configure to show digital output signal when attribute validation fails. Configure to show digital output signal when attribute validation succeeds. Section 9: Define External System Integration s Specify location identifier to be sent to external system Specify the value to be sent as identifier to external system Target end point for SOAP service Action URI for SOAP service Specify timeout for SOAP service (ms) Select one of the following: Location name as configured in OFS Location EPC as configured in OFS User-defined value (below) Specify the value to be sent to the external system. Specify the end point address for SOAP service. For example, Service This value is currently unused and need not be configured. Specify a timeout in milliseconds. NOTE: If the SOAP server fails to respond, it delays scenario execution significantly. This configurable timeout enables scenario execution to continue if the SOAP service does not respond within the set number of milliseconds. Send digital output when web service fails (U/C) Configure to send digital output signal when web service fails. OAT Asset Tracking Installation and Configuration Guide 66

67 3.8 Configuring Reports Reports are accessed after OAT Asset Tracking installation. OAT Asset Tracking reports include the following: Asset Timeline Asset by Location Asset History Custom pre-configured reports. See the OATxpress User Guide for details on modifying user and role privileges. The Asset by Location, Asset by Location Details and Asset History reports are pre-configured with a set of attribute values. This is convenient for reports generated often. The format and required parameters differ for the three supported types of reports. Valid types are ASSET_BY_LOCATION, ASSET_BY_LOCATION_DETAILS and ASSET_HISTORY. Report configuration files are located in the <ofs_install>/ofs/conf folder. NOTE: In the definition files below, comment lines start with #. ASSET_BY_LOCATION definition file # The CACHE flag is used for debugging purposes. # if set to true it will read this file only at startup # if set to false, the file will always be read, and never internally cached # if no property is provided the default is "false" # This parameter is optional. CACHE=false # The name of the report that gets displayed in the title bar # and on top of the report result page # This parameter is mandatory. REPORT_NAME=Sample Configured Report based on Asset By Location # Select the format of the report. # Possible values are: # - ASSET_HISTORY # - ASSET_BY_LOCATION # - ASSET_BY_LOCATION_DETAILS # There are different sets of required search criteria based on the report type chosen # This parameter is mandatory. REPORT_TYPE=ASSET_BY_LOCATION # The EPC_TYPE specifies if a given EPC complies to a specific format. # Valid formats are: # HEX or ALL which includes: sgtin, sscc, giai, grai, CUSTOM, # This parameter is mandatory. EPC_TYPE=HEX # This specifies a pattern appropriate for the given EPC_TYPE # This parameter is mandatory. EPC_PATTERN=* # Location filter setting OAT Asset Tracking Installation and Configuration Guide 67

68 # This can be the Database ID or the name given to the Location # in the OATxpress Location configuration screen # Multiple Locations can be specified # This parameter is optional ASSET_LOCATION=TagComLocation # The name of the Asset as defined in the Product configuration Page # This parameter is mandatory ASSET_TYPE=EngineAsset # EXPRESSION Specifies an optional attribute based Expression. # This parameter is optional. # The expression must have the following format: # FieldSeparator FS::= ~ # RowSeparator RS::= # Operator OP::= IS NULL IS NOT NULL LIKE > >= =!= <= < # Logic LO::= AND OR # Attribute ATTR::= [a-za-z0-9][a-za-z0-9]* (The attribute key as defined in the AssetDefinition.xml file) # Value VAL::= [a-za-z0-9][a-za-z0-9]* # Row ROW::=ATTR FS OP FS [ VAL ] # Expression EXPR::=ROW [RS LO RS EXPR] EXPRESSION=engNum~IS NULL~ ~AND mountdate~=~12/12/2008~ # specifying the observation time span. # This allows to specify if an asset remained at the # given location lessthan or morethan a given number of weeks, days, hours or minutes # based of today's date # The DIRECTION specifies if it is a "lessthan" or a "morethan" # operation. Possible values are: # - lessthan # - morethan # - ignore This disables the Timespan filter # This parameter is mandatory. DIRECTION=moreThan # The TIMESPAN is a simple number greater than 0 # This parameter is mandatory, but ignored if DIRECTION is ignore TIMESPAN=1 # The Unit is used in connection with the TIMESPAN parameter and is one off # - week # - day # - hour # - minute # This parameter is mandatory, but ignored if DIRECTION is ignore UNIT=week ASSET_BY_LOCATION_DETAILS definition file This is identical to ASSET_BY_LOCATION, except that the property REPORT_TYPE is set to ASSET_BY_LOCATION_DETAILS. ASSET_HISTORY definition file # The CACHE flag is used for debugging purposes. # if set to true it will read this file only at startup OAT Asset Tracking Installation and Configuration Guide 68

69 # if set to false, the file will always be read, and never internally cached # if no property is provide the default is "false" CACHE=false # The name of the report that gets displayed in the title bar # and on top of the report result page REPORT_NAME=Sample Configured Report # Select the format of the report. # Possible values are: # - ASSET_HISTORY # - ASSET_BY_LOCATION # - ASSET_BY_LOCATION_DETAILS # There are different sets of required search criteria based on the report type chosen REPORT_TYPE=ASSET_HISTORY # The EPC_TYPE specifies if a given EPC complies to a specific format. # Valid formats are: # HEX or ALL which includes: sgtin, sscc, giai, grai, CUSTOM, EPC_TYPE=HEX # This specifies a pattern appropriate for the givenepc_type EPC_PATTERN=* # The type of asset as defined when the system got set up. ASSET_TYPE=HopperAsset # Specifies optional the location of the asset. Possible values are: # - a location name # - a comma separated list of location names # or not specified at all selects all configured locations. #ASSET_LOCATION= # Specifies an optional attribute based Expression. # The expression must have the following format: # FieldSeparator FS::= ~ # RowSeparator RS::= # Operator OP::= IS NULL IS NOT NULL LIKE > >= =!= <= < # Logic LO::= AND OR # Attribute ATTR::= [a-za-z0-9][a-za-z0-9]* (The attribute key as defined in the AssetDefinition.xml file) # Value VAL::= [a-za-z0-9][a-za-z0-9]* # Row ROW::=ATTR FS OP FS [ VAL ] # Expression EXPR::=ROW [RS LO RS EXPR] #EXPRESSION= # Relative start/end date specification. # the base for computation is 'now', # meaning whenever the report is executed # 0 means now, # any positive value will be in the future # any negative value will be in the past # the unit is "days". The sample setting sets a start date 30 days in the past START_TIME=-30 # and uses as end date 'now' END_TIME=0 # To specify absolute dates use: # The TIME_FORMAT defines the format of the date and time specified in # START_TIME and END_TIME and can be any valid java date/time format as # specified by the java SimpleDateFormat #TIME_FORMAT= OAT Asset Tracking Installation and Configuration Guide 69

70 # This defines the start time. # This has to match the format defined in TIME_FORMAT #START_TIME= # This defines the end time. # This has to match the format defined in TIME_FORMAT #END_TIME= To Create and Deploy a Preconfigured Report In the OATxpress reporting framework, reports are identified by EVENT names specified in a file called custom_eventmap.xml. These event names map to a handler that processes this event. Event names are not to exceed 50 characters in length. In the context of the Asset Tracking solution this event handler is always as follows: com.oatsystems.raf.newevent.report.assettrackingeventhandler. Following is a sample entry in the custom_eventmap file: <event name="sample_configured_report_event" classname="com.oatsystems.raf.newevent.report.assettrackingeventhandler " modulename="" snapback="" /> In this case the name of the event SAMPLE_CONFIGURED_REPORT_EVENT also identifies the property file called SAMPLE_CONFIGURED_REPORT_EVENT.properties which contains the definition of the search criteria. This allows the handler class to load the criteria and run the appropriate queries. The next step is to link the report into the user interface so that it can be viewed. Therefore the file custom_reportmap.xml has to be modified. Following is a sample entry: <report name="sample configured report" reportconstant="sample_configured_report_event" /> This adds an entry to the list of available reports with the name Sample configured report. After making changes are made perform the following steps: Restart OATxpress. Login as the superuser. Add the new report to a particular group of users. To do this: o o Select the Roles icon and click Edit for the Role to which you want to add the report. On the next screen, scroll down in the Reports selection box and select all the reports that should be viewable NOTE: The files custom_eventmap.xml and custom_reportmap.xml are stored in the following folder: <ofs_install>\jakarta-tomcat \webapps\oatedge\web-inf\classes It is important to note that these manual customizations are deleted the next time the deploy command is executed. It is recommended that you create a backup of the changed files and update the new custom_eventmap.xml and custom_reportmap.xml files as necessary. OAT Asset Tracking Installation and Configuration Guide 70

71 Chapter 4 Configuration for Zoning and Visualization 4.1 Introduction This chapter explains the procedures to configure and use Visualization and Zoning. Visualization helps the user to graphically track assets on the screen. For more details refer to the Asset Tracking User Guide. 4.2 Pre-requisites OATxpress OAT Asset Tracking 4.3 Map Configuration A Map refers to an image of an area in a site that may have one or more sub locations called Zones. A Zone is defined as a set of polygon points in a map image that correspond to specific predefined business locations. Map and Zone configuration helps designate which maps according to their hierarchy and which zones and sub zones must be made available through Visualization. It is important to know the exact polygon points of locations on map such that when the RTLS data (x and y positions for RTLS assets as they move) is received, they can be plotted and assigned to zones / locations respectively. Map and Zone configuration is based on the visualization_configuration.xml within the OFS_INSTALL/ofs/conf/ directory. Following is the default visualization_configuration.xml file. <ZoneConfiguration> <Maps/> <Zones/> <Navigation/> <ZoneConfig> <UIStatus/> <BusinessLocationHierarchy/> <RPMapping/> </ZoneConfig> </ZoneConfiguration> OAT Asset Tracking Installation and Configuration Guide 71

72 Configuration for Zoning and Visualization Following is an example:... <Maps > <Map mapid="assembly_plant" borderthreshold="15" description="map of assembly plant" name="assembly Plant relativehttpurl= images/maps/ assembly_plant.jpg" height="1197" width="1800"> value="1" /> value="0" /> value="0" />... <Calibration deviceepc="00fffffff "> </Calibration> </Map> <PreCalibrated> </PreCalibrated> <Property name="a11" <Property name="a12" value="0" /> <Property name="a13" <Property name="a21" value="0" /> <Property name="a22" value="1" /> <Property name="a23" Attributes on <Map> tag Optional/ Required mapid Unique id for each map(should not contain spaces) Required borderthreshold The distance around the zone that needs to be considered as inside the zone(default 0) Optional of the map Optional Name Display name for the map Required relativehttpurl Map image file url. All map images are expected to be placed in the: <oat_install_dir>/ jakarta-tomcat /webapps/oatedge/images folder. Required Height Height of the map Required Width Width of the map Required Calibration is the information required to transform a device coordinate system to the image coordinate system. An RTLS device might report X,Y in feet or meter or as GPS coordinate. Calibration is used to map the device X,Y to map image X,Y. Each map can have more than one calibration. Each calibration must be linked to an antennaepc for source coordinate system. OAT Asset Tracking Installation and Configuration Guide 72

73 Configuration for Zoning and Visualization All the transformations are linear transformations of the form specified below: x' = a11*x + a12*y + a13 y' = a21*x + a22*y + a23 where a11 - scale factor on x axis a12 - shear factor on x axis a13 - translation on x axis a21 - shear factor on y axis a22 - scale factor on y axis a23 - translation on y axis The above equation can be simplified to a matrix representation as follows: / a11 a12 a13 \ / x \ / x'\ a21 a22 a23 * y = y' \ / \ 1 / \ 1 / A * X = X' 4.4 Types of Calibration There are two types of calibration supported for the zoning: Pre-calibrated CalibrationByExample Pre-calibrated If the Matrix A is known for the linear transformation from device to image, then the matrix A can be provided for calibration. The configuration for a pre calibrated map is as follows: <! deviceepc is antennaepc of the device> <Calibration deviceepc="aabbccddeeffaabbccddeeff"> <PreCalibrated> <Property name="a11" value="1" /> <Property name="a12" value="0" /> <Property name="a13" value="0" /> <Property name="a21" value="0" /> <Property name="a22" value="1" /> <Property name="a23" value="0" /> OAT Asset Tracking Installation and Configuration Guide 73

74 Configuration for Zoning and Visualization </PreCalibrated> </Calibration> CalibrationByExample The calibration matrix can be found by solving few linear equations. The minimum requirement for solving the linear equation are set of at least 3 non-colinear points on device coordinate system and equivalent point in the image coordinate system. For example a location A "say a parking spot" on the device coordinate system is x1,y1 and the equivalent point(same location A) on the image is x1',y1'. Having 3 such points, the whole matrix can be determined. Following are the equations formed from the provided data points: Equation for a11, a12 and a13 are Equation for a11, a12, and a13 are: x1 = a11*x1 + a12*y1 + a13 x2' = a11*x2 + a12*y2 + a13 x3' = a11*x3 + a12*y3 + a xn' = a11*xn + a12*yn + a13 Equation for a21, a22, and a23 are: y1' = a21*x1 + a22*y1 + a23 y2' = a21*x2 + a22*y2 + a23 y3' = a21*x3 + a22*y3 + a yn' = a21*xn + a22*yn + a23 If more than 3 points then the solution might not be unique, so the equations are solved with min square error (Sum((xi'-xi'')^2) is minimum, where xi'' is computed using the solved values and xi' is actual value). Example for such configuration is as follows: <calibration deviceepc= 0F00 > <CalibrationByExample> <Point srcx="466" srcy="1413" destx="179" desty="115"> <Point srcx="466" srcy="1413" destx="179" desty="115"> <Point srcx="875" srcy="1541" destx="398" desty="541"> <Point srcx="883" srcy="1233" destx="550" desty="230"> <Point srcx="1307" srcy="1190" destx="860" desty="490"> OAT Asset Tracking Installation and Configuration Guide 74

75 Configuration for Zoning and Visualization </CalibrationByExample> </Calibration> 4.5 Zone Configuration A Zone can represent a whole map, a section of a map, or a dummy node for navigation. Example: <Zone Configuration clickable= true visible= true >... </Maps> <Zones> <Zone zoneid="assemblyparkinglot" name=" Assembly Parking Lot" mapid="assembly_plant_praking" parentzoneid="assemblyplant" clickable= false > <Polygon> <Point order="1" x="752" y="180"/> <Point order="2" x="980" y="371"/> <Point order="3" x="715" y="698"/> <Point order="4" x="479" y="506"/> </Polygon> <Property name="size" value="1 sqm" label="size"/> <Property name="area" value="200" label="area"/> </Zone>... In the above example zone Assembly Parking Lot is defined as a polygon on zone "Assembly Plant". Since Assembly Parking Lot has a mapid, it must have a map definition identified as "assembly_plant_praking ". Zone polygons are always defined against the lowest level map. The relationship between two zones on a map can only be containment or disjoint. No two zones can intersect with each other. One zone can contain another zone completely but cannot overlap partially Attributes on <Zone> tag Attributes on <Zone> tag Optional/ Required zoneid Unique id for the zone (should not contain spaces) Required Name Display name Required mapid Map of the zone, If not specified it means that Optional OAT Asset Tracking Installation and Configuration Guide 75

76 Configuration for Zoning and Visualization Attributes on <Zone> tag Optional/ Required parentzoneid isbusinessloc Clickable Visible this zone / location doesn't have map Parent zone for the current zone. Helps define the hierarchy of the zones (If not defined, the parent is root) Defines if a zone should be associated to a business location and thus used for zoning. If not specified the default value is NO Defines if a zone is clickable on the map to view properties. If not specified the default value is based on the clickable attribute on the <ZoneConfiguration> tag Defines if the zone should be visible on map. If not specified the default value is based on the clickable attribute on the <ZoneConfiguration> tag Optional Optional Optional Optional Navigation Tag Zones that are not associated to any predefined business locations but are used as dummy nodes for creating a meaningful hierarchy are defined under this section. These zones will not have maps and will not be used for zoning. For example: A zone by name "building" can be used as a top level navigational node but it will not represent a real zone on map. Example: <Navigation> <Zone zoneid="avena_motors" name="avena Motors"/> </Navigation> In the above example avena_motors represents the top level zone which is not defined as a polygon but it serves as a root node in the hierarchy ZoneConfig Tag ZoneConfig tag can help define overall zone properties like zone status etc. When a property is defined with ZoneConfig it will be applied to all the zones that are defined. OAT Asset Tracking Installation and Configuration Guide 76

77 Configuration for Zoning and Visualization Example: <ZoneConfig> <UIStatus> <Status name="full" bgcolor="ff0000"/> <Status name="empty" bgcolor="00ff00"/> <Status name="partial" bgcolor="0000ff"/> </UIStatus> </ZoneConfig> The name for status can be any valid string. The color is represented as RGB with each representing value between 00-FF. Colors as string like "red", "green", "blue", etc., are not supported, they have to be converted to RGB format. When scenarios change the status of zones / business locations to one of the status strings, then visualization UI will reflect the zone background with the appropriate color BusinessLocationHierarchy Tag This tag defines the zones Vs business locations mappings. Since OAT scenarios are associated with business locations and any scenario based changes at those business locations will be reflected in the respective zones (in the Visualization User Interface) as long as a relationship is established in the BusinessLocationHierarchy tag. Example:... location=... <BusinessLocationHierarchy> <BusinessLocation zoneid="assemblyparkinglot" "Assembly_Parking_Location /> </BusinessLocationHierarchy> RPMapping Tag This section defines the association between zones and read point locations. Each zone used for zoning must be mapped to a read point location. This helps the ZoneFilter to associate the zone with a location epc for logging add / remove read events. Example:... <RPMapping> <RPMap rplocation="assemblyparkinglot_rp" zoneid="assemblyparkinglot"/> </RPMapping> OAT Asset Tracking Installation and Configuration Guide 77

78 Configuration for Zoning and Visualization... NOTE: All business locations and read point locations must be defined prior to using them in the visualization configuration for zone mapping. 4.6 Visualization Properties Configuration This section describes the configurations to customize the User Interface parts of Visualization such as Asset icons, size, background and component configurations such as tab sizes, User Interface styles etc. Properties configuration is specified in the app_properties properties file located in the: <oat_install_dir>/ jakarta-tomcat /webapps/oatedge/web-inf/classes directory Following are the visualization specific variables that can be defined in the app.properties properties file: VIZ_DEFAULT_PIN_ICON: Relative URL for the default image icon to use for displaying assets. Example: VIZ_DEFAULT_PIN_ICON: =images/default.jpg Value is typically images/default.jpg. It is expected that all the images are placed under <oat_install_dir>/ jakarta-tomcat /webapps/oatedge/images folder. VIZ_DEFAULT_PIN_COLOR: Default background color for the asset icon. VIZ_GROUP_PIN_ICON: Relative URL for the group icon image for grouped assets. Example: VIZ_GROUP_PIN_ICON: =images/group.jpg VIZ_GROUP_PIN_COLOR: Default background color for grouped asset icon. VISUALIZATION_REFRESH_TIME: The time interval before the application sends a request to get updated asset information. Though visualization aims at displaying realtime data, the application waits for a data refresh based on this time interval. This interval can be as low as 10 secs and is always specified in milliseconds. Example: VISUALIZATION_REFRESH_TIME=10000 VISUALIZATION_TAB_NAMES: A comma separated string of content headings to be displayed on the visualization s properties pane. Example: Scenarios, Reports. This can be customized to have any textual heading depending on the data that is supposed to be displayed. The order of the heading in this comma separated string will be the order in which the lists of data will be displayed on the properties pane. Example: VISUALIZATION_TAB_NAMES=Scenarios,Reports OAT Asset Tracking Installation and Configuration Guide 78

79 Configuration for Zoning and Visualization VISUALIZATION_TAB_SIZES: A comma separated string of the percentage of area a data list should occupy on the zone properties panel. The order of the sizes / percentage values in the comma separated string, should be in sync with the order defined for VISUALIZATION_TAB_NAMES and VISUALIZATION_TAB_IDS Example: VISUALIZATION_TAB_SIZES=30, 30 VISUALIZATION_TAB_IDS: A comma separated list of ids to identify the correct data list. Example: VISUALIZATION_TAB_IDS=scenario,report VISUALIZATION_TAB_LIST_STYLE: A comma separated string of list styles that determine style for all the list elements within each list. 'Bullets' and 'Numbers' are the two styles that are currently supported. Example: VISUALIZATION_TAB_LIST_STYLE=bullets,numbers OAT Asset Tracking Installation and Configuration Guide 79

80 Chapter 5 Installing and Configuring on a Handheld Device This chapter explains the procedure to install and configure OAT Asset Tracking on a handheld device. Note that you need to use this only if you plan to use handheld devices and associated OAT Asset Tracking handheld scenarios. Sample use cases and scenarios are available to help in the process of installing and configuring OAT Asset Tracking handheld application. The samples.zip file provides example use cases to define the asset model configuration and configurations for locations, devices, scenarios and integration. Download this from the OAT Support Center s FTP site. 5.1 Pre-requisites Setup the following: OATxpress installed and the OATxpress Server running on one of the platforms supported for Asset Tracking (see Chapter 1 Pre-requisites). The wireless network on the handheld device configured for communication between the OATxpress Server and the device. Perform the following steps to test the connection: o o Click on Internet Explorer on the handheld device to open a browser window. Type the following URL in the location bar: The ipaddresss and port are the IP address and port of the OATxpress server. The OAT Foundation Suite login page appears. A desktop/laptop, on which Microsoft Active Sync is installed, available and connected to the handheld device through Microsoft Active Sync. OAT Asset Tracking Installation and Configuration Guide 80

81 Installing and Configuring on a Handheld Device 5.2 Installing OAT Asset Tracking s handheld application NOTE: 1. Copy the OATAssetTracking.cab file to the Application folder on your handheld device. Install the Asset Tracking application by double-clicking on the OATAssetTracking.cab file 2. Use the HandheldUI.xml file to customize the initial User Interface of your application. If you have downloaded the samples, copy the HandheldUI.xml file from the directory Samples/handheld into the Application/OAT Data folder on your handheld device. If you have not downloaded the samples, see OAT Asset Tracking User Guide for an example of the HandheldUI.xml file. Copy this file to the Application/OAT Data folder on your handheld device. Customize this file by modifying the asset-handling stations in this file. See the User Guide for more information. 3. Cold boot your handheld device. The files have to be copied into the Application folder before the installation for persistence across the cold boot of the device. On cold boot, the application is automatically installed and started. Hence the HandheldUI.xml file has to be copied before cold boot. 5.3 Configuring OAT Asset Tracking Handheld Application To configure this application, follow the steps outlined below: 1. Click on OATAssetTracking in the Start Menu on your handheld device. OAT Asset Tracking Installation and Configuration Guide 81

82 Installing and Configuring on a Handheld Device Figure 1 : Start Menu 2. Once the server is configured, login can happen with the username and password. 3. Message below is displayed, if tried to login when the OATxpress is not reachable. Click ok to login and go the configuration page below. Figure 2 : OAT Login OATxpress unavailable NOTE: If the cache contains the user credentials and the username and password are valid, the user is directed to application home page. If the username and password credentials are incorrect or if the cache does not contain the user credentials, then Invalid username/password is displayed as error. OAT Asset Tracking Installation and Configuration Guide 82

83 Installing and Configuring on a Handheld Device 4. Asset Tracking application s main menu is displayed. This menu is generated based on the sample HandheldUI.xml copied earlier. This User Interface can be customized. Refer to the Asset Tracking User Guide. Click Menu, at the bottom of the window, then click Settings within it. Figure 3 : OATasset The Menu list in the status bar consists of Settings, About and Exit options. Settings in the Menu list goes to configuration page. NOTE: Click OATServer to change the server information. For this to take effect, the application needs to be restarted. About in the Menu list gets the version details of the application. Exit exits the application. 5. The OAT Asset Tracking Configuration menu appears. OAT Asset Tracking Installation and Configuration Guide 83

84 Installing and Configuring on a Handheld Device Figure 4 : Configuration Menu 6. Click OAT Server in the Configuration menu, to set the IP address and port of the OATxpress server. Figure 5 : OAT Server Enter the OAT Handheld ID. Enter values of the OAT Server Hostname or IP and the port, as shown above. Click Save to return to the Configuration menu. OAT Asset Tracking Installation and Configuration Guide 84

85 Installing and Configuring on a Handheld Device 7. Click Device in the Configuration menu and make the following changes: Figure 6 : Device Set Attenuation to 0 for no attenuation or full power. Increase attenuation to reduce RF power. Check the Beep On Reading Tag to have the handheld beep when it reads a tag or scans a barcode. Leave the Maximum number of reads per read command at 30. This is the number of EPCs processed in one RF read cycle on the handheld. Check the appropriate Barcode Types that should be recognized by the handheld. These are listed in script number barcode format. Click Save to save your settings. 8. Click Locations in the Configuration Menu. OAT Asset Tracking Installation and Configuration Guide 85

86 Installing and Configuring on a Handheld Device Figure 7 : Locations (Main) Enter the timeout for the Webservice client (in seconds). Select one of the following radio buttons o o Don t store information locally - to not store the location information in the memory. Migrate all - to migrate all the locations available in the OATxpress. NOTE: On selecting Migrate All, Locations have to be migrated whenever any changes are made on the OATxpress server. o Migrate only selected (Default) - to migrate only certain locations from the OATxpress and save the location information. Click Selection - to display figure below to select the locations. OAT Asset Tracking Installation and Configuration Guide 86

87 Installing and Configuring on a Handheld Device Figure 8 : Locations (Selection) Click Get - to display locations in All Locations. Select the location from All Locations and click > to move the location to Selected locations. Any number of locations can be selected. Click Save, to save this setting. 9. Click Products in the Configuration menu. Figure 9 : Products (Main) OAT Asset Tracking Installation and Configuration Guide 87

88 Installing and Configuring on a Handheld Device Enter the timeout for the Webservice client (in seconds). Select one of the following radio buttons. o o Don t store information locally - to not store the product information in the memory. Migrate all - to migrate all the products available in the OATxpress. NOTE: Products and Locations have to be migrated every time any product or location changes are made on the OATxpress server. Click Save - to go back to configuration page. 10. Click on Reliable Messaging. Figure 10 : Reliable Messaging Default Show OATxpress status on status bar Select Policy Type Check to see the status of the connection and message queue icon at the bottom of the application. NOTE: If unchecked the connection status and the message status icon are shown as notification icons in the Windows notification bar. Select one from the dropdown list: Time Based Policy is based on the time specified in Time to Live, after which the messages will not be sent to OATxpress, and also will not be Checked Count Based Policy OAT Asset Tracking Installation and Configuration Guide 88

89 Installing and Configuring on a Handheld Device Default available in the queue. Count Based Policy is based on the number of retries specified in Maximum Retry Count, till which messages will be in the queue. NOTE: On selection of either policy, the other will be disabled. Maximum Retry Count Time to Live (in Minutes) Interval between two retry command (In Seconds) OAT Connectivity check Interval (In seconds) Queue size Queue size threshold Disk space threshold Enter the number of times retry is allowed. NOTE: This is used only when Count based Policy is used. This value is not editable. NOTE: This is used only when Time based Policy is used. Enter the time in seconds, after which the messages will be retried to be sent to OATxpess. Enter the time in seconds for the handheld to check for the status of the connection with OATxpress server. Enter the Number of Messages that can be stored while the OATxpress server connection is unavailable. Enter the percentage of messages that can be stored while the OATxpress server connection is unavailable. Enter the percentage of information that can be stored while the OATxpress server connection is unavailable. Default is 30. Default is 5. Default is 1. Default is 120. Default is 50. Default is 80. Default is Close the OAT Asset Tracking Configuration Menu. 12. Close the OATAssetTracking application. The Attenuation and Barcode Type settings (made in the Device configuration menu) take effect only when the application restarts. Your handheld device has now been configured to communicate with your installation of OAT OAT Asset Tracking Installation and Configuration Guide 89

90 Installing and Configuring on a Handheld Device Asset Tracking Message Information Figure 11 : Icons in OATxpress The icons in status bar indicate the following: OATxpress Status icon is updated based on the status of OATxpress connection. o o Shows the unavailability of OATxpress. Shows that OATxpress is available Message Status indicates the message queue size or threshold. o o o Shows there is enough storage in the disk and queue to store offline messages. Warning icon indicating the message queue size has reached the configured threshold value. Indicates disk space is not sufficient and no more data can be submitted. When OATxpress is offline all the messages are displayed in the Pending Message list. These messages are sent to OATxpress server, once the connection is restored and are displayed in Recent Messages. Pending messages displays the Message Type and the Message ID whereas the recent messages display the Message Type and the Response. OAT Asset Tracking Installation and Configuration Guide 90

91 Installing and Configuring on a Handheld Device Figure 12 : Message information If the handheld is restarted before transfer of messages happens the messages can be retrieved as the messages are stored in the persistent storage. Offline Messages are sent to OATxpress server once the connection is restored. On exiting the application (Asset Tracking), if any pending messages are in the queue, a pop-up message as displayed below appears. Figure 13 : Message Processing Click Yes, to exit the application. This completes installation and initial configuration for OAT Asset Tracking. For more information or for guidance on usage, please refer to the User Guide of this product. OAT Asset Tracking Installation and Configuration Guide 91