EE180D_Weekly_Engineering_Journal_Smart_Wearable_Device - EE180D SystemsEngineering YuhuaiLin,ManniChen,YunZhang Feb.02,2016 TableofContents

EE180D_Weekly_Engineering_Journal_Smart_Wearable_Device -...

This preview shows page 1 out of 7 pages.

You've reached the end of your free preview.

Want to read all 7 pages?

Unformatted text preview: EE180D Systems Engineering Smart Wearables in Workplace Weekly Engineering Journal Yuhuai Lin, Manni Chen, Yun Zhang Feb. 02, 2016 Weekly Engineering Journal ​ Table of Contents Table of Contents 1 Mission Description Abstract 2 Team 3 Team Member Responsibilities 4 Progress Report Referencing Design Document 5 Source Code 6 Platform Development 7 Development Progress 8 Test Results 9 Development Concerns or Limitations Noted 10 References 2 Weekly Engineering Journal 1 Mission Description Abstract This abstract describes your mission. This will answer the famous Heilmeir Questions (​ ​ ) These questions are always asked by industry management, investors, and others evaluating your plans. I have included the questions here formatted for our program missions: 1) What is your product development mission? Our device is devoted to assessing and improving the work efficiency for people working in the office. It combines different sensors to detect the comprehensive working infrastructure and monitor individual context. The system can make notifications to provide better environment suggestions. Besides, the pre­programmed system can fully evaluate individual working efficiency and monitor individual participation in team work through the collected data. All the assessments of each individual can be uploaded to personal cloud and the company’s database as a source for further evaluation. Internet to Things (IoT) is formed which makes data analysis easier and more accurate . Our device is portable and light­weighted, in the form of clipper, watch or wristband so that it can be carried easily with the user. 2) How is it done today, and what are the limits of current practice? The traditional way of tracking individual work performance is through sign­up sheets or time cards, which can only help with attendance checking but are not able to monitor individual’s involvement in work. We also waste a lot of time in assessment using and analyzing data gathered through traditional methods. Other than the traditional way, nowadays some companies have applied wearable devices to workplace. For example, British Grocery Tesco is using armbands to track the goods that are transporting, which makes it unnecessary for workers spending time marking clipboards. Boeing has been using gears that can give instructions to wire assembly personnel without them needing to look at manuals. Although these devices have already helped to increase working efficiency and satisfactory, we found that most of the devices are limited to certain fields or functions and does not have ubiquitous value. 3)What's new in your approach and why do you think it will be successful? Our product might be a breakthrough in the workplace performance area to help company to fairly evaluate their workers’ productivity based on the data gathered through a programmed chip with embedded sensors. Meanwhile, the device can also provide environment and personal exercise suggestions, which will also benefit to individual officers. The novelty of our device is that it contains a variety of sensors so that more functions could be integrated in this wearable device, which will benefit most of the daily workplace. The device comes out of ideas from the brainstorm by our group members. Today they need to be detailed analyzed and tested to be put into our real device. 4) Who are the users and user community that will benefit from your product? Companies with indoor offices and their employees will eventually benefit from our device. 5) What will be the impact of your product and service if you are successful? 3 Weekly Engineering Journal Our device will increase efficiency in workplace and offer more accurate evaluation of both individuals and team productivity. Besides, our device will also increase individual’s satisfactory on his or her work. 6) What are the midterm and final "exams" to determine if you are successful in your product development? Since our device development involves both software and hardware implementation, there are a couple of ways to thoroughly test the development progress. The success and accuracy of collected data, the feasibility to judge the work performance and group interaction, the practicability of the device suggestions and privacy consideration can all be considered as the factors in examining our device progress. 2 Team Yuhuai Lin, UID: 004­160­688, Mobile: 310­308­0740, E­mail: ​ [email protected] Manni Chen, UID: 304­145­309, Mobile: 310­435­8121, E­mail: [email protected] Yun Zhang, UID: 004­145­344, Mobile: 310­800­5284, E­mail: ​ [email protected] 3 Team Member Responsibilities Please include one paragraph describing detailed responsibilities for each team member. This includes original proposals and also should be expanded as progress continues. Responsibilities must evolve as progress continues. There should not be duplication of these paragraphs. Each team member should prepare a distinct objective. 1) Common Parts: ​ 9 degree of freedom sensor, GPIO Block Programming, ADC Block Programming 2) Individual Parts: Yun Zhang hardware: sound level sensor and humidity sensor software: implementation of the algorithm for individual context assessment Yuhuai Lin 4 Weekly Engineering Journal hardware: light sensor and thermometer software: implementation of the algorithm for individual productivity and exercise assessment Manni Chen hardware: infrared emitter and sensor software: implementation of the algorithm for assessment of team interaction 4 Progress Report Referencing Design Document This is the general format for our reports. Many of the sections below may not change often. For this section please include: 1. Generally a one page description 2. Describes progress ​ by each ​ team member with ​ attributions​ to each team member For this week, we all completed tutorial 6 and 7 together and just started the 9DOF tutorial and completed setting Intel Edison into Access Point Mode 3. Progress must include: a. Description of hardware or software development or experimental measurements with analysis with a concrete description. For this week, we successfully finished the tutorial 6 and 7 and started tutorial of 9DOF sensors. In tutorial 6, we familiarized ourselves with the Intel cloud­based analytics service. We learnt to register an Intel Edison and sensors/actuators. We also learnt to collect data provided by Edison through pre­installed IoT agent, which converts the UDP packets into REST calls, and use custom components such as rotary sensor. In the tutorial 7, we learnt how to send requests from the Cloud Analytics to the Intel Edison to control the LED light through MQTT protocol. Then we learnt to set up rules on the Cloud­based Analytics to send notifications (such as emails) when sensor observation meets the rule requirement. At the end of tutorial 7, we learnt to make REST calls directly to the cloud so that we can bypass the IoT agent. Lastly, we started to try out the tutorial of 9DOF sensors and finally we set the Edison to AP mode. 4. Describes problems encountered In tutorial 6, when we tried to modify rules to turn on the LED light in addition to email notification when the light level is lower than 20, we did not succeed. Although we received the emails several times, the LED light never turned on. 5 Weekly Engineering Journal When we started the tutorial of the 9DOF sensor, we needed to first set the Intel Edison to Access Point (AP) mode. We tried to follow the tutorial on the IoT website of Intel ( ­us/getting­started­with­ap­mode­for­intel­edison­board), but we found that the method on the website did not really work. 5. Describes solutions developed We failed multiple times and did not find a solution to the problem we encountered in tutorial 6. For the sake of time, we put aside the problem and proceeded to the next step. With the help of Chris, we were able to change Intel Edison into Access Point mode without manually operating on the board. By typing the following command: ​ configure_edison ­­enableOneTimeSetup ­­persist​ , ​ we turned on the Access Point mode of the Intel Edison. It will maintain in this mode even if we power it off. Then we were able to SSH connect the Intel Edison and apply it to 9DOF sensor. 6. Describes proposed changes in plans 7. Describe any changes in schedule 8. Changes that result in design modifications (for example a new interface specification) must also be reflected in design document with a revision update 5 Source Code This section includes a source code development history. This may be a list and description of modules that have been developed along with a brief description (one sentence). This may also include source code excerpts or entire programs that have been developed that you feel are important to highlight. 6 Platform Development This section includes a platform development history for those projects that include hardware platform system development. This may be a list and description of systems including sensor systems, sensor components, embedded platform components and any other assets that have been developed along with a brief description (one sentence). This may also include architectural diagrams and images of systems have been developed that you feel are important to highlight. 7 Development Progress This section includes a development history of progress in the area of algorithm development, system implementation, or other areas as applicable. This may be one paragraph to one page in length. 6 Weekly Engineering Journal 8 Test Results This section describes test results including. 1. Test approach (a few sentences to one paragraph) 2. Test results (This may include a few sentences to one paragraph or may include the output of log files and graphical data as applicable) 3. Discussion of test results comparing actual results with desired behavior (a few sentences to one paragraph as applicable) 9 Development Concerns or Limitations Noted This section includes any discoveries that lead to confusion, recognition of development unknowns or risks, or any other concern. We will address each of these with planning and assistance. 1. 2. Security: On one hand, we need to make sure the individual’s privacy is well preserved. On the other hand, we need to report the overall individual’s workplace performance to their supervisors. There must be a balance between these two factors to make sure that supervisors can successfully evaluate the employee’s performance and the employees will not feel being overly serveiled. People’s workplace performance varies. It is very hard to have an unique standard to evaluate everyone’s productivity fairly. 10 References This section lists any new references that you have found important or required in this last week. 1. ­in­the­workplace 2. 3. 4. ­blocks­for­intel­edison­­­9­degrees­of­free dom­block­?_ga=1.29734655.1554489867.1454471599 7 ...
View Full Document

  • Spring '09
  • POTTIE
  • engineering journal, Weekly Engineering Journal

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture