Questions

Product

This device is designed to monitor the movement of a person within a given (indoor) area.

• How big an area (minimum & maximum sizes)
• Is the area size customizable (by the user or admin) and modifiable or limited by device capabilities/range
• Is it always indoors, e.g. inside a dwelling (monitoring area, device mounting, device casing, lighting, temperature, power outlets)
• Do you need to understand the area, e.g. what rooms there are, where the rooms are in the area.  If so, is the area customizable (by the user or admin) and modifiable
• Do you need to distinguish between a person and other movement, e.g. a pet
• Do you need to distinguish between different types of movement, movement sequences, e.g. into and out of an area being a ‘complete action’

It should alert one or more contacts if movement is not detected within specific times.

• Minimum of 1 contact, is there a maximum number of contacts
• Is the contact list customizable (by the user or admin) and modifiable
• What type of messaging/alert is required, e.g. text, email
• Can you chose different alert types for each contact
• GDPR on contact details
• Are we keeping a log of the alerts
• If we are logging data – security and privacy considerations
• Is the alert a simple sound or a message giving where/when/what (or other detail)
• Does the alert have to be acknowledged (is it active or passive)
• Who sets the times, user or admin, are they modifiable
• Do the timeframes auto adjust for BST

It should be unobtrusive for the monitored person, e.g. no wearables or cameras

• Are we defining unobtrusive in terms of physical positioning or does it include financial and privacy considerations
• Mounting position, e.g. ceiling would give better range but would be more difficult to install/maintain
• If no batteries how is it powered, cables for main (positioning of same), what about solar input
• Casing can help to lessen visibility
• Should not interfere with existing devices
• Should not require additional technology/devices to be installed in order to use the product - Given the anticipated switch off of analogue phones, are we assuming all locations will have wifi available

It should be easy to install, setup and maintain (restart when it goes offline, no batteries to replace).

• Casing
• Positioning
• Power source
• User installation
• Setup of variables, e.g. contacts, areas, rooms?, times
• Modification of setup variables
• Storage of setup variables, e.g. local or remote at server (or both)
• Restart booting and auto start of the application (on power cut or reset)
• Do you need a reset to factory setting option (for recycling or reuse)

It should notify the contact(s) if the device goes offline.

• Do you need remote monitoring to tell you if the device is not online/responding (or would a device ping/heartbeat to the contact(s) be sufficient)
• If you went with ping/heartbeat, would those notifications be mutable
• Are all contacts notified
• Do you need to log/report an amount of time offline
• If logging this data – security/privacy concerns
• Do you wait for a specific amount of time before reporting an offline event
• Location of remote monitor
• What form is the notification in, e.g. email, text, descriptive, brief, same for all contacts
• Do you need to show that the device has power, wifi connectivity, e.g. light(s) (LED) on the casing

General questions (possibly for the developers)

• Have you checked that this type of device is not already available (we don’t want to reinvent the wheel unless we are doing this as an intellectual exercise for us as opposed to a really useful bit of kit for others to use)
• Do we have a specific budget
• Do we have any development constraints, e.g. skills, time, hardware

Notes for Derek

• Ambient activity patterns (definition, setup)
• Anomaly or emergency (who defines the difference)
• Client/server for monitoring, data storage, setup/installation/modification
• Power consumption limits