TrackAbout Certified Devices - Revision history

Jfamularo: /* RFID Scanning Rugged Android Devices */ Add ECOM RFID

2023-01-10T21:49:38Z

RFID Scanning Rugged Android Devices: Add ECOM RFID

Jfamularo: /* Barcode Scanning Rugged Android Devices */ Add ECOM

2023-01-10T21:48:34Z

Barcode Scanning Rugged Android Devices: Add ECOM

Lsilverman: update hours estimate (by SublimeText.Mediawiker)

2022-03-23T20:15:48Z

update hours estimate (by SublimeText.Mediawiker)

Lsilverman: why is dev needed? (by SublimeText.Mediawiker)

2022-03-23T18:12:14Z

why is dev needed? (by SublimeText.Mediawiker)

Lsilverman: update (by SublimeText.Mediawiker)

2022-03-23T18:03:09Z

update (by SublimeText.Mediawiker)

Lsilverman: update (by SublimeText.Mediawiker)

2022-03-23T18:02:17Z

update (by SublimeText.Mediawiker)

Lsilverman: reorder (by SublimeText.Mediawiker)

2022-03-23T17:58:17Z

reorder (by SublimeText.Mediawiker)

Lsilverman: /* Barcode Rugged Android Devices */

2022-03-23T17:57:41Z

Barcode Rugged Android Devices

Lsilverman: /* RFID Rugged Android Devices */

2022-03-23T17:57:32Z

RFID Rugged Android Devices

Lsilverman: /* Featured Rugged Android Devices */

2022-03-23T17:57:13Z

Featured Rugged Android Devices

@@ Line 210: / Line 210: @@
+|
 :RFID
 |}

@@ Line 171: / Line 171: @@
 ;Hardware Scanner (Requires Configuration)
 :Code39, Code128, QRCode, DataMatrix (Tested, possibly more with Scanner software)
 |}

@@ Line 20: / Line 20: @@
 # Research device specifications - A TrackAbout engineer will evaluate the specs and capabilities of the device as advertised by the manufacturer. A particular area of focus is determining whether the device uses custom barcode or RFID scanning hardware. Scanning hardware usually requires software work by TrackAbout. It is necessary to integrate the manufacturer's software development kit (SDK) in order to fully enable the scanning function within TrackAbout's apps. Sometimes, the manufacturer provides a "data wedge" app which can send scans to the TrackAbout app, and integration is not required. This evaluation needs to take place.
 # If no custom hardware is present and no custom integration is required, TrackAbout will perform a certification. The customer will be responsible for the cost at the current labor rate. Testing takes between two and ten days and will have a minimum labor charge of 4 hours, possibly more depending on the complexity of the evaluation.
-# If custom integration is required, a negotiation regarding the labor requirements and scheduling of the work must take place, taking into account TrackAbout's other development priorities, and the size of the customer opportunity. '''For custom integration and certification, TrackAbout will require two devices, one for development and one for the QA team.''' Certification for a new device takes, on average, 16 hours of developer and QA time. However, it could take more time, depending on the complexity. An initial estimate will be provided and a statement of work agreed to before the work may start. The timeframe of the work will also need to be negotiated.
+# If custom integration is required, a negotiation regarding the labor requirements and scheduling of the work must take place, taking into account TrackAbout's other development priorities, and the size of the customer opportunity. '''For custom integration and certification, TrackAbout will require two devices, one for development and one for the QA team.''' Certification for a new device can take from 40-80 hours of software development and QA time. An initial estimate will be provided and a statement of work agreed to before the work may start. The timeframe of the work will also need to be negotiated.
 ==Why do devices sometimes require additional software development to be certified?==

@@ Line 21: / Line 21: @@
 # If no custom hardware is present and no custom integration is required, TrackAbout will perform a certification. The customer will be responsible for the cost at the current labor rate. Testing takes between two and ten days and will have a minimum labor charge of 4 hours, possibly more depending on the complexity of the evaluation.
 # If custom integration is required, a negotiation regarding the labor requirements and scheduling of the work must take place, taking into account TrackAbout's other development priorities, and the size of the customer opportunity. '''For custom integration and certification, TrackAbout will require two devices, one for development and one for the QA team.''' Certification for a new device takes, on average, 16 hours of developer and QA time. However, it could take more time, depending on the complexity. An initial estimate will be provided and a statement of work agreed to before the work may start. The timeframe of the work will also need to be negotiated.
 ==What if I want to use a non-certified device?==

← Older revision		Revision as of 18:03, 23 March 2022
Line 37:		Line 37:

	Outside North America, please ask the [[Contact Us\|Support Team]].		Outside North America, please ask the [[Contact Us\|Support Team]].
		+
		+	TrackAbout recommends not buying second-hand hardware from gray markets such as eBay. Generally, used hardware has a limited lifetime remaining due to aging of the batteries and the operating system.

	==Barcode Scanning Rugged Android Devices==		==Barcode Scanning Rugged Android Devices==

@@ Line 27: / Line 27: @@
 ==How to request device certification==
 Contact the [[Contact Us|Support team]]
 ==Barcode Scanning Rugged Android Devices==

@@ Line 55: / Line 55: @@
 |}
-==Barcode Rugged Android Devices==
+==Barcode Scanning Rugged Android Devices==
 {| class="wikitable sortable" border="2" cellpadding="4"
 |-

@@ Line 28: / Line 28: @@
 Contact the [[Contact Us|Support team]]
-==RFID Rugged Android Devices==
+==RFID Scanning Rugged Android Devices==
 {| class="wikitable sortable" border="2" cellpadding="4"
 |-