Wasp Asset
Key Info:
Wasp Asset is asset-tracking software from Wasp Barcode Technologies, formerly known as AssetCloud. It is designed to help organisations track physical assets using records, barcode or RFID workflows, mobile access, check-in and check-out, reports and configurable information about location, condition and ownership.
Details
Product identity and asset records
Wasp now uses Wasp Asset as the current product name for the asset-tracking product previously called AssetCloud. A migration or evaluation should account for this naming change in documents, integrations and user training. Asset records can document tags, categories, locations, users and lifecycle details. Test how older AssetCloud-labelled data and reports are represented so a rename does not create an artificial duplicate catalogue.
Tracking and control workflows
Barcode and RFID-based workflows can support entry, audit, movement and check-in or check-out of assets. The system can be used from mobile devices and offers cloud and on-premises deployment options. A trial should use the intended scanner, label stock and network environment, then simulate a damaged label, an incorrect transfer and an asset without an assigned owner. Check the audit history before and after a correction.
Reports and deployment choice
Wasp Asset includes reporting and access-control capabilities that can help teams monitor status and accountability. The cloud or on-premises choice changes responsibilities for backups, upgrades, access and integrations. Verify the exact edition, mobile support, data-import path, report scheduling, API or connector needs and retention obligations. Reconcile a sample audit report to a physical count before treating it as an operational control.
Evaluation record
Document the approved asset scope, identity rules, required fields, operational owners, source systems, retention, integration boundaries, test exceptions and acceptance measures. Keep fields for pricing, customer size, languages, operating systems and apps blank unless a current official source maps them precisely to the BBS field. Run a time-boxed pilot with a representative asset sample, named data stewards and a written exception log. Compare user actions, audit trail and reports against the present process. At the end, decide whether the product can support the required control model, what configuration or integration work remains, and which measurable result would justify a full rollout. Keep the pilot evidence in a decision record that another administrator can replay, including sample source files, permission settings, expected reports, failure handling, sign-off owners and the plan for migration, training and post-launch review.