Project Canary - A connected, information sharing, workplace safety device. by Aidan Pattinson

Project Canary A connected, information sharing, workplace safety device. Aidan Pattinson

Project Canary

A connected, information sharing, workplace safety device. Aidan Pattinson

Acknowledgments Special thanks to my Honours supervisor Dr. Scott Mayson, and classmates for guidance and feedback throughout this year. I would also like to thank Chuan Khoo, Dr. Scott Mitchell, Cameron Leeson and David Barrett for their extensive assistance in developing electronic prototypes that were critical in making this project a reality.

RMIT University Industrial Design Honours Project A thesis submitted to RMIT University as part of the fulfilment of the requirements for the Bachelor of Design: Industrial Design (Honours), School of Architecture and Design Written, edited, photographed and designed by Aidan Pattinson. Supervisor: Dr. Scott Mayson ÂŠ 2015 Aidan Pattinson aidan@pattinsondesign.com aidanpattinson.com

Contents 11

Abstract

12 15 21

Formulating an Approach Framing the Problem Project Approach

22 25 28 32 35

A Market Behind Literature Review Existing Solutions Market Position Opportunity in Design

36 40 42 46

Context and application Contextual Requirements Technological Requirements User Requirements

52 57 58 61 62 65 72 82

Adding Information Particle IO IFTTT Freeboard Fritzing Initial Electronic Prototyping Proof of Concept Future Development

84 88 90 98

System Basis System Components Scenarios Software Solutions

106 113 129

Canary Monitoring Personal device Environment Device

140 144 149 150 153

Evaluation Key Process Decisions Electronic Function Product Design User Evaluation

154 159 160 163

Conclusion Project Possibility Adoption by Users Personal Reflection

170 166 167 168 169

Appendix References Image Credits Glossary of Terms Program code

Abstract Safety in the workplace should never be compromised, but unfortunately accidents still occur far too regularly. Current product solutions designed to ‘call for help’ do not provide enough of an obvious benefit for the general user to consider them a necessity or to promote the active use of them. Technology advances over the last several years have brought products like wearable fitness trackers and smart watches into the mass market. The sensing and visualisation of data these products use could form the basis for a new category of intelligent workplace safety technology. A device that promotes awareness of a users actions and environment, and is an effective fast response mechanism if an accident is to occur or a workplace is becoming unsafe. Project Canary seeks to stream-line workplace safety information delivery, by integrating with existing practices and providing a new system foundation that will incorporate safety and productivity management. Individuals will receive task information safety feedback, and accurate personal threat awareness warnings. This unified system of task information and threat awareness will aim to ensure use by the end user. Internet of things prototyping tools and technologies have been used heavily to rapidly generate an outline of a final devices function. This in combination with the creation of versatile physical housings ensuring the greatest flexibility of work applications.

Chapter 1 Introduction

Formulating an Approach

Current product based solutions used to monitor workers in high risk or isolated environments have in most cases not kept up with the technology available to solve the problem. Designing and implementing new technology can be a costly and time-consuming process, which is creating a lag in development of modern safety technology. Not providing current solutions could mean that users are going through a poorer user experience than could be available to them. Would trade workers use, and feel a higher level of safety if a smart device was monitoring them and their environment in the same way, their phone or smart device does their home or daily fitness routine? The same sensors and processing ability found in general wearable devices are now cost effective and available enough to be used in things like safety products. Once a base is developed, the solution could potentially update more regularly at a reasonable cost.

Instead, it could be viewed as a product present to improve the safety of the whole work area, and for everyone in it. Currently digital monitoring of workplaces are performed by large, specialised products with equally specific applications. There is currently no personal monitoring solution that is widely available and applicable or adaptable to any number of trades. This research seeks to explore if such a solution could be developed that provides the necessary safety benefits to a big corporation, but also the flexibility required to a single person, or small business owner.

If this category of solution is successfully designed, a user may not see it as a badge of incompetence.

There is currently no personal monitoring solution that is widely available and applicable or adaptable to any number of trades.

Equipment carried and used every day by a potential end user.

Chapter 1 Introduction

Framing the Problem Current product based solutions used to monitor workers in high risk or isolated environments have in most cases not kept up with the technology available to solve the problem. Designing and implementing new technology can be a costly and time-consuming process, which is creating a lag in development of modern safety technology. Not providing current solutions could mean that users are going through a poorer user experience than could be available to them. Would trade workers use, and feel a higher level of safety if a smart device was monitoring them and their environment in the same way, their phone or smart device does their home or daily fitness routine? The same sensors and processing ability found in general wearable devices are now cost effective and available enough to be used in things like safety products. Once a base is developed, the solution could potentially update more regularly at a reasonable cost.

If this category of solution is successfully designed, a user may not see it as a badge of incompetence.

The Spark Core, WiFi development chip.

The Internet of Things The Internet of things is a relatively new product, service and software category that is used to define products often labelled as â&#x20AC;&#x2DC;smartâ&#x20AC;&#x2122; things. It includes objects, websites or apps that are created to connect people or solve problems utilising technology, wireless communication and the internet. This field consists of the creation quality, mass produced products, designed to enhance and improve the function or activity it is needed for, by connecting the device with the vast amount of information available on the internet, or to other devices via a wireless communication protocol. The product may be fixed in a users home or office, portable, potentially for use in a car or while traveling or physically attached to the users, such as smart watches, fitness trackers or Google Glass type products.

Due to the large amount of data that is being recorded by many of these devices, and their ability to connect to the internet, users privacy is a big issue that will become more important to the users of the technology (Walther, 2011). This of course will be a potent and reoccurring issue this project will face, and will require constant and careful ethical consideration for the user and the information the product may be processing.

Due to these reasons the device must be unobtrusive, seamless, and demand as little attention as possible, until its functionality requires it to. Due to the drop in the price of components used to facilitate connection of objects to the internet, Internet of thing devices are appearing for more and more activities and purposes. The field is incredibly vast and is expanding. Most of these are aimed at improving performance, adding functionality, or caring for mental well-being (Trend Watching, 2014). They are often used to record information and present it to the users to show use statistics and potentially progress with that activity. More importantly, link with a users other devices, such as a smartphone where they can share it to other products or services.

Project Canary

Introduction

Spark Core based electronic prototyping.

Open Development While this project, if undertaken by a larger company or consultancy, would be completely internal or in-house, a large portion of the development being undertaken in this project could be considered open-development. Primarily the electronic prototyping and development that has been used to prove the concept and potentially develop a working end solution. There are many tools available to anyone seeking to create a new Internet of Things product. The key tools used to develop this project are explained in subsequent chapters of this book. Often these tools have a large and extremely helpful internet based community. This community often posts tutorials of certain key techniques, detailed instruction of their own projects, and also frequent community forums where users post issues and solutions to their own projects. As these prototyping tools will most likely be used to produce outcomes in this project the final outcome may need to be labelled as a result of open source development with accreditations to those who helped along the way, depending on the weighting of these enthusiasts input to the project.

Introduction

Project Canary

Project Approach This project was initially going to be approached firstly as a product design project for the construction industry, with some exploration into the software and underlying electronics that would make it possible. It was quickly realised the importance the internal components and their function would have not only on the possibility of the idea as a whole but on the physical product. The initial stages consisted of divergent and convergent development cycles, aimed at producing a design proposal that was accurate to the initial aims, has a strong user applicability, and real market need. This was performed in conjunction to research and development into a basic electronic solution aligning with the design proposal.

Project Canary

Introduction

Chapter 2 The Field

A Market Behind

Can a digital product, with a connection to the worker and their environment, and the capacity to process information in real time, replace or improve users day to day experience and safety?

Literature Review

The field of workplace safety is just beginning to add technology to their workflow but is lagging behind other industries. Rather than fitting into one field this project aligns to is an intersection of the following three technology for high-risk Can a areas. digitalConceptual product, with a connection to the worker environments, ever iterating internet technology and their environment, and the capacity to process products, and workplace safety hardware. information in the realfield time,ofreplace or improve users day to day experience and safety? Research conducted in this project been based on workers, safety conditions and safety to add TheAustralian field of workplace is just beginning requirements considerations be made to make technology tobut their workflow butwill is lagging behind it international andfitting available. other industries.applicable Rather than into one field this project aligns to is an intersection of the following This is an opportunity for a leap forward threeproduct areas. Conceptual technology for high-risk in personal protective equipment andtechnology accident environments, ever iterating internet prevention technology, simply through the addition of products, and the field of workplace safety hardware. relevant and accurately shared information. Research conducted in this project been based on Australian workers, conditions and safety requirements but considerations will be made to make it international applicable and available. This product is an opportunity for a leap forward in personal protective equipment and accident prevention technology, simply through the addition of relevant and accurately shared information.

The Field

This product is an opportunity for a leap forward in personal protective equipment and accident prevention technology, simply through the addition of relevant and accurately shared information.

Chapter 2 The Field

Literature Review Can a digital product, with a connection to the worker and their environment, and the capacity to process information in real time, replace or improve users day to day experience and safety? The field of workplace safety is just beginning to add technology to their workflow but is lagging behind other industries. Rather than fitting into one field this project aligns to is an intersection of the following three areas. Conceptual technology for high-risk environments, ever iterating internet technology products, and the field of workplace safety hardware. Research conducted in this project been based on Australian workers, conditions and safety requirements but considerations will be made to make it international applicable and available. This product is an opportunity for a leap forward in personal protective equipment and accident prevention technology, simply through the addition of relevant and accurately shared information.

Project Canary

The Field

Users in Concern Not confined to a single profession, the solution focuses on three groups of users. These categories may suit a vast number of different professions not limited to trade work. While the final product produced may not be ideal for all areas, it should be able to adapt to different applications with a small change to elements of the product. This may include sensors or attachment methods. Foremost, people who work in some form of isolation, which may be, but is not limited to people working in remote areas where there are limited forms of communication available. It also covers workers who may be close to others but have the chance of going unobserved for extended periods of time, construction workers on a large site for example. This category could also include workers who are new to the job or an environment, they may be unsure of the surrounding dangers, or the potential hazards of work equipment. Australian Bureau of Statistics (ABS) found the highest number of workplace injuries and illnesses are affecting the twenty to twenty-four age group. (ABS, 2014) This users potential hesitation to seek help means they could be considered â&#x20AC;&#x2DC;isolatedâ&#x20AC;&#x2122; in a workplace. High-risk workplaces, where there is a risk of someone being seriously or fatally injured. People may also be doing this kind of work in isolation, or in a larger work site. This category contains the largest number of users, but it is where the implementation will most likely be needed. Primarily it will consider users working around dangerous machinery, but also vehicle operators and workers in the vicinity of other vehicles. Research conducted in the United

The Field

Project Canary

States found the deaths of over 600 workers between 2004 and 2006, was due to contact collisions with construction equipment. (Teizer, Allread, Fullerton, & Hinze, 2010) People working in environments that have the potential to cause harm after extended exposure are also be considered. This may include people from a large range of professions, potentially including mining applications Finally, to design for a workplace where there are multiple people using the product. Further development in this particular area may open up opportunities to design a more expansive system. Creating a safety network monitoring more than the user and their environment but potentially separate fixtures or moving machinery as well. The ABS also reported the ratio of injuries amongst owner-workers and employees being almost ninety percent to 10 percent respectively. (ABS, 2014) An intervention implemented amongst a large work group where users are at a greater risk is more applicable than users on their own.

Primary Discourses Taking into account how wide a field that has been considered, a general hierarchy of project discourses has been formed. To provide a safer work environment for the users of the final product, which should not be confined to the user groups discussed, but should also include extreme users, such as enthusiasts or private users who find the functionality appealing. The product should extend to provide the same environment for those around the user which should include but is not limited to colleagues and co-workers.

To not appear as a badge of poor work practice, that will prevent a person from using the device. Or a new user or company to be discouraged from using it. This is applicable to both the electronic function, and the products visual language.

To create a solution that has an obvious benefit to the user, or company implementing the product. Making its use in the workplace obviously necessary. Current product solutions do not provide enough of an obvious benefit for the general user to consider them necessary, and actively use them.

Current product solutions do not provide enough of an obvious benefit

To provide aÂ solution not specific to oneÂ application, but adaptable to suit different professions or trades. This has been achieved by designing a widely applicable product, with the potential to change internal components upon adoption.

for the general user to consider them

To accurately perceive what is taking place and reliably notify without false alarms, as well as moderating notifications sent to workers or supervisors so as not to become an annoyance or distraction.

necessary, and actively use them.

Project Canary

The Field

Existing Solutions Initial research into what is available to companies or private workers has shown there are a number of general features that most products will use. These features could be used to define the current device categories. The most common being, alarms, location alarms, environment sensors, and fall/ mobility monitors. Many of the devices, labelled as â&#x20AC;&#x2DC;man down alarmsâ&#x20AC;&#x2122; are designed to sense a period of inactivity by the user, and then sound a high pitch alarm, calling for help. The vast majority of these devices are designed to be worn on the user, but they are overly bulky and obtrusive during tasks. This outweighs the small benefit the post-incident alarm provides a worker. Alarm based systems with no other form of communication ultimately rely on someone to hear and respond to the alarm and come to a users aid. This is an unacceptable waste of time in what could be a very time important situation. There is also the chance that no one will hear the alarm, or may not know the significance of it if heard, this is especially relevant for users working in isolation, and even noisy environments. There are solutions not related to trade industries that have similar functionality. Global positioning system locators and personal safety beacons are providing a lot more functionality and reliability for the user than the abovementioned alarm systems. If targeted to communicated with the right people, it has the potential to greatly decrease response times from accident to help.

The Field

Project Canary

The critical framework to be used to review products already being used in the work environment Where or how it is connected with the user: This section is to describe how the user is supposed to interact with the product, where it is intended to be worn or how it is connected to the user during use. Ability to monitor the user: A brief description of how the product monitors the user or environment. Monitoring/alarm system: A description of how the product monitors the user or environment, and what system if any, the product uses to notify others or call for help. A summary could also be included to evaluate if similar functionality could be included in the project. Reliability: An assessment on the reliability the user could place in the above factors. Aesthetics and functionality: A brief assessment of the products visual language and any key functionality not mentioned so far.

Grace Industries Super Pass II

Where or how it is connected with the user: The Super Pass II is designed to connect with the user via a fairly cumbersome alligator clip. Most likely intended to attach to the belt or pocket edge the clip levers close with a tight grip ensuring it wont come loose during regular use. It is however very hard to access the clip for fast removal, even without gloves. The clip also does not keep the product steady which could create inaccuracies with the monitoring functionality discussed in the following section. The monitor also has a metal loop designed for use on a lanyard. While it is useful to provide this option, some monitoring ability may be compromised. Ability to monitor the user: What could be considered a very basic entry into work place safety monitoring, the Super Pass II has been designed to monitor movement, and excessive environment temperature. Once on, the device will monitor both of these, alarming if the device is completely still for 30 seconds, or if above pre set temperature ranges, i.e. 200Ë&#x161;F for 12 minutes.

Monitoring/alarm system: When alarming the device outputs a 98+ decibel tone increasing in volume as time progresses. Reliability: Considering the devices basic functionality, it is relatively reliable, the biggest concern is its battery life. It runs off a 9v battery which is required to be changed every two working weeks. There is no known notification of a low or flat battery, it simply doesnâ&#x20AC;&#x2122;t turn on. The device is also hard to easily understand and operate, and considering there are only three buttons, could easily be put into manual alarm mode while trying to switch it on or off. Aesthetics and functionality: The Super Pass II is very much a typical work place product. As shown it is essentially a high-visibility-yellow rectangular box, with an equal 5mm fillet on every edge, and excessive and in your face branding in place of some greatly needed operation instructions or graphics. The device while rugged is not over the top styled as such, which is a positive. But it could be designed to fit in close to the user instead of loosely hanging off the clip. (Grace Industries, n.d.)

Project Canary

The Field

BlackLine GPS ‘Loner SMD’ Where or how it is connected with the user: Unfortunately, the first noticeable negative of the Loner SMD is the attachment method, it uses the same tension alligator clip used in the Grace Industries Super Pass II. While it may not be as much of a negative due to the more streamlined shape, the product it sill heavy enough for the non-fitted nature to potentially cause an issue with the builtin sensors. The user is also required to connect the device with a computer to configure its use case, settings, sensor sensitivity and emergency contacts. This is all browser based and appears to be relatively user-friendly. Ability to monitor the user: The Loner SMD is a great leap forward in workplace safety monitors, the system Blackline GPS provides is well thought out and widely diverse. Built into each device are sensors designed to be versatile by diagnosing a number of potential eventualities without needing advanced components. It is advertised to monitor a users motion, fall monitoring, current GPS location and historical ‘bread-crumb’ location. (Blackline Safety, n.d.)

The Field

Project Canary

Monitoring/alarm system: The Loner SMD features bright flashing LEDs and a high pitch tone when alarming. What puts the Loner SMD above the rest is the service provided by Blackline GPS that will respond to the alert and GPS location and provide the necessary response by contacting the emergency services. Reliability: The wearable appears to be very reliable, and if there are false alarms, the response system should prevent any negative impact or response to the alarm. A product ecosystem has also been developed to improve the accuracy and applicability of the system with a wider range of user groups. The ‘Loner Beacon’ (Blackline Safety, n.d.) provides GPS accuracy indoors, and the ‘Loner Bridge’ (Blackline Safety, n.d.) extends the range to isolated workers by adding satellite communication as a replacement for cellular. Aesthetics and functionality: The Loner SMD does not conform with the typical ‘highvisibility’ aesthetic but follows more of a slightly rugged style medical product. The feed-forward of the emergency functionality and interaction is effective, and emergency lighting is positioned well, so it stands out to both the user and responding persons.

MSA Altair 5X Where or how it is connected with the user: The device attaches with a slim clip, slightly less bulky and sharp as that previously reviewed on the Grace industries Super Pass II. The clip has a similar lanyard or strap type mount available, along with a docking and charging station when not in use. Ability to monitor the user: Aimed at being used on a person, not in an environment, the Altair a few main features that extend its capability and overwatch on a user. While monitoring for hazardous substances, the device also monitors the users motion, detecting if they potentially collapse or fall while working as a result of an accident or hazardous gas. The Altair also has the ability to communicate with other devices close by, warning that user if the first device detects a drop in air quality or no motion from the user. (MSA, n.d.) Monitoring/alarm system: Aimed at being used on a person, not in an environment, the Altair a few main features that extend its capability and overwatch on a user. While monitoring for hazardous substances, the device also monitors the users motion, detecting if they potentially collapse or fall while working as a result of an accident or hazardous gas.

The Altair also has the ability to communicate with other devices close by, warning that user if the first device detects a drop in air quality or no motion from the user. (MSA, n.d.) Reliability: A small but relatively clear display is also present on the front of the device, showing the air quality test results for each substance and a small diagram gauging the danger level if the user doesnâ&#x20AC;&#x2122;t understand readouts or percentages. The only downside I could observe being that it does require interaction and some attention to get the best most accurate results out of the monitor, but that operation could easily be integrated into the workplace practice. Aesthetics and functionality: The Altair is larger in size than the other products tested. The body consists of a fully encasing poly carbonate housing, with transparent sections for warning lights, sensor inputs and the display. Under the display are up, down and power buttons that are the inputs for the system. The buttons basic function are easy enough to understand, but the buttons have multiple functions depending on what menu the user is navigating through. Extended use would be needed to ensure a user retains familiarity and understanding of operations. (MSA, n.d.) Project Canary

The Field

Market position

User experience design The process of meticulously developing every aspect of a product to improve the quality of interaction with the end user.

Personal safety Accident, injury and motion detection. Scheduled check in times. Location specific notifications. Small in size. Simple to use and interact with.

Environment safety Accurate detection of device surroundings. Vastly capable sensors. Workplace or industry specific. Large in size. Portable or fixed.

The Internet of Things Connected to popular services, or devices via the internet. Visualisation of monitored data. Capable or performing multiple functions Short product life-cycle. High weighting on design, usability and quality of construction.

Project Canary This project sits in a field that is a combination of others, rather than belonging to a single field. It is not a traditional work place safety product, nor does it completely align with products and services being created in the Internet of Things category. The combination of a highly capable personal safety monitor, with a reliable and accurate environment safety monitor. Including the addition of an almost Internet of Things type approach to information sharing and connectivity. Would be where a solution would be most successful in being developed. For the final product to be well received by the stake holder groups, a large emphasis must also be placed on the influence of user experience design.

Opportunity in Design The most evident gap in the marketplace is to provide a simple solution that effectively alarms if the user is in an accident but to also attempt to notify before a potential event and act to prevent injury or accident. The solution must take a number of things into consideration to be effective and applicable to the widest range of users. It must be designed for the most rigorous situations, but also for everyday wear if required. The opportunity to create a modular solution could also be explored. A device that can have components changed to better suit particular applications. As well as supporting products that could be implemented around the device to increase accuracy or provide additional environment information. The system should be able to fully integrate with existing systems, software and products to greater increase the user experience. In addition to any supervisory systems used to organise work. A successful solution cannot be at any time a hindrance to a user, and must be used effortlessly.

Project Canary

The Field

Chapter 3 Context and Application

A Market Behind This Project This project has been undertaken to address work place safety and accident prevention in a technological and connected time. It will need to address many contexts depending on the occupation and setting of the user, but generally may refer to a number of use cases, within this time line of consecutive events. Potential immanency of an accident, post accident and currently engaged in tasks, which may refer to most other activities. These time brackets have very different events happening in them and cover a broad range of eventualities. For the product to be applicable to these contexts a heavy emphasis should be placed on a streamlined communication and response method. Developing a solution that will effectively solve those problems will be difficult and may present a task with greater difficulty than developing a physical safety product. However, if correctly implemented it will have an adversely positive effect on a users experience in an environment in regards to personal safety. The end user, will still need to undertake a number of interactions to user the device, therefore the physical interaction must be simple, straight forward and require less thought and attention than the task currently underway.

Context and Application

For the product to be applicable to these contexts a heavy emphasis should be placed on a streamlined communication and response method.

Chapter 3 Context and Application

This Project This project has been undertaken to address work place safety and accident prevention in a technological and connected time. It will need to address many contexts depending on the occupation and setting of the user, but generally may refer to a number of use cases, within this time line of consecutive events. Potential immanency of an accident, post accident and currently engaged in tasks, which may refer to most other activities. These time brackets have very different events happening in them and cover a broad range of eventualities. For the product to be applicable to these contexts a heavy emphasis should be placed on a streamlined communication and response method. Developing a solution that will effectively solve those problems will be difficult and may present a task with greater difficulty than developing a physical safety product. However, if correctly implemented it will have an adversely positive effect on a users experience in an environment in regards to personal safety. The end user, will still need to undertake a number of interactions to user the device, therefore the physical interaction must be simple, straight forward and require less thought and attention than the task currently underway.

Project Canary

Context and Application

Contextual Requirements The potential use cases for this product could be considered subcontexts within the main contexts of during work, unsafe work practice, and post accident or injury. They all aim to achieve the result of a safer workplace for the user and those around them, irrelevant of the contexts position in the aforementioned timeline. These subcontexts are not confined to a single occupation or workplace, but more depend on how the product solution may interact with the user and workplace environment during that particular task.

Context and Application

Project Canary

A wearable solution that may include products that are worn on the user, or attached to their body or work wear temporarily or permanently by some form of mechanical fixture or adhesive. While this may be an effective way of applying to the user, it is very intrusive on the user and their work capacity and a large amount of development would be necessary to reduce its obtrusiveness. Current examples of this not related to the context of work safety are smart wearables like watches or fitness trackers.

Environment sensor solutions may fit into any of the above mentioned contexts, but has the specific function of interacting with the work environment, and its digital presence to perceive hazards to the user that will have an effect over an extended period of exposure.

A product based solution may refer to a device like a mobile phone, that is carried by a user, with out a physical or mechanical attachment to the user or their clothing. This may not provide the most accurate of sensing capabilities. If the device is enclosed or covered in a bag or pocket, air quality or ambient light may not be effectively measured. A device that is fixed to the work environment for the duration of the work, which may have heightened sensing abilities, due to the lack of a restriction of size or power consumption. While it may not be most applicable as a user sensor, it could be used to increase the accuracy or communication abilities of the user devices. Solutions that are attached to external equipment, or vehicles, that are not primarily related to this projects main focus on the user, but may be incorporated to work with a main device. These sensors could be powered, or passive and may require the on user or environment device to locate them.

Project Canary

Context and Application

Isolated workers

â&#x20AC;&#x153;As this device may be required to send a wide range of notifications to a user or supervisor, the format of the information delivery must be clear and concise.â&#x20AC;? High-risk workers

Groups of workers

Context and Application

Project Canary

Technological Requirements Sensor information will be processed to take into account a number of factors before communicating a warning.

Foremost, the largest issue faced by this particular technology product is accurately diagnosing events in the space around it. This has been approached by including multiple sensors on the device, so the product can gauge several things about the users environment at once. Sensor information will be processed to take into account a number of factors before communicating a warning. The device will check the relevant information against preset calibration levels. The device will confirm the high reading is accurate with other devices nearby. Finally check if the high reading is a potential threat in that devices location. Secondly, something that is not related to the products ability to monitor an environment but is arguably one of the most crucial parts is the products battery. This is only applicable to mobile sub-contexts that do not have an independent source of power. This product will need to be constantly on while the user is in the workplace or potentially hazardous environment to be effective. Conceptually, this would be responded to by the device powering up or down during monitoring the user, in response to the sensor inputs or the distance from other devices. The closer one device gets to another, less strain is put on each devices sensing frequency. Further research into the possibilities of new and innovative mobile power options should be explored, but to keep the project in the realms of current possibility, a systems approach may be more effective at managing this requirement. This may include smart controlling of what features are online and when, chargers located in common

Context and Application

Project Canary

work areas, nightly charging, or location based zones (filtered by hazard level) where the device is off or on and in what capacity. Location sensors are required to accurately position a device if it determines the user needs to be contacted. This may take place before or after an accident. Location information will most likely be performed by a GPS module, but considerations will have to be made to increase that parts accuracy in certain environments. Blackline GPS include the previously mentioned â&#x20AC;&#x2DC;Loner Bridgeâ&#x20AC;&#x2122; product that connects to the wearable device and communicates the location via satellite, it is more accurate but requires a large secondary product. (Blackline Safety, n.d.) Research has also been undertaken into how to improve GPS single is transmitted in urban environments, through the use gyroscopic sensors and information sharing with location-enabled mobile devices. (Tan, Chu, & Zhong, 2014)

This product has the obvious requirement of being equipped with the ability to communicate with an external party, co-worker or emergency service. This will be all the more effective, as the device will be able to determine exactly what is happening to a user, and determine if the threat requires help from someone nearby, or immediate response from a higher authority.

Integrated environment sensors are a simple way to make this project more widely applicable. The sensors can be used for their main function, potentially including gas or hazardous substance detection, air quality, ambient light, temperature, or they could be used to recognise correlations in readings or with other sensors that may signify other situations. A worker may be in a space with low ambient light, this may mean they are underground or in a confined space. The product could then begin monitoring air quality to determine if that space is, in fact, safe, and if not how long the user can be there before they could harm themselves.

Project Canary

Context and Application

â&#x20AC;&#x153;Sensors focused at monitoring the users environment play a big role accurately diagnosing situations before they have a chance to occur.â&#x20AC;?

Context and Application

Project Canary

User Requirements While it is crucial for this product to appeal to every user, realistically it may not be an average users choice on whether or not it is implemented. It will be most commonly used and potentially most effective if implemented in large trade companies, with a group based workforce. Isolated and lone workers will still be a high priority for development as well, but will not have the same advantage of information sharing as the former use case. The products ability to track its location is critical to the function of the device. All the other included sensing technology would be useless if it did not have some way of communicating a users location if there was something to go wrong. However even with its benefits, this feature may not appeal to a large number of people. Especially in the context of a large company, the average worker would not want to have their location and activities tracked. To satisfy these concerns, it was determined early in the product development that the user needed to have control over when they were being monitored or not. This is solved by using a simple ‘working’ or ‘not working’ switch on the product. To ensure that the device is always in operation when the user is actually working, this switch could also be used to log the workers hours on the job. However, if a user forgets or does not switch on the device, they will still be notified of some threat information if shared from near by devices. Some industries, especially where there is a group based work environment, may have issues with their perception of safety equipment, not as a necessity. Especially one that

Context and Application

Project Canary

does not have the obvious benefits of engineering based safety like a helmet or scaffolding. This problem could be solved by ensuring that the products user experience is very well defined and flawlessly carried out, so at no point is it a hindrance to the user. The idea that this product will only need a two-step interaction to operate (unless in an emergency) works towards this goal. The trial implementation of the products may be enough to make the benefits known to the user, and hopefully the device will become as much a part of their work life as other smart products have with the rest of their lives. Crucially, a successful solution must not be hard to operate, or view information on. As previously discussed, some users will be operating in high-risk environments, where there is little time or room for distraction. The device must turn on, and function autonomously with little input from the actual user. Unless the users attention is required. When it is required that the user interact with a product, interaction must be clearly communicated and the touch points must be obvious as to their function. Providing the user with obvious feed-forward of a parts function or the meaning of a flashing light emitting diode is very important in ensuring that the product requires little cognitive load from the user. These events may be few and far between, it may have been some time since a users training in operating the device. The product should treat each situation as if the user has this level of knowledge.

It was determined early in the product development that the user needed to have control over when they were being monitored or not. This is solved by using a simple ‘working’ or ‘not working’ switch on the product.

Project Canary

Context and Application

Chapter Summary What is it? What is being proposed is a set of electronic devices for use in trade workplaces. One, mounted on the worker featuring a number of sensor inputs, customised upon implementation to be relevant to the workplace it is being designed for. The second fixed in the environment while still being portable if necessary. Both housed in a form that fits into the final environment while challenging current safety product styling and features. But still user-friendly and capable of performing reliable and with little user supervision as possible even in most rigorous situations.

Simply because of the likely expensive development and implementation cost that would be incurred to bring the rest of the workplace into line with the new practices. Even considering the fact that it will most likely be adopted by such large companies, the isolated or owner-worker should not be left unconsidered.

The products will be bundled with a system and software solution that will incorporate every aspect of the users work. From user safety profiles, to task management.

Why is it what it is? This project was created to inspire the adoption of â&#x20AC;&#x2DC;smartâ&#x20AC;&#x2122; products and digital information sharing in industries typically not identified as those most up to date with what technology can bring to the workforce. As well as to challenge the industry of the internet of things, to break the mould of what is possible with integrated technology products, and to present a future of more than just consumer level products in the Internet of Things field.

Who is it for? Designed for the key user groups defined on previous pages of isolated, high-risk and group workers this device should be applicable to an enormous range of users. These groups were identified and defined for that exact purpose, so as to create a set of stakeholders that would inform the creation of the most diverse product solution. There will also be professions not originally considered that will also find the functionality beneficial. Due to this point, decisions made during development will need to consider all users, and the result may be required to cater equally to each group rather than perfectly fitting one user group.

Further than just speculation of what the internet of things can do to the industry, this product would legitimately provide real value to the safety of every user. An effective and reliable first and last line of help that will provide action to accidents faster and more effectively. Building on this point, it is a necessary development to create a precedent of what a more intelligent safety product could do for the workplace. This should allow more products to come through as technology is integrated into more aspects of every high-risk workplace. Challenging the hard lined and structural approach to workplace safety will even be necessary for the future.

Where will it be implemented? It is most likely that this product will be initially adopted by large workforces, or government controlled industries. Project Canary

Context and Application

Chapter 4 Methods

Adding Information Key Tools This project was originally intended to be approached with a higher emphasis on user-centred product design, especially during the early stages of formulating what the best solution would be. What needed to be avoided, however, was this project being turned into a theoretical concept, with no grounding in what is physically possible. This meant the approach needed to be modified from what would have been ideal to what was possible to create now. When researching what is currently in the market, the realisation that the success of a product was almost an equal weighting between its user friendliness and applicability to the worker, and the functionality achieved by the electronics and integrated technology became apparent. To test and develop what exactly is possible for this product and to gain an understanding of the current field of connected devices, a greater emphasis needed to be placed on electronic prototyping than traditional product development. Beginning research into the practice of electronic prototyping revealed a number of simple but effective tools that greatly assisted the development of this project. A solid understanding of what function the device is performing even formed a base for future product development as is discussed in this chapter.

Methods

â&#x20AC;&#x153;To test and develop what exactly is possible for this product and to gain an understanding of the current field of connected devices, a greater emphasis needed to be placed on electronic prototypingâ&#x20AC;?

Spark Core microcontroller.

Chapter 4 Methods

Key Tools This project was originally intended to be approached with a higher emphasis on user-centred product design, especially during the early stages of formulating what the best solution would be. What needed to be avoided, however, was this project being turned into a theoretical concept, with no grounding in what is physically possible. This meant the approach needed to be modified from what would have been ideal to what was possible to create now. When researching what is currently in the market, the realisation that the success of a product was almost an equal weighting between its user friendliness and applicability to the worker, and the functionality achieved by the electronics and integrated technology became apparent. To test and develop what exactly is possible for this product and to gain an understanding of the current field of connected devices, a greater emphasis needed to be placed on electronic prototyping than traditional product development. Beginning research into the practice of electronic prototyping revealed a number of simple but effective tools that greatly assisted the development of this project. A solid understanding of what function the device is performing even formed a base for future product development as is discussed in this chapter.

Project Canary

Methods

A Spark Core and air quality sensor. The Particle Build programming interface.

Particle IO “Particle IO” is a relatively new company founded in 2012 that aligns with the emerging category of the Internet of Things. (Particle IO, n.d.) Primarily they are a designer and manufacturer of WiFi enabled microcontrollers that facilitate rapid electronic prototyping, specifically for developing Internet of things based products. They also provide a cloudbased programming and hosting service for the devices purchased by customers.

Particle provides all this at a small per unit cost instead of the massive upfront cost potentially applicable to these companies.

In early 2015 Particle IO launched its third Kickstarter releasing the ‘spark electron’ the third micro-controller created by the company but this time with a new communication method. Instead of passing data over WiFi it will have an included sim card and communicate data via GSM. (Particle IO, n.d.)

The compatible software package is browser based, while slow, can be accessed from any platform.

Particle IO microcontrollers are essentially simplifying the processes of prototyping internet enable products. Aside from the innovation of the chips themselves, more recently Particle IO has created the option for developers to use their WiFi chips and hosting platform to scale the prototype into a batch or (low quantity) mass manufacture run. This means that an internet product start-up can launch a small run of their new device without incurring the cost of creating the cloud platform, programming or WiFi chip certification.

The Particle IO system has several advantages over its immediate competitors, of which there are few. Spark Core and photon have a very small PCB footprint compared to other internet enabled chips.

The same core and photon have Arduino compatible code and hardware. Particle IO boasts a very active, supportive and free community forum of other users familiar with the product and service. (Particle IO, n.d.) In this project, the Spark Core, and Spark Photon microcontrollers will be used as a platform for initial electronic prototyping and concept development. The ability to rapidly iterate and develop the design with the integrated internet is unparalleled in simplicity, only in price by other more complicated system.

Project Canary

Methods

IFTTT ‘recipe’ programming interface.

IFTTT A great example of a website/software based Internet of Things service, IFTTT (short for: if this, then that) provides the unique service of linking products and services to one another. (IFTTT, n.d.) There are currently 186 ‘channels’ that can be used as inputs or outputs that can be linked together. This is achieved by activating the channel, by signing into the information source, I.e. Twitter or Facebook, and creating an if this then that ‘recipe’ to link an action with a result. Using the aforementioned ‘channels’, a user could use IFTTT to copy any tweet from any user or hashtag (there type and amount of inputs differ per channel) and share or post it on Facebook. This may not be the most exciting example, but there are hundreds of incredibly useful recipes that streamline workflow, and link products outside of their internal ecosystems that were not previously compatible. Originally IFTTT linked purely digital Internet services, but new channels are frequently being added to the services, and it is now possible to add IFTTT integration to physical things as well, specifically Internet of Things products. Fitness

Methods

Project Canary

trackers can automatically log your performance to a Google drive spreadsheet, the Global Positioning system location of your internet enabled phone could detect you are nearly home and turn the lights on, message a loved one, or change the temperature via your Nest thermostat. The options are endless and very useful. IFTTT also has a Particle IO channel, meaning any number of the input channels could trigger a pre-programmed function on the microcontroller or the Spark core could alternatively trigger something to happen outside of the attached outputs. This is a previously unavailable and very exciting function that will add so much functionality to a prototype without the huge development time and cost previously applicable.

Project Canary

Methods

Freeboard.io start-up. Open viewing San Francisco roaming air- quality monitor.

Freeboard The Spark core micro-controller produced by Particle IO has a number of ways of connecting with the internet, some simple triggers, others the communication of data. One of the simplest is a ‘Spark Variable’ which is a variable piece of data, potentially manipulated by the program code, but originally originating from an analogue or digital input to the circuit. Freeboard is one of many browser-based data visualisation programs that interpret data produced by any source capable of transmitting the readable data.

the evaluation of concepts, considering a final product may use a similar, browser-based visualisation of user data. Built for open-source electronic projects, Fritzing guides a user through creating an electronic prototype and getting it manufacture ready. A user builds a graphical representation of the physical circuit they have designed and tested, inserting major parts like the Spark Core and Arduino, as well as smaller components from the built-in library. Once all the parts in place the user routes the cabling to connect all the components on the virtual prototyping breadboard. (Fritzing, n.d.)

As with IFTTT you can configure Free board data ’Panes’ to listen for and read information from the Spark Core variables, interpret and display that information in a visually pleasing window. The ‘Panes’ can have multiple inputs, meaning that some could display information from a Spark Core, others from sensors in a phone, or Google Maps data etc. In this project, Freeboard will be used to test the capability and accuracy of electronic prototypes as well as a system for

Project Canary

Methods

Circuit graphic and Fritzing generated circuit diagram. Fritzing printed circuit board layout interface.

Fritzing Built for open-source electronic projects, Fritzing guides a user through creating an electronic prototype and getting it manufacture ready. A user builds a graphical representation of the physical circuit they have designed and tested, inserting major parts like the Spark Core and Arduino, as well as smaller components from the built-in library. Once all the parts in place the user routes the cabling to connect all the components on the virtual prototyping breadboard. (Fritzing, n.d.) Other than the benefits of having a clear image for communicating the circuit to others, Fritzing is able to take the component layout and connection data the user created on the virtual breadboard, and convert information into a circuit diagram with automatically rounded connection lines. What makes the program even more useful for product scaling is Fritzing is then able to convert the circuit layout into a printed circuit board diagram for manufacturer. There is one similar program that has similar uses and benefits to Fritzing.123Dcircuits is an Autodesk browser based alternative (Autodesk, n.d.), that similar options to produce and convert diagrams for manufacturer. The one difference and positive of 123Dcircuits is the ability to add in code for the virtual circuit and run a simulation of the

Methods

Project Canary

desired function all in the browser. The biggest negative and what make Fritzing the best choice for initial circuit development is the lack of components in the built in library. It has the basics, but complex sensors and components are not present. Fritzing will be used in this project primarily as a communication tool, to seek help and begin manufacture discussions.

Initial Electronic Prototyping

Initial electronic prototyping aimed to achieve a requirement of the user based sensor, â&#x20AC;&#x153;Attempt to notify before a potential eventâ&#x20AC;?. Meaning the prototype should sense, diagnose and notify before the user is in any direct danger to be harmed. This prototype will focus on the sub-requirements of diagnosing harmful environments and preventing extended exposure. Using the Spark Core, multiple low cost, widely available sensors were tested for their compatibility and responsiveness in a circuit. Tests were also conducted to define the most efficient way of communicating information between two devices. Determining that it is possible to communicate and confirm specific information wirelessly, even on low fidelity prototyping tools.

Project Canary

Methods

Circuit diagrams for Spark Core 1 (left) and 2 (above) Actual circuit (right) and Freeboard output.

Functioning Prototype Previously, a heart rate sensor was used to initiate the monitoring of this prototype. To increase the reliability of the initial prototype the pulse sensor was replaced with a simple on/off switch, so as to free an input pin for a second carbon monoxide sensor. This will be used to check the data of the first sensor before it is published to the spark cloud. To attempt to simulate one worn product seeking clarification of a â&#x20AC;&#x2DC;threatâ&#x20AC;&#x2122; with a nearby device. Shown to the right is the freeboard readout of both sensors, the difference in outputs was due to a slight lag in the first sensor, not a false reading. To simulate the users location and movement, Freeboard is also reading accelerometer and Global Position System data from an iPhone. That could be tethered to the prototype to simulate a complete device. Finally, the monitoring device (second Spark Core) will take a new and more advanced approach at reading the published data, and in turn republish it backv to the Spark Cloud with a different value title so it will not be confused. Then a simplified data visualization will display the data.

Methods

Project Canary

This new visualization is created by modifying an existing and open-source HTML file and Javascript to display data with more meaning than Freeboard.

The new visualization has been modified to convert the raw analogue data published and confirmed by the two Spark Cores and display it by exposure level, not just a number. For example, a value of 430 that is read and confirmed by Spark Core 1 is converted and republished by Spark Core 2 and displayed as a “moderate reading” rather than the ‘430’ value that Freeboard would show.

This was achieved by changing the data type read by Spark Core 1 to one that would transfer using a different communication method from one read by Freeboard. Spark Core 2 is then responding this data published by Spark Core 1 and converting it back to the data type used to publish Spark Variables, which is then sent to the Javascript visualization.

Results This concept was able to perform as desired. It did however, take some time to refine the confirmation method between the two gas sensors and the translation of data types from one publishing method to another. The modified Hypertext Markup Language (HTML) file is successful in reading the data but for a currently unknown reason the data is incredibly varied and the visualization often freezes. While the data was published through the confirmation program, there were some accuracy issues, which did not align with data that was produced in earlier tests. This may be a circuit issue, or interference from the gas sensor positioned directly before the confirming sensor in the circuit. With these limitation becoming evident, it was necessary to explore other options in prototyping the function of the product. There was success however in the approach to data communication. The dashboard type approach was very effective at communicating a users threat level, specific to the sensors in use. The implementation of the second gauge, potentially representing the final interface of the product was also interesting. This gauge displayed averaged threat level, rather than specific threat information. Conforming to the previous idea of a distraction-free interface, that provides information with a low cognitive load, with the ability to call attention to itself if the need arises.

Project Canary

Methods

Proof of concept

Results from the initial electronic prototype were very beneficial in informing key aspects of the physical device development. This section takes place after the form and features of the device are confirmed. The final ‘Proof of Concept’ prototype seeks to simulate how the product and system could work using the prototyping tools listed, but with a greater functionality that previously attempted. Unfortunately, the advantage of the Particle IO system was also what caused issues in initial prototyping. The Spark cores were required to communicate to the ‘Particle Server’ overseas, this caused a long lag in communication between devices, but also occasionally prevented functionality all together. Before prototyping could continue the communication issues needed to be solved. There were a number of ways this could have been achieved, including migrating the prototyping to another form of microcontroller. To keep the prototype most in line with how the actual product would function the approach of having the devices and a local communications hub was chosen. This consisted of loading a local version of the Particle cloud onto a ‘Raspberry Pi II’ and configuring it to act as the server hosting the devices. Spark cores communicated with each other, via a wireless router and the local cloud, decreasing the response time, and greatly improving the systems reliability.

Methods

Project Canary

Live Feedback Time and cost constraints prevented the electronic prototyping from progressing past the use of separate boards for the microcontrollers and sensors. Instead, accuracy of interaction was the goal. Ideally at this stage of prototyping all the sensors and processing components would be mounted onto a single printed circuit board. However, the approach of a prototype board and attached sensors does replicate the interchangeable nature of the final product somewhat. Four main parts made up the final prototype. The Particle Cloud and router assembly, the Freeboard Dashboard, the main sensor device, and the slave device with low-fidelity user interface. Information detected on the main sensor device was interpreted and communicated to Freeboard and the slave device four times each second. Freeboard displaying all the information gave a good interpretation of the range, accuracy and latency of each sensor. The slave device also displayed live information from the sensors, but averaged to a simple bar chart, rather than raw numeric data.

Project Canary

Methods

Prototype Components The master Spark Core hosted five sensors. Air quality, temperature, light, sound, and gyroscopic orientation. More outputs were attempted but were limiting the stability of the device. To simulate interaction of working and not working, all sensors transmit when the switch on the slave Spark core is in each respective positions. Each sensor outputs its converted data to Freeboard, creating an overall dashboard interface.

The slave Spark Core has one output and an input, designed to simulate a final device it will be placed in a form prototype, with screen and switch mounted in final positions. As mentioned above the output switch controls the transmission of the master Spark Cores sensors. The attached LED bar graph simulates the gauge like final interface designed to call attention to over all safety level.

NO DECREASE IN LATENCY

Communication speed Even when running on the local Particle cloud, the upper limit of the spark core is four output messages per second. More frequent messages resulted in the microcontroller crashing and becoming unresponsive for a long period of time. This information was able to be sent and received on freeboard and the slave Spark Core with no decrease in update frequency up to untill the range extent of the local Particle Cloud server. To ensure that all information was still updated as fast as possible, a hierarchy of sensor information was established and communication points were distributed across a threesecond block. This could be customised to ensure that sensors most relevant to the situation or conditions the worker is in, will be monitored more frequently than others. The example shown to the left has the units location sending every three seconds, while air quality, temperature and light are checked three times in the same period.

Project Canary

Methods

Final Freeboard readouts.

Form prototype next to a lithiumion polymer battery and charging circuit.

Results While this prototype was overall very successful and was a great leap forward from previous iterations, there were still several issues. These did not affect the ability to test the interaction between devices, but prevented more function from being added to this assembly.

form mock up. With the local cloud and master Spark core assembly out of site, it did appear that all the components were operating within this mock up. This was most engaging when used with the Freeboard dash displayed on a mobile device.

Although its benefits outweighed the few problems, hosting the prototype on the local cloud prevented a number of outputs from being added. This is due to the limitation of communication over this network, not the microcontrollers themselves. Primarily it disrupted the implementation of an actual GPS output. in testing a tethered smartphone needed to be used rather than the actual board. The GPS required a separate microcontroller to transmit the information, which was then not possible to display on the Freeboard interface. For this to be possible the Freeboard input needed to display a map interface, which required an internet connection, defeating the purpose of the internet free assembly. Creating the wireless â&#x20AC;&#x2DC;slave deviceâ&#x20AC;&#x2122; was very useful in testing how this prototype functioned. To do so a simple lithium-ion polymer battery and charging circuit were added to a basic

Project Canary

Methods

Future Development Progressing functionality of the electronic side to this project could have been an entire years work in itself. However, I believe that enough was done to ground the subsequent product design in reality, and inform the creation of a system relevant to what is actually possible. Given more time and resources, it would have been useful to break away from Internet of things prototyping tools and the limitations discovered in the development of this project. Further iterations with more sensors, more effective connectivity and processing capability would be the obvious progression of this project.

Methods

Project Canary

Chapter 5 User Experience

System Basis

System Basis Developed alongside the physical product, and refined to suit the function of the final electronic proof of concept, the underlying system proposal intended to mesh all aspects of the project together providing a coherent concept. Many aspects of the product and system are flexible. Making the product applicable to the widest audience, but equally effective to each use case when customised upon implementation. The following chapter will explain how the product could function in its ideal conditions. That is, in a large established workforce, where all users are equipt with the device, and all components of the product are used. This system proposal would have slight variations depending on the final use, and configuration of the product. In some cases, many of the advanced functionality may not be possible due to the nature of that use case. A single isolated user, for example, while still benefiting from the advanced monitoring built into the device, would lack the information sharing functionality. System Basis

Many aspects of the product and system are flexible. Making the product applicable to the widest audience, but equally effective to each use case when customised upon implementation.

Chapter 5 User Experience

System Basis

System Components

The majority of research and development supporting the decisions made in creating this system were developed during electronic prototyping and experimentation. As mentioned, the scenarios and application described in this chapter would be considered an ideal implementation. It would have differences depending on the final intended use, and workplace. For the purpose of progressing this project towards a final outcome, the decision to develop for one general application needed to be made. To have such a large possibility of final products, the Canary system would require an innovative way of implementing the products into a workplace. To prevent compatibility issues, or lengthy training of a new tool as part of a growing implementation of connected products in the work place, the products would be implemented alongside an expansive software solution. The software package would not only control the settings and function of the monitoring devices, but integrate personal, task and safety awareness into a single solution.

System Basis

Project Canary

Upon implementation, certain parts of both the personal monitor and environment device (further description 100137pp) could be customised to better monitor users, and the common safety issues associated with that workforce. Critical environment and location sensors will remain, but components like higher sensitivity gas or air quality sensors could be interchanged. In most applications, the system would require three main components. The sensor equipt, personal monitoring device, the communication hub and software application installed on a smartphone or tablet. As with the internal components, these products may not be necessary for every application, but restrictions were made to keep it simple to understand.

Software Application The software solution is critical in creating a streamlined user experience. By taking over management, notifications and device settings, the user interface and interaction points on the remaining designed products can remain simple. The application will not always need to be used in day to day use of the system, only when calibrating device settings or changing locations. In a group environment, multiple devices can be used but are not needed for ideal function.

Communication Hub When a task or location is accepted on the software application, device settings are automatically calibrated to respond to risks identified when setting up the task. These changes are sent via the environment device to all user monitors tethered to it.

User Monitor Finally, the user monitor will interface with all other parts of the system, including other devices connected to the same information hub. Creating highly monitored areas of the workplace users can pass through.

If there are multiple environment devices in a workplace, users moving through the workplace would have their devices seamlessly update to specific area settings depending on what hub they are tethered to.

Project Canary

System Basis

Typical Scenario The opposite page provides a brief description of three typical scenarios, not specific to a trade or industry. Insights were acquired through inital user interviewing early in this project. Most trade operations will fall into the third category of use shown here. Work taking place in a group, safety operations being followed and existing safety solutions set up to protect users or check hazardous environments. These procedures are documented before work can begin. However remove initial monitoring and physical/engineered safety solutions, which would often happen in mobile or short-term work site, and users safety begins to decrease. The issue in group work of safety being a hinderance to productivity was also noticed, often in areas where time to completion of a job is more important that the quality of finish or following of procedures. If there was to be an accident, luckily the user is still in a group environment, and a response would not be too far away. A users safety can very quickly be minimised when they are working alone. While the risks of social influences reducing safety are removed, the risk of an accident going unnoticed is increased massively.

System Basis

Project Canary

Single user

Group of users

Existing solutions

personally check environment or equipment

conduct environment or equipment safety procedures

document procedures

conduct check of environment using existing device

begin task

move workplace or change task

check in?

begin task

document procedures

begin task move workplace or change task re-conduct safety procedures

potential accident or injury

move workplace or change task

reconduct safety procedures

alarm wait for a response from a passerby or colleague

alarm or immediate response

potential accident or injury is ideally prevented

Integration into a Workplace The canary system could ideally be implemented into a workplace of any size and be relevant to a large number of trade opperations. Upon implementation, a company would order a monitoring device per worker, or a set for however many people will be working at a time. An environment device per work group or location. And subscribe to the software application that will be used to operate the devices, and coordinate task management and worker productivity. While also providing individual workers with sites into their safety during work. The personal monitoring device has a number of sensors built in that would be standard to every device. So that basic functionality would be preserved, these include GPS, Gyroscopic and accelerometer positioning sensors, and temperature, sound and light exposure sensors. In this iteration of the product, there is one sensor that can be interchanged to make it more relevant to each workplace. In future versions ideally several different sensors could be added.

System Basis

Project Canary

one per work place is the minimum necessary

one per work group or location

one per worker

device fixtures are offered as add ons

sound and temperature sensors are included in every device

customisable air-quality/dust/ gaseous sensors

Location and positioning sensors are included in every device

device range and communication methods could potentially be customised

customisable visual or light sensor

Ideal Scenario Thankfully, accidents and safety issues do not happen in every workplace, every day. So that the device would not become a distraction or hindrance during the operation of other tasks, the basic operation of the product needed to be kept as simple as possible. Using the software application to control the settings and function of the device meant that physical controls could be kept simple, with the final device only requiring three interaction points. Work begins with the task being created or accepted from a previous list on the software application. Preset conditions, operations and locations for the task are confirmed, followed by a digital version of the companies already existing risk assessment documentation. The application then sends this information to a specific environment device if there are multiple in a workplace, or the device paired to the application. This device then interprets the information to determine the best settings ans sensor frequency depending on the conditions. This will achieve the best coverage in an environment, but also

System Basis

Project Canary

preserve battery life for less strenuous applications. The workers devices can then be removed from charge, turning the device on. After loading the task settings the device can be switched to ‘Working’ Initiating the sensors. This action has been put in place to ensure that the user is comfortable with their privacy, and is aware that they are only being monitored when working. This will be a key requirement for the system to function. and the worker must conform to this operation to be aloud onto a site. During operation a current and cumulative level of risk or exposure to the environment around them is shown on the user interface. Further information about the devices interface can be found on page 122. To finish a task and cease monitoring the device is switched back to ‘not working’. at the completion of a day, the worker can view exposure and minor safty risks that were encountered during the day, ideally learning about their operation and how to conduct safer work practices in the future.

Set up and allocate task. Complete safety documentation and task specific settings.

Switch into ‘Working’ mode to initiate monitoring and productivity documentation.

Live and cumulative exposure information is displayed on the gauge interface.

Switch out of ‘Working’ mode to complete task and cease monitoring.

Continue to subsequent tasks, and review previous task information.

Emergency use Considering the devices response to a potential threat in an environment was more crucial to the operation of the device than other aspects. However, the same simple, minimal touch point approach was taken as the day to day interaction. Different levels of emergency notification and response were required in the product. The response to environment or exposure risks, response to immobilisation injuries and response to personal alarms from other users. As a user begins to reach dangerous levels of exposure to any aspect of their environment the device will attempt to notify that user, and create the awareness of this risk. Other users tethered to the same communication hub will receive subsequent warnings. Once responded to, on the Sofware application work could continue or stop depending on the severity of the risk. In the event of a user becoming unresponsive or immobile, the device will seek out and contact the closest another user before seeking external help. This warning will depend on the position and placement of the device on the user,

System Basis

Project Canary

and will not alarm if the device has been removed from its fixture. To respond to a warning or notification from another user, the worn product will call attention to itself displaying basic information on the gauge display. If more attention is required the software application will launch and display location and threat information from the other user. But as the environment device only hosts users in a single work area, the user in concern should not be too far the notified person. This method is entirely conceptual and could not be tested in a real environment, so refinements would need to be made in a final product and software being implemented in a workplace.

If a potentially dangerous event is detected, visual and auditory warnings are produced by the worn device.

Before notifying others the information is checked then shared with nearby devices

Pre-programmed response mechanism determines how threats are responded to.

Tablet Software Solution The Canary software solution has been designed for implementation as a responsive mobile application. With different applications and tools specific to the tablet and mobile versions. The tablet application will act as the main interaction point for the system. It is required to configure each device before an operation and to review information after the completion of a task. To ensure that not only the application is used, but the monitoring products themselves, the Canary application includes other productivity and safety functionality. The application should then be all a company or workgroup needs to begin operation. Each may have slightly different functionality depending on the level it is operating at. For example, a single user may not require any form of group-based task management. Larger companies will also have different levels of the application, with some being able to create and accept new tasks, and others with only the permission to view and edit task information.

System Basis

Project Canary

The software application will, when monitoring a work site or paired with an environment device, be able to see each device in it. Readouts of exposure risks in each area will become much clearer this way. Similar to the Freeboard dashboard present in the electronic prototype. This is also important if in the event of an accident or exposure risk, users can easily be made aware of where to go or who to help.

AIR QUALITY WARNING

LOCAL HOST 8

3 USERS CLOSE

NOTIFY ALL

AIR QUALITY WARNING

3:17

LOCAL HOST 8 LOCAL AIR QUALITY

3 USERS CLOSE

NOTIFY ALL

Mobile Software Solution The mobile application will function much the same way as the tablet solution, and in the case of single workers, will have the ability to set and modify device settings as the tablet system can. Most likely the mobile application will have less permission to edit tasks or change settings of the worn devices. It is primarily in place as a communication tool. Notifications will arrive through the mobile application at the same time as the worn device. The mobile device will also provide users with detailed information for review regarding their safety level or exposure to potentially harmful environments.

Project Canary

System Basis

101

The Canary application includes other productivity and safety functionality. The application should then be all a company or workgroup needs to begin operation

102

System Basis

Project Canary

System Basis

103

Conclusion

The creation of an underlying system is critical for a product to succeed at this scale. It becomes more important when the systems function will actually affect peoples safety. The information described in this chapter could be considered an introduction into the framework for a successful Canary system design. As with the electronic prototype, the design of the software and functionality of this production to take into account every eventuality, would be a massive project of its own. Understanding the functionality of the system, software and product interaction is important for many features of the design to be understood. However so that all aspects of the project could be considered and a complete concept could be created the design of the physical products became a greater focus.

Project Canary

System Basis

105

Chapter 6 Product Intervention

Canary Monitoring

It has been a great challenge to design an electronic product for a trade workplace that has very specific use. While keeping it broadly relevant to the large number of applications that it could potentially fill.

107

Chapter 6 Product Intervention

109

Design Introduction It has been a great challenge to design an electronic product for a trade workplace that has very specific use. While keeping it broadly relevant to the large number of applications that it could potentially fill. Using the format and approximate size of the current size of electronic assemblies as a base, the product was designed to join the necessary placement of certain elements in a simple but pleasing form. The user interface has been placed high on the device, and angled out so it is easy to see in a number of placements. While sensor input areas are kept below and away from potential obstruction. It was also necessary for the designed products to keep a low profile to prevent obstructing a user during work. The basic shapes and curved surfaces provide enough of a ruggedised finish for a product that is attached to users or equipment. Without going as far as ruggedised power tools. In combining these aspects, a visual language unique to the safety product field was established. When it became necessary to design a second device, which became evident through prior mentioned electronic prototyping, it was less of a challenge to migrate the visual elements into a larger device with different elements and functions

110

Product Intervention

Project Canary

Personal Device The personal monitoring device is a result of numerous iterations beginning after the completion of the first electronic prototype. Shown in the foreground, it is designed to contain the sensors and communication components necessary for the system to function.

processing and long range communication is processed. This not only provides more accurate information for the users and supervisors, but allows the product to be a lot smaller than existing devices with multiple sensors.

The device is intended to be attached to the user, or their equipment, but will still function if placed in their surroundings. As previously mentioned, as the settings and customization of the device are primarily covered in the software application the user interaction points of the device are low in number and simple to use. This was an important factor that was considered from the beginning of the product development. The device will monitor without supervision, and interactions are kept to a minimum so not to distract from the potentially dangerous environment around the user, or the task at hand. The device is intended to be used by each and every user in a workplace so the best visualisation of space can be created. With information being shared to check and confirm readings from each device. This product will interface with local communication hubs, where some of the devices

Project Canary

Product Intervention

113

Function The devices would be stored on site, or in mobile storage cases. These packages would include charging solutions so devices are always available. The device activates when removed from the charging station, most likely at the beginning of a work day or task.

As well as the primary user interface each side of the product has a large power notification light. Being lower on the product it has less chance of being obscured. It would only be used to provide feedback to a user, or draw attention to critical information on the device.

To ensure accurate use information is being sent to the right paired user application profile. The devices share information only with the application, and logged in user on the wirelessly paired smartphone application.

The internal sensors are distributed throughout the enclosure. with inputs for sound or air quality, and light based sensors being present in the base of the device. An area that is less likely to be obscured by loose clothing.

As previously mentioned the main switch on the front is the only interaction needed in day to day operation. Controlling the operation of the sensors is given to the user so they are comfortable that their privacy is secure when not working, but are safe when working. An issue continually brought up in user research. In a workplace, this same switch could be used to log productivity, or time worked by visiting contractors.

The side sensor panel also incorporates two notification buttons that are used to interact with notifications on the device. single presses will be used to interact with the user interface, and intently pressing and holding both buttons acts as a call for help or panic button.

If the user forgets to engage the sensors, and devices in the same location are online, short auditory notifications are sent at regular for a few minutes every 30 minutes.

114

Product Intervention

Project Canary

Form The basic form of the personal product is designed around a simple profile for ease of mounting on the rear of the device and docking vertically. So it is easy to view in a number of positions the user interface protrudes from that profile finishing at an angle. To provide a natural gripping surface, and a guide to interfacing buttons the profile is cut back allowing these components to be added in a place that will not be bumped or accidentally activated.

The main casings are created from high impact plastics with a rubberised spray applied to all surfaces, creating a subtle ruggedized feel than bare plastic. Unless seperatly fixed, the transparent sections, including the user interface and ambient light sensor are co moulded with the main plastic body. Contrasting graphics are added after all other processes.

The rear surface includes a raised panel that then recesses back to locate the induction charging and mechanical fixture point. Both these surfaces needed to be located easily and without visual aid. The high visibility mixture of red and orange was chosen for its differentiation from both existing safety products and power tools. The colour is not as off-putting as other highvisibility standard colours, but is still easily recognisable in the workplace. The casing would have the option in higher volume orders of custom finishes, to better align with the application or uniform of that workforce.

Project Canary

Product Intervention

117

Design for Use Creating a product intended for heavy use in a potentially damaging environment has been a challenge. Many aspects would need further input from material experts to ensure such a simple form could still perform as needed in a field where overly ruggedised objects are expected. The external body was created with the minimum amount of parts to archive the designed shape and function requirements This was important as all openings part lines and sensor inputs had to have some element of water and dust resistance added. Rubber gaskets are moulded to fit each parting surface. Sensor inputs would require special materials depending on the sensor being used. Damaging elements cannot be let into the product, but the information being monitored cannot be misread by an overly efficient filtering mesh.

118

Product Intervention

Project Canary

User Interface Throughout the development of this project, the question of the necessity of a visual interface kept arising. While there are benefits by not including the display, including the very attractive proposition of a smaller product. The addition of the screen definitely makes basic interaction with the product easier. Protecting the screen behind these several layers of plastic work towards the subtle integration of ruggedness in this product. The transparent sections on each side panel function as subtle product status and notification lights, as well warning lights to draw attention to the device or user in an environment.

Project Canary

Product Intervention

121

Interface Example As a result of the electronic research, the use of a averaged gauge to show a users current exposure risk or threat level is to be used. This display should not always require attention, so the use of the low fidelity display works well for its application. As the information only needed to be displayed as a graph, the LED screen is mounted behind a transparent hole pattern in the external casing. Graphics has been added to communicate the meaning of the interface sections. The exposure risk or threat level is displayed using on or off â&#x20AC;&#x2DC;dotsâ&#x20AC;&#x2122; formed by the holes in the casing. Representing a users situation with lights and colour should require less attention thatn text and numbers, especially when quickly glancing at the display while performing other tasks. The signal strength to the environment communications hub is also displayed along with the devices battery life. Some experimentation into other forms of communicating using text or symbols on this display were explored, but were not as effective as the approach presented here.

122

Product Intervention

Project Canary

Shown to the right is an example of the progression through stages of notification on the device. The top shows a typical environment, this could quickly spike to the second image, responding to rapid change in an environment. This may be as simple as power tools turning on, or the change in air quality. The third image shows what would be displayed if the potential threat or exposure hazard does not subside or increases to a level that could harm the user. If the level rises and remains for some time the user is notified of the change. This would be present on the device and as a silent notification on the mobile application. Notifications can be acknowledged and silenced by tapping a button on the side of the device.

---

Fixtures and Charging To make the product applicable to the largest amount of users, a unique mounting system needed to be created. The fixture consists of a cylindrical locking mechanism that is spring loaded into the locked position. To fix to the product the user pushes on the metal mounting plate on the rear of the device, moving the locking pins into the device. When attached the device can be freely rotated, preventing the device from restricting movement. The device is removed by pressing the locking pins together. The locking assembly is designed to be attached to a number of fixture options while retaining the same familiar locking functionality. These may include simple belt loops, or permanent fixtures for bags or equipment. The option of charging the product using an induction coil was the most appropriate for this product. The addition of a port for charging did not seem ideal on something that required constant protection from the elements. The charging point attaches to the device magnetically, and can be used while fixed to equipment if needed. This situation is not ideal, the device will be charged most often in docking solutions, which will also include the same contact point.

Project Canary

Product Intervention

125

The device shown is reacting to an emergency call by the user.

To increase the functionality of worn devices, a supporting communications hub was required.

127

Environment Device To ensure the size of the personal monitoring device remains compact, many functions critical to the operation of the system were incorporated into a second product designed to be mounted in the work site among the users. This worked well in creating the proposal for an information sharing system, as information can be passed amongst users tethered to the local hub, rather than separately to every other device in the work place. Much like how the function of the Spark Cores improved when operating off the local cloud, rather than the communicating over the internet. The personal devices will communicate with the environment hub using short-range wireless communication. With the environment device providing the ability for that device to communicate externally to the worksite using longer range methods such as cellular networks.

Project Canary

Product Intervention

129

Design for Placement Following the same development as the personal device, the environment device is designed to be capable in a trade environment. Utilising the same rubber sealing approach as previously used. The environment device will house fewer components than the personal monitor, but they are larger in size. Primarily components to process and interpret the information from all personal devices connected to the hub. Secondly communications components, for receiving information from multiple connected devices, and to communicate information externally if the need arises. This device has been designed around the size of two parts that already have the ability to perform these tasks, just to a lower standard and reliability of the components necessary for a successful final product. The user interface is again present in the form of an LED screen, mounted behind the hole pattern informed from the design of the personal device.

130

Product Intervention

Project Canary

Fixtures Even more important than in the personal monitor is the need for a versatile mounting solution. The device, while always being â&#x20AC;&#x2DC;attachedâ&#x20AC;&#x2122; to something has several mounting options. This is not only for mobile workers, but for work sites that may rapidly need to expand the range, or when the group of workers shift to another area. Two fixture points have been designed into the rear side of the device. The first a simple loop allowing the fast attachment to objects or the environment with the use of a caribena or zip-tie. Second is a mechanical fixture mounted above the channel pictured. It uses a set of metal parts with cuts strategically placed to create flex over mounting components. A set of locking faces will secure the device on the mounting hardware. This solution opens up the option for the device to be mounted in a number of locations, using a mounting bracket as pictured, or even the strap and buckle approach also shown. The latter would allow the device to be frequently moved and placed at a set of pre determined points.

Project Canary

Product Intervention

133

Environment device visual interface displaying the wireless signal output.

Environment Device active display area.

User interface The environment device utilises the same hole pattern covered interface featured in the personal device, but on a much larger scale. The increase in size makes displaying different types of information possible, even simple symbols and text.

In the event that a user does interact with the device, the display has basic navigation and setting adjustment functions through the side mounted buttons. Users can scroll through basic information screens, enter and modify signal strength or connection settings.

All information and settings of the environment device are adjustable through the software application. However, the physical version is still necessary to display live information in use, when the a mobile is not available or convenient to use. The physical display will also be used to identify product groupings to confirm your personal device is paired to the correct hub.

The above graphics represent three of these such screens. An identifying number that will relate to mapping information. This identifies that environment device as the ninth in this work site. Centered is a settings screen showing the adjustable signal strength output of the device. Finally a simple representation of the personal devices connected, and the gauge information being displayed on their device.

The display is easier to understand when viewed from a distance, at which point the display â&#x20AC;&#x2DC;pixelsâ&#x20AC;&#x2122; form the correct shapes. This, in fact, works towards the idea that the device will most likely be viewed from afar, as up close interaction will be rare. Project Canary

Product Intervention

137

Product Conclusion

So much of the design for these products were based on prior experimentation and research findings. Including the limitations of what system elements were needed and the feasibility of what components were included in them. This meant that the products were designed for a single application, not the vast amount of applications and workplaces as was originally intended. These products functioning as described may suit the existing work practices of only a few industries. At this point, if design development was to continue, the project should be assessed to see if an expensive solution is still possible, or if design should continue for the narrower user group. With a greater focus on the user now they are more clearly defined.

Project Canary

Product Intervention

139

Chapter 7

Evaluation

Chapter 7

143

Project Focus Evolution

Trade work IOT product - prevent accidents - speed up response times to accidents - prevent false alarms - applicable to the widest audience possible

Connecting Products - focus shifted to designing a solution that is possible - using connected micro controllers and internet of things prototyping tools

Accident Prevention - monitoring every aspect of a workers environment - monitor biometric data of the user - combining all input information with information about the workplace or task - a product solution will process all information gathered and determine risks and aim to prevent accidents relating to the environment or a users own work practices

Exposure Risks - redefining the ability for this product to prevent accidents, but instead to prevent exposure to dangerous environments - incorporating sensors relevant to a users environment to monitor changes, risks and exposure over time

Information Sharing - development into how multiple low-cost devices could monitor as effectively or better than specialised solutions

System Design - creating the framework for a system that would operate a product solution of the electronic research - development of a software application

Safety Awareness - consideration into how the information used to prevent accidents could be used when not in an emergency context

Product design - creating a physical product representation of the device - incorporating knowledge and device function determined in research stages

145

Improvements could still be made in every aspect of this prototype, it is a vast leap forward from previous iterations and is successful in communicating the concepts core function

146

Evaluation

Project Canary

Electronic Function The iterative development, programming and problem solving regarding the Spark core based prototypes has taken an enormous portion of the development of this project. Time that was originally intended to be spent approaching the project as a product design exercise, rather than the heavy system function with product components entering development after the electronics were completed. However the influence the development have had on the project has been positive. Key findings that aided the project were not denied by taking an unplanned approach. Both the negative and positive aspects of the electronic prototypes have informed the project development, and grounded the final concept as something that is actually possible. The proof of concept device, while still hosted on Spark core microcontrollers, is a fairly elaborate device, with multiple communication flows as described on page 77. While improvements could still be made in every aspect of this prototype, it is a vast leap forward from previous iterations and is successful in communicating the concepts core function, and the basic interaction of the designed products.

Project Canary

Evaluation

147

Product Design Creating a physical representation of what a designed solution would look and function like was a critical part of this project. It aids in communicating the concept, and also as a tool to review how viable a physical solution would be. At this point in time, with what technology is available, a custom designed product was necessary to perform all the required tasks. A more capable software application as the entire solution was considered. It was not capable of including more specialised sensors, and for that reason was a limiting platform. I believe that the product created would function well in a work environment. It has been designed to be versatile in how it attaches and interacts with users, so workers do not have to change practices to operate it. The visual language may not be exactly aligned with what is traditionally associated with safety or work products, but this sets it apart in a work site making it easy to recognise when information is needed. In shedding the ruggedized look and features, some durability would indefinitely be lost, but I believe that the product has been created to a suitable level. The reason being that it is intended to be mounted on a user, or encased

148

Evaluation

Project Canary

in a charging station, the device would not be handled or used with the same level of force as work tools. Some user testing was performed throughout the development of this project, which informed several small aspects of the interaction and design. Unfortunately, the electronic prototype and final functional models were produced slightly too late for testing to have an effect on the development of the project. The design for a work environment would be a dominant area of focus if the development of this product would continue. Creating a casing that is properly able to withstand the elements, and the tasks undertaken in an environment.

User Evaluation Final external feedback of the product concept as a whole was sought from two parties. One with a long career in the power industry, who has worked in isolation and in groups but has also been involved in the implementation of new technology projected into the existing workflow. The second was from an experienced paramedic. This feedback was sought after to see how a the final product, which is more specific for trade or construction work at this point could be seen as useful to other workers. Key feedback points; Having an external party able to monitor GPS location while on operations is a useful feature, that when bundled with the other monitoring features could be easier to accept. Travel was a key point from both users, pointing out that fatigue and the nature of working in remote locations are seriously threatening.

Monitoring several aspects of an environment at once, and having sensors specific to the workplace is the most innovative feature. Products are already used, but only have one application. Having one do it all product is very appealing to large companies. The device attaches well to belts or bags, which is important considering the amount of equipment already used. More consideration may be necessary with the strength of the attachment method. The simple display and button layout is appealing to users not familiar with technology products, but it is also very important as tools should not take a users attention away from their environment.

Integrating the master ‘working’ and ‘not working’ function to operate the GPS and other sensors is interesting, and a good response to privacy issues that would be the first roadblock in implementing this device. However, it may need more consideration how applicable it is to every workplace and user.

Project Canary

Evaluation

151

Chapter 8

Conclusion

155

Chapter 8

157

Project Possibility Many aspects of this projects development, while somewhat successful, were not completed to a stage that could be implemented into a workplace. Considering the positive user feedback on the main purpose and interaction points of the device I believe that there is a real market need for this device. It was an early realisation in this project for it to become possible, development and implementation of a final product would need extensive backing from a large company or organisation. If development was to continue, the project in its current state is enough to communicate its function and potential to improve a workers user experience with safety. The product could be pitched to large construction companies, unions or organisations like WorkSafe Victoria and Safework Australia. Backing and support from these types of companies would accelerate the development of this project far beyond what I have been able to achieve

Project Canary

Conclusion

159

Adoption by users The biggest challenge faced with the adoption of this product, even with the support of the organisations listed on the previous page, is the adoption and use by workers. This issue is one that has been obvious from the beginning of this project. The creation of the underlying system design and software application was intended to ensure use by all users. Incorporated into the software is the ability to schedule and plan tasks, monitoring a users safety and time in the work site as well as being able to prepare and manage safety documentation required for each job. The system aims to also be a turn-key solution for companies seeking to digitise and enhance their workflow, and bring it up to date in one large stride. Finally to ensure use by all workers, the device could also become a necessary product for entrance onto a work site. As physical solutions such as hard hats are required today. However to ensure a users confidence in the privacy in the device when not in use, the physical ‘working’ and ‘not working’ feature was well received. Users are firmly aware

160

Conclusion

Project Canary

then that they are being monitored for safety when on the companies time, but would never have their privacy breached when on a break or at home. This eventuality may be more necessary in some organisations than others.

Personal Reflection As mentioned the original intended approach to this project was not able to eventuate, instead the main focus of the project was on the electronic function and feasibility. A large amount of the functions and features were influenced by the system and electronic prototyping, the product design elements filled in the gaps to make it something visual and pleasing to use. I may have been somewhat ignorant in approaching the development of an Internet of Things product, as a normal user experience and design exercise. Considering that before this project I had had very little to no exposure to the development of an electronic product, I am extremely pleased with the development so far. However, if I was to have the time again I would definitely reconsider my ability to undertake this project, without a deeper understanding and knowledge of complex connected devices and electronic prototyping.

It would have also been incredibly beneficial for project to have been more defined, and less broad initially. This would have assisted decision making, and produced the correct solutions and prototypes sooner. Instead, avenues were explored that were not used in the final approach, and the only knowledge gained was how not to achieve this product. Negative points aside, this project while still conceptual, has been successful in identifying a product that could be used in a workplace. Solutions that add connectivity, sensor monitoring and information sharing like existing internet of Things products could very soon be used to assist the practices and safety of workers. So more attention can be given to the job underway.

Had this been the case I believe that the solution I would have produced, while there may not be any differences, would be a lot more responsive and capable than the Spark Prototyping used in this project.

Project Canary

Conclusion

163

Appendix

References

(12)United States Patent. (2013, July 28). (12)United States Patent ABS, A. B. O. S. (2014). 6324.0 Work-Related Injuries, Australia (JUL 2013 TO JUN 2014) (pp. 1–48). Australian Bureau of Statistics. Autodesk. (n.d.). 123d Circuits. Retrieved from https://123d. circuits.io Blackline Safety. (n.d.). Blackline GPS Loner Bridge. Retrieved May 14, 2015, from Blackline Safety. (n.d.). Blackline GPS Loner SMD. Retrieved May 14, 2015, from http://www. blacklinesafety.com/ solutions/loner-smd/ De Chesnay, M. (2014). Nursing Research Using Ethnography : Qualitative Designs and Methods in Nursing. New York: Springer Publishing Company. Fritzing. (n.d.). Fritzing. Retrieved from http://fritzing. org/ learning/ Grace Industries. (n.d.). Super Pass II. Retrieved June 11, 2015, from http://www.graceindustries.com/ documents/ literature/SuperPass%20II%208.5x%20 11%2009.pdf ideomethodcards. (2007). ideomethodcards, 1–110. IFTTT. (n.d.). IFTTT.

MSA. (n.d.). Altair 5x simulator. Retrieved June 9, 2015, from http://webapps.msanet.com/altair5xsimulator/ default.aspx MSA. (n.d.). ALTAIR® 5X Multigas Detector. Retrieved June 9, 2015, from http://au.msasafety.com/Portable- GasDetection/Multi-Gas/ALTAIR%26reg%3B-5X- MultigasDetector/p/000080001600001023

166

Appendix

Project Canary

Particle IO. (n.d.). Particle Community. Retrieved from https://community.particle.io Particle IO. (n.d.). Particle IO “Shield Shield.” Retrieved June 11, 2015, from http://docs.particle.io/core/ shields/ Particle IO. (n.d.). Spark Core Documentation. Retrieved June 11, 2015, from http://docs.particle.io/core/ Particle IO. (n.d.). Spark Electron Kickstarter. Retrieved June 11, 2015, from https://www.kickstarter.com/ projects/ sparkdevices/spark-electron-cellular-dev-kit- with-a-simpledata Siroker, D., & Koomen, P. (2013). A/B Testing : The Most Powerful Way to Turn Clicks Into Customers. Hoboken: Wiley. Tan, Z., Chu, D., & Zhong, L. (2014). Vision: cloud and crowd assistance for GPS urban canyons (pp. 23–27). Presented at the MCS ‘14: Proceedings of the fifth international workshop on Mobile cloud computing & services, New York, New York, USA: ACM Request Permissions. http://doi. org/10.1145/2609908.2609950 Teizer, J., Allread, B. S., Fullerton, C. E., & Hinze, J. (2010). Autonomous pro-active real-time construction worker and equipment operator proximity safety alert system. Building Information Modeling and Collaborative Working Environments, 19(5), 630–640. Trend Watching. (2014). Internet of caring things, 1–14. Ulllted States Patent [19]. (2013, July 29). Ulllted States Patent [19]. Walther, J. B. (2011). Introduction to Privacy Online. In Privacy Online (pp. 3–8). Berlin, Heidelberg: Springer Berlin Heidelberg. http://doi.org/10.1007/978-3-642- 21521-6_1

GitHub,. ‘Spark/Particle-Cli’. N.p., 2013. Web. 28 Oct. 2015. In order to create the Raspberry Pi local cloud to host Spark Core micro controllers, the Particle-cli Github repository must be used. It was first published by Particle/Spark and has 26 contributors. It can be found at the following website. https://github.com/spark/particle-cli

Seeedstudio.com,. ‘Grove System - Wiki’. N.p., 2015. Web. 28 Oct. 2015. The proof of concept electronic prototype was created using components from the ‘Grove system’ created by Seeedstudio. To use the sensors on Spark Core code elements of each sensor library were used. Directions and full libraries for each sensor can be found at the following websites. http://www.seeedstudio.com/wiki/Grove_-_Air_Quality_ Sensor http://www.seeedstudio.com/wiki/Grove_-_Light_Sensor http://www.seeedstudio.com/wiki/Grove_-_Temperature_ and_Humidity_Sensor http://www.seeedstudio.com/wiki/Grove_-_3-Axis_Digital_ Gyro http://www.seeedstudio.com/wiki/Grove_-_GPS

Project Canary

Appendix

167

Glossary of Terms LED

Light Emitting Diode.

GPS

Global Positioning System.

Spark Core Spark Cloud

Cloud based program hosting for Spark Core.

Spark.variable

Program code function used to publish data to the internet.

Spark.publish

Program code function used to publish data to other devices.

IoT HTML Javascript

168

WiFi capable micro-controller.

Internet of Things. HyperText Markup Language. The programming language used in HTML.

Appendix

Project Canary

Program Code A critical fault was found late in the development of the final electronic prototype and was corrected for reliability of the device. No change was made to the master Spark Core assembly. The slave Spark Core was modified to include a three axis accelerometer. The programming and functionality of the master Spark Core remained as is printed in this book. The slave Spark Core had its functionality and programming adjusted so it no longer triggered all the sensors on the master assembly to communicate to freeboard, nor did the averaged information display on the slave devices LED bar graph. These functions were possible but as the devices were hosted on the local cloud the devices could not communicate effectively without one or both crashing. To amend this fault the slave device conducted the averaging programming internal to its assembly while also publishing the information to freeboard No information was pulled down to this device. The accelerometers â&#x20AC;&#x2DC;Yâ&#x20AC;&#x2122; axis was used to display an averaged level on the display depending on the severity of moment. It updated four times each second.

Project Canary

Appendix

169

z x

Program Code Slave Spark Core // Cabling for i2c using Sparkfun breakout with a Spark Core // Spark Core <-> Breakout board

pinMode(ledPins[thisLed], OUTPUT); }

// Gnd

- GND

// 3.3v

- VCC

Serial.begin(57600);

// 3.3v

- CS

Serial.println(“”);

// Digital 0 - SDA

accel.powerOn();

// Digital 1 - SCL gains[0] = 0.00376390; // This #include statement was automatically added by the Particle IDE.

gains[1] = 0.00376009;

#include “adxl345/adxl345.h”

gains[2] = 0.00349265;

int x, y, z, i;

accel.setAxisGains(gains);

double xyz[3], gains[3], gains_orig[3]; //set activity/ inactivity thresholds (0-255) ADXL345 accel;

accel.setActivityThreshold(75); //62.5mg per increment accel.setInactivityThreshold(75); //62.5mg per increment

int ledPins[] = {

accel.setTimeInactivity(10); // how many seconds of no activity is inactive?

// 2, 3, 4, 5, 6, 7, A7, A6, A5, A4 A7, A6, A5, A4, 7, 6, 5, 4, 3, 2

//look of activity movement on this axes - 1 == on; 0 == off

};

accel.setActivityX(1); accel.setActivityY(1);

void setup(void) {

accel.setActivityZ(1);

for (int thisLed = 0; thisLed < 10; thisLed++) {

170

Appendix

//look of inactivity movement on this axes - 1 == on; 0 == off

Project Canary

accel.setInactivityX(1);

// Output x,y,z values

accel.setInactivityY(1);

Serial.print(“values of X , Y , Z: “);

accel.setInactivityZ(1);

Serial.print(x);

Serial.print(“ , “);

//look of tap movement on this axes - 1 == on; 0 == off

Serial.print(y);

accel.setTapDetectionOnX(0);

Serial.print(“ , “);

accel.setTapDetectionOnY(0);

Serial.println(z);*/

accel.setTapDetectionOnZ(1); double xyz[3] = {0, 0, 0}; //set values for what is a tap, and what is a double tap (0-255)

double ax, ay, az;

accel.setTapThreshold(50); //62.5mg per increment

for (int i = 0; i < 10; i++)

accel.setTapDuration(15); //625us per increment

{

accel.setDoubleTapLatency(80); //1.25ms per increment

double newxyz[3];

accel.setDoubleTapWindow(200); //1.25ms per increment

accel.get_Gxyz(newxyz); if (newxyz[0] > xyz[0])

//set values for what is considered freefall (0-255)

xyz[0] = newxyz[0];

accel.setFreeFallThreshold(7); //(5 - 9) recommended - 62.5mg per increment

if (newxyz[1] > xyz[1])

accel.setFreeFallDuration(45); //(20 - 70) recommended - 5ms per increment

xyz[1] = newxyz[1]; if (newxyz[2] > xyz[2])

//setting all interrupts to take place on int pin 1

xyz[2] = newxyz[2];

//I had issues with int pin 2, was unable to reset it

delay(100);

accel.setInterruptMapping( ADXL345_INT_SINGLE_TAP_BIT, ADXL345_INT1_

}

PIN ); accel.setInterruptMapping( ADXL345_INT_DOUBLE_TAP_BIT, ADXL345_ INT1_PIN );

if (xyz[0] > 15)

{

accel.setInterruptMapping( ADXL345_INT_FREE_FALL_BIT, ADXL345_INT1_

xyz[0] = (((xyz[0]) & 0b1111));

PIN );

Serial.print(“Subtotal x1 “);

accel.setInterruptMapping( ADXL345_INT_ACTIVITY_BIT,

ADXL345_INT1_

Serial.print(xyz[0]);

PIN );

ax = ((ax) + (xyz[0]<<8))*-1;

accel.setInterruptMapping( ADXL345_INT_INACTIVITY_BIT, ADXL345_INT1_

Serial.print(“Subtotal x “);

PIN );

Serial.print(ax);

}

//register interrupt actions - 1 == on; 0 == off

else

accel.setInterrupt( ADXL345_INT_SINGLE_TAP_BIT, 1);

{

accel.setInterrupt( ADXL345_INT_DOUBLE_TAP_BIT, 1); accel.setInterrupt( ADXL345_INT_FREE_FALL_BIT, 1); accel.setInterrupt( ADXL345_INT_ACTIVITY_BIT, 1); accel.setInterrupt( ADXL345_INT_INACTIVITY_BIT, 1);

ax= (ax) + (xyz[0]<<8) Serial.print(ax) }*/ ax = xyz[0]; if ( ax > 15 )

accel.get_Gxyz(gains_orig);

ax -= 246.42;

displayBars(10);

ay = xyz[1];

delay(5000);

if ( ay > 15 )

void loop(void) {

az = xyz[2];

}

ay -= 246.42; if ( az > 15 ) //Boring accelerometer stuff

az -= 228.89;

int x,y,z;

Serial.print(“X=”);

accel.readAccel(&x, &y, &z); //read the accelerometer values and

Serial.print(ax);

store them in variables x,y,z

Serial.println(“ g”);

Project Canary

Appendix

171

Serial.print(“Y=”);

}

Serial.print(ay);

// turn off all pins higher than the ledLevel:

Serial.println(“ g”);

else {

Serial.print(“Z=”);

digitalWrite(ledPins[thisLed], LOW);

Serial.println(az);

}

Serial.println(“ g”);

}

Serial.println(“**********************”);

}

//Spark.publish(“X”, String(ax)); //delay(500); Spark.publish(“Y”, String(ay)); //delay(500); //Spark.publish(“Z”, String(az)); double gax = ax - gains_orig[0]; double gay = ay - gains_orig[1]; double gaz = az - gains_orig[2]; int graph = int(abs(gax * 5) + abs(gay * 5) + abs(gaz * 5)); Spark.publish(“graph”, String(graph)); if (graph > 10) graph = 10; displayBars(graph); gains_orig[0] = ax; gains_orig[1] = ay; gains_orig[2] = az; /* //getInterruptSource clears all triggered actions after returning value //so do not call again until you need to recheck for triggered actions byte interrupts = accel.getInterruptSource(); // freefall if(accel.triggered(interrupts, ADXL345_FREE_FALL)){ Serial.println(“freefall”); //add code here to do when freefall is sensed } //inactivity if(accel.triggered(interrupts, ADXL345_INACTIVITY)){ Serial.println(“inactivity”); //add code here to do when inactivity is sensed */ } void displayBars (int ledLevel) { for (int thisLed = 0; thisLed < 10; thisLed++) { // if the array element’s index is less than ledLevel, // turn the pin for this element on: if (thisLed < ledLevel) { digitalWrite(ledPins[thisLed], HIGH);

172

Appendix

Project Canary

Program Code Master Spark Core #define REF_PIN 2 void getCurrentTemp( int *sign, int *whole, int *fract); char temp_string[10]; void setup() { //Serial.begin(9600); // initialize DS18B20 datapin digitalWrite(REF_PIN, LOW); pinMode(REF_PIN, INPUT); // sets the digital pin as input (logic 1) pinMode(15, INPUT); }

pinMode (Pin, OUTPUT); delayMicroseconds (5); pinMode (Pin, INPUT); delayMicroseconds (60);

void loop() { getCurrentTemp(temp_string); Spark.publish("Temp", temp_string); delay(5000); }

} else { digitalWrite (Pin, LOW); pinMode (Pin, OUTPUT); delayMicroseconds (60); pinMode (Pin, INPUT); }

void OneWireReset (int Pin) // reset. Should improve to act as a presence pulse { digitalWrite (Pin, LOW); pinMode (Pin, OUTPUT); // bring low for 500 us delayMicroseconds (500); pinMode (Pin, INPUT); delayMicroseconds (500); }

}

void OneWireOutByte (int Pin, byte d) // output byte d (least sig bit first). { byte n;

byte OneWireInByte (int Pin) // read byte, least sig byte first { byte d, n, b;

Appendix

d = d >> 1; // now the next bit is in the least sig bit position.

for (n = 0; n < 8; n++) { digitalWrite (Pin, LOW); pinMode (Pin, OUTPUT); delayMicroseconds (5);

for (n = 8; n != 0; n--) { if ((d & 0x01) == 1) // test least sig bit { digitalWrite (Pin, LOW);

174

}

Project Canary

if (sign) { temp[0] = '-'; } else { temp[0] = ' '; }

pinMode (Pin, INPUT); delayMicroseconds (5); b = digitalRead (Pin); delayMicroseconds (50); d = (d >> 1) | (b << 7); // shift d to right and insert b in most sig bit position } return (d); }

if (whole / 100 == 0) { temp[1] = ' '; } else { temp[1] = whole / 100 + '0'; }

void getCurrentTemp (char *temp) { int HighByte, LowByte, TReading, Tc_100, sign, whole, fract; OneWireReset (REF_PIN); OneWireOutByte (REF_PIN, 0xcc); OneWireOutByte (REF_PIN, 0x44); // perform temperature conversion, strong pullup for one sec OneWireReset (REF_PIN); OneWireOutByte (REF_PIN, 0xcc); OneWireOutByte (REF_PIN, 0xbe);

}

temp[2] = (whole - (whole / 100) * 100) / 10 + '0' ; temp[3] = whole - (whole / 10) * 10 + '0'; temp[4] = '.'; temp[5] = fract / 10 + '0'; temp[6] = fract - (fract / 10) * 10 + '0'; temp[7] = '\0';

LowByte = OneWireInByte (REF_PIN); HighByte = OneWireInByte (REF_PIN); TReading = (HighByte << 8) + LowByte; sign = TReading & 0x8000; // test most sig bit if (sign) // negative { TReading = (TReading ^ 0xffff) + 1; // 2's comp } Tc_100 = (6 * TReading) + TReading / 4; // multiply by (100 * 0.0625) or 6.25 whole = Tc_100 / 100; // separate off the whole and fractional portions fract = Tc_100 % 100;

Project Canary

Appendix

175