For UK enterprises running ServiceNow Hardware Asset Management, a ServiceNow-native locker application is the right procurement direction. Two reasons drive that verdict: native CMDB integration eliminates the reconciliation overhead that API-only alternatives create, and the operational ROI is measurable from the first pilot site.
Pro Tip: Before issuing an RFP, run a one-day ServiceNow HAM assessment to map your current asset normalisation gaps. Vendors who cannot align to your existing CI structure during that session will struggle during rollout.
A ServiceNow-native locker application is the correct procurement direction for any UK enterprise where ServiceNow HAM is the strategic platform for hardware asset governance.
| Point | Details |
|---|---|
| Buy direction | Choose a locker application that runs natively inside your ServiceNow tenant, not via API middleware. |
| Pilot first | Start with one UK site, two to three HAM workflow triggers, and four defined KPIs before scaling. |
| Critical red flags | Reject any vendor that cannot demonstrate on-tenant deployment and a current ServiceNow Store listing. |
| KPI to anchor on | A notable reduction in onsite engineer tickets is a published benchmark from Smart Collect® case evidence. |
| Smart Collect® | Velocity-smart’s Now Certified platform supports smart lockers, smart vending, and Smart Kiosk™ natively inside your tenant. |
The term “locker application” covers two entirely different markets. This guide covers only one: a smart locker system that runs as a certified application inside ServiceNow, controlling physical smart lockers, smart vending units, and kiosks while writing asset records directly to the customer CMDB.
Excluded from scope:
The distinction matters for three practical reasons. Procurement frameworks in regulated UK sectors require auditable asset custody chains. CMDB hygiene depends on records being created natively, not synchronised from a parallel database. And HAM workflows, including automated approvals and disposal orders, only fire reliably when the triggering event originates inside the tenant.
The core argument is governance, not convenience. A native application inherits your existing Role-Based Access Control without a separate user store, which means access permissions for locker transactions are governed by the same policies that control every other ServiceNow workflow. Audit trails are native records, not exported logs from a vendor system.
Asset lifecycle automation in ServiceNow updates CI and asset records automatically on deploy, swap, and retire events, and triggers transfer and disposal orders as part of standard workflows. An API-only locker product cannot guarantee that sequence without additional reconciliation work, and that work compounds across every ServiceNow upgrade.
Organisations that automate the hardware lifecycle with ServiceNow HAM gain real-time asset visibility and reduce manual reconciliation, which directly extends asset life by improving inventory accuracy. A locker application that writes natively to the CMDB makes that benefit automatic rather than a quarterly data-cleansing exercise.
Statistic callout: A UK utility running Smart Collect® cut shared-equipment loss and damage substantially, a result that depends entirely on CMDB records being accurate in real time, not reconciled overnight.
Evaluation should map directly to procurement risk. Integration depth is the primary differentiator: a native in-platform application keeps workflows inside ServiceNow and eliminates tab-switching and data reconciliation, whereas API-only approaches routinely leave the CMDB out of sync.
Numbered evaluation dimensions:
Red flags to reject at RFP stage:
The functional baseline covers three layers: hardware form factors, ServiceNow automation, and governance controls.
Hardware form factors:
ServiceNow automation:
Governance and audit:
Physical deployment is where well-specified locker applications fail in practice. Site readiness is the most common cause of delayed rollouts.
Site survey checklist:
Operational model:
Pro Tip: Map your locker locations against your existing IT support workflows before finalising placement. A locker positioned outside badge-access zones loses most of its 24/7 value proposition.
Commercial models fall into three structures: CapEx hardware purchase with an annual software support fee; Opex subscription covering hardware-as-a-service and software; and fully managed service where the SI partner owns operations. On-tenant deployment is available across all three, but confirm it explicitly, as some vendors default to vendor-hosted for Opex models.
| TCO driver | Notes |
|---|---|
| Hardware CapEx | Locker units, vending machines, kiosk hardware; varies by form factor and compartment count |
| Installation and commissioning | Site survey, power and network provisioning, physical installation |
| Software licensing | Per-tenant or per-unit; confirm ServiceNow release alignment is included |
| SI integration services | CI mapping, flow configuration, HAM workflow alignment; typically a one-off project cost |
| Consumables and maintenance | Ongoing replenishment, spare parts, firmware and hardware support contracts |
KPIs to track from day one:
A Devoteam session on HAM optimisation demonstrates how automated procurement and deployment workflows reduce manual effort and accelerate fulfilment, providing a practical reference for setting pilot success criteria.
| Phase | Activities | Typical duration |
|---|---|---|
| Discovery and HAM assessment | CI normalisation audit, stockroom mapping, network and power survey | 2–4 weeks |
| Pilot design | Scope one site, define success metrics, configure flows in dev tenant | 2–3 weeks |
| Integration and testing | HAM workflow alignment, CI mapping, UAT with IT and facilities teams | 3–4 weeks |
| Pilot go-live | Single site, live transactions, KPI measurement | 4 weeks |
| Enterprise roll-out | Phased site deployment, optimisation, SI handover | Variable by site count |
Dependencies that extend timelines:
Before contracting, verify the following artefacts, not just vendor claims about them.
Security and compliance controls in smart locker systems depend entirely on the audit trail being native to the ITSM platform, not exported from a vendor portal after the fact.
Smart Collect® runs natively inside the customer’s ServiceNow tenant. There is no parallel database, no middleware layer, and no separate vendor security perimeter to review. Asset state, device location, ownership history, and audit data sit in the customer CMDB as native records.
Capability summary:
Certifications: Now Certified / ServiceNow Store listed; ISO 27001 and ISO 9001 certified (Velocity Smart Technology, UK-headquartered).
A global pharma customer recorded a 500%+ uplift in IT service throughput and 83% faster fulfilment, per published Velocity Smart case studies.
| Evaluation criterion | Smart Collect® position |
|---|---|
| ServiceNow/CMDB integration | Native; no API sync or parallel database |
| Security and compliance | ISO 27001, ISO 9001; on-tenant; inherited RBAC and audit trail |
| Form factors | Smart lockers, smart vending, Smart Kiosk™ |
| Automation | Deploy, swap, retire, transfer, stockroom orders; HAM workflow triggers |
| UK operational support | Channel-led via ServiceNow Service Specialist Partners including Atos, DXC, SCC |
| Tenancy | Runs inside customer tenant; no vendor-hosted default |
The ServiceNow-native locker category is not emerging; it is proven. Enterprises that have already aligned locker management to ServiceNow HAM are reporting throughput gains and ticket reductions that were achieved on conventional ITSM workflows, before agentic AI entered the picture. As Now Assist matures and AI agents drive end-to-end physical handover workflows, those outcomes will compound. Waiting for further platform maturity means deferring measurable savings that are available today.
The practical recommendation: prioritise on-tenant deployment, validate with a single UK pilot site, and measure against the KPIs defined in the commercial section above. Organisations that pilot first and scale second consistently outperform those that attempt enterprise rollout without a controlled baseline.
The fastest path to a governed, CMDB-integrated device handover capability is a structured 90-day pilot at one UK site. Download the Smart Locker Whitepaper for the full technical and commercial decision framework, then book a ServiceNow HAM assessment with the Velocity-smart team to map your CI normalisation gaps before scoping the pilot.
The pilot scope should cover one locker form factor, two to three HAM workflow triggers (deploy, swap, retire) and the four KPIs listed in the commercial section: onsite ticket reduction, fulfilment speed, IT staff time recovered, and asset loss rate. Velocity-smart’s channel partners, including Atos, DXC, and SCC, can co-deliver the integration workstream inside your existing ServiceNow engagement. Request a pilot statement of work via the Smart Collect® product page.
Prioritise Now Certified and on-tenant deployment documentation when reviewing vendor materials.