Practical guide · Amulink
When a personal alarm project grows beyond a few samples, the team needs a reliable way to match each device to its current service arrangement. A simple device register can help prevent confusion during handover, maintenance and reassignment. This guide outlines a practical record structure for B2B teams evaluating Amulink WPD-01.
Give each device one clear record
Use the identifier provided with the device, or an internal asset reference agreed with your team. Confirm how the supplied identifier should be recorded; do not assume that every interface uses the same naming convention.
At a minimum, record the model, asset reference, current status, responsible team and date of the latest handover. Useful status labels might include sample, in evaluation, assigned, awaiting review and retired. These are suggested register labels, not claims about WPD-01 platform features.
Link the record to the service arrangement
A device inventory alone does not explain who receives an alert. Keep a controlled reference to the current SIM or service arrangement, receiving contact or monitoring service, and the person responsible for changes.
WPD-01 supports manual SOS and two-way calling. Confirm their actual configuration for the project and record where the approved instructions can be found. Keep passwords and other credentials out of an ordinary shared spreadsheet; use your organization’s approved access process.
Use a short handover checklist
- Confirm the physical device matches the register entry.
- Check the supplied accessories against the agreed package.
- Record who receives the device and who supports it.
- Complete an arranged SOS and voice workflow check.
- Record the instructions used and any unresolved action.
- Set the date or trigger for the next review.
For WPD-01, demonstrate the charging dock and the agreed manual SOS procedure using the supplied instructions. Our support plan guide covers the wearer’s routine; the register tracks the organization’s handover responsibilities.
Record changes with an owner and a follow-up check
A new contact, replacement SIM, change of site or supplier-approved configuration change can alter the service workflow. Record what changed, who authorized it, who carried it out and when the relevant check was completed.
Ask the supplier which settings or software details are available to your team and which changes require supplier support. Do not assume a particular remote management or update capability. Keep an accessible copy of the current approved operating instructions and ask for clarification when a change is unclear.
Retest what the change affects
A contact change calls for an arranged check with the new receiving contact. A SIM or network change calls for connectivity and voice checks. A new location may require fresh evaluation of positioning or geofence behavior.
Use our SIM and voice guide and geofence testing guide to organize those checks. Mark an item ready only after the relevant result is recorded, rather than merely after someone edits a field.
Handle reassignment deliberately
Before assigning a device to another wearer or project, confirm the approved process for removing or changing previous contacts, location rules and other service settings. Follow supplier instructions and the organization’s data-handling procedures.
Record the reassignment, the checks performed and the current responsible team. Keep unresolved devices clearly identified so they are not handed out accidentally as ready-to-use stock.
Make the register useful for support
When reporting a problem, the register should help the team identify the device, its current service arrangement, the last relevant change and the observed behavior. Record a concise description and the support outcome. Collect only the information needed for the task and restrict access according to your organization’s policies.
NIST’s IoT Device Cybersecurity Capability Core Baseline provides a starting point for organizations identifying the capabilities they need when acquiring or integrating connected devices. It is useful background for supplier questions, but a register alone is not evidence of product security or compliance.
Plan your WPD-01 pilot with Amulink
Explore application scenarios, consult the product resources, or request a sample for your project. Share your intended scale, operating region and service responsibilities so the evaluation can include handover and support from the start.
Source and editorial note
NIST IR 8259A: IoT Device Cybersecurity Capability Core Baseline (published May 2020; checked October 13, 2026) supplies the general connected-device acquisition context. This is an original operational guide, not recent news or a claim that WPD-01 meets the NIST baseline. The proposed register and handover process are Amulink editorial recommendations; available device and service capabilities must be confirmed for the deployment.