Equipment & Maintenance Inspections
- Starter – Record-Only: For this type of service you won’t need a validation database. When the app user scans an asset’s barcode, you will prompt the app user to enter information regarding the inspected asset. A tradeoff with record-only is that you cannot give directed information about that specific asset to the app user as they scan its barcode. For example, as they inspect an instrument that records temperatures, you might want to tell them what the correct temperature settings should be. You can’t do that unless you have a validation database. Another tradeoff is that you cannot use the text/voice-search feature to search a validation database. However, record-only services are a great way to start. << Check out our Step-By-Step Instructions. >>
- Intermediate – Validation: For this type of service you will need a validation database. When the app user scans an asset’s barcode, you will prompt the app user to enter information regarding the inspected asset. You can also give directed information about that specific asset to the app user as they scan its barcode. For example, as they inspect an instrument that records temperatures, you can tell them what the correct temperature settings should be. You can even use text- or voice-search for any/all items or just when an item doesn’t have a barcode. << Check out our Step by Step Instructions. >>
- Advanced – IT/Developer Integration: IT/Developers can seamlessly integrate codeREADr into their existing applications and back-end using our extensive set of APIs. The can also use advanced features such as regular expression, contextual variables and Webify.
Capturing Asset IDs: Scan barcodes, tap NFC tags, text/voice entry and/or search database
Assets most often need to be labeled with a barcode (low cost) or an NFC tag. Alternatively, you could simply label each asset with a human-readable number for text/voice-entry. Then, if you are using a validation database, you could use the apps Look-Up feature to simply search for the asset in the database and select (instead of scanning) – whether for hard-to-label assets or for all assets. It’s remarkably fast and accurate even when searching for the first few characters of an ID or name.
However, for speed and to minimize error, using a barcode is ideal for both record-only and validation services. For record-only services you should ideally label each asset with a QR code embedded with a identifier (e.g., Fire Extinguisher – Lobby #4). You can easily print QR labels using low-cost programs, such as iBarcoder for PC and Mac.
Alternatively you could use the barcode already on the asset or label it with one of the other barcode types (e.g., Code 39, Code 128, etc.), not necessarily a QR code. With a validation service this is no problem because you would have already associated the asset ID (barcode value) to the asset name (response text). See importing a CSV file.
However, with a record-only service, unless you use a QR Code, you will have to associate the asset IDs with the asset name when you do your reporting. Unless you are familiar with Excel or other database programs, that might be a lot of work – hence the reason to use QR codes with names for record-only services.