Professional Documents
Culture Documents
Calvin College
2014-2015
Submitted By:
1
©Carl Cooper, Brad Kunz, Jessica Par, Nick VanDam, and Calvin College
2
Executive Summary
As technology spreads into markets which were once unexplored, advantages of new processes and
information available can arise as a result. With many individuals becoming increasingly interested in
tracking their personal fitness levels throughout the day, technology has recently advanced enough in
order to make this available and efficient to do so. With many personal fitness tracking devices already
on the market, a company known as BioBit has identified a unique need in this market that has yet to be
successfully fulfilled, namely the area of group fitness. With teams and workout groups unable to track
data both individually and as a cohesive group, information is difficult to compare and analyze between
multiple individuals. BioBit sees a need where a team-oriented fitness tracking device can be used in
order to easily track and display information to active groups such as sports teams and training groups.
A team of four electrical and computer engineering students from Calvin College decided to solve this
problem by designing a wearable tracking device that will send real-time data to an Android app where
the user can see the entire team’s fitness information. This fitness tracking system is designed for
coaches, trainers, athletes, and sports teams. Each athlete will wear a fitness device, which will collect
data from biometric sensors. These sensors include the ability to track information such as a user's heart
rate, acceleration, and steps taken. The data taken from these sensors will then be sent to a centralized
hub, which communicates with all the devices in the network via Wi-Fi. Once the information is received
by the hub, it is then published to a web-hosted server and database to be stored and later referenced
by the partnering Android app. The intent of the partnering Android app is to provide the fitness leader,
such as a coach or trainer, a user-friendly interface in order to compare and analyze the data obtained.
With this information in hand, a unique advantage is then available to the users in order to make
educated and timely assessments based on the real-time data received through the technology.
BioBit is requesting $430,000.00 as startup capital. It will be used for both additional design of
prototypes and the first production models that will be sold. This capital will also support the salaries of
the designers, workers, facilities, marketing, and raw materials. Through growth and additional
production, BioBit plans to be debt free by its 3rd year, giving the company greater flexibility and cash
flow to continue into the future. The goal of the core group of designers is to have a deliverable product
by May of 2015.
3
Table of Contents
Executive Summary....................................................................................................................................... 3
Table of Contents .......................................................................................................................................... 4
1. Introduction ........................................................................................................................................ 10
1.1 Calvin College Engineering Program ........................................................................................... 10
1.2 Team Information ....................................................................................................................... 10
1.2.1 Carl Cooper ............................................................................................................................. 10
1.2.2 Brad Kunz................................................................................................................................ 11
1.2.3 Jessica Par ............................................................................................................................... 11
1.2.4 Nick VanDam .......................................................................................................................... 11
1.3 Report Overview ......................................................................................................................... 12
1.4 Design Norms .............................................................................................................................. 13
1.4.1 Trust........................................................................................................................................ 13
1.4.2 Integrity .................................................................................................................................. 13
1.4.3 Caring...................................................................................................................................... 13
2. Project Requirements ......................................................................................................................... 13
2.1 Project Statement ....................................................................................................................... 14
2.2 Requirements .............................................................................................................................. 14
2.2.1 Functional Requirements ....................................................................................................... 14
2.2.2 Electrical Requirements.......................................................................................................... 15
2.2.3 Software Requirements.......................................................................................................... 15
2.2.4 Communication Requirements .............................................................................................. 15
2.2.5 Physical Requirements ........................................................................................................... 16
3. System Design ..................................................................................................................................... 16
3.1 System Communication .............................................................................................................. 16
3.1.1 Possible Solutions ................................................................................................................... 17
3.1.2 Decision Criterion ................................................................................................................... 17
3.1.3 Decision Matrix....................................................................................................................... 18
3.2 Wearable Location ...................................................................................................................... 20
3.2.1 Possible Solutions ................................................................................................................... 20
3.2.2 Decision Criterion ................................................................................................................... 21
4
3.2.3 Decision Matrix....................................................................................................................... 22
3.3 End-User Application Platform ................................................................................................... 23
3.3.1 Possible Solutions ................................................................................................................... 23
3.3.2 Decision Criterion ................................................................................................................... 23
3.3.3 Decision Matrix....................................................................................................................... 24
3.4 Overall System Block Diagram .................................................................................................... 25
4. Fitness Tracking Device ....................................................................................................................... 26
4.1 Fitness Tracking Device Architecture .......................................................................................... 26
4.2 Hardware .................................................................................................................................... 26
4.2.1 Processing and Communication Board .................................................................................. 26
4.2.2 Heartbeat Sensor.................................................................................................................... 28
4.2.3 Step Sensor ............................................................................................................................. 30
4.3 Battery......................................................................................................................................... 32
4.3.1 Requirements ......................................................................................................................... 32
4.3.2 Alternatives ............................................................................................................................ 32
4.3.3 Decision .................................................................................................................................. 33
4.3.4 Implementation ..................................................................................................................... 34
4.4 Software ...................................................................................................................................... 34
4.4.1 Communication Board............................................................................................................ 34
5. Central Hub ......................................................................................................................................... 34
5.1 Central Hub Architecture ............................................................................................................ 34
5.2 Hardware .................................................................................................................................... 34
5.2.1 Requirements ......................................................................................................................... 34
5.2.2 Alternatives ............................................................................................................................ 35
5.2.3 Decision Criterion ................................................................................................................... 36
5.2.4 Decision .................................................................................................................................. 36
5.2.5 Implementation ...................................................................................................................... 37
5.3 Software ...................................................................................................................................... 37
5.3.1 Server...................................................................................................................................... 37
5.3.2 Data Transmission Protocol.................................................................................................... 37
5.3.3 Packet Processing ................................................................................................................... 37
6. End-User Application .......................................................................................................................... 38
5
6.1 Software Design .......................................................................................................................... 38
6.1.1 Overview................................................................................................................................. 38
6.1.2 Functionality ........................................................................................................................... 38
6.1.3 Inputs ...................................................................................................................................... 38
6.1.4 Outputs ................................................................................................................................... 38
6.1.5 Software Updates ................................................................................................................... 39
7. Physical Design Specifications............................................................................................................. 39
7.1 System Enclosure ........................................................................................................................ 39
7.1.1 Wearable Design .................................................................................................................... 39
7.1.2 Material Selection .................................................................................................................. 43
8. Prototype and Deliverables ................................................................................................................ 43
8.1 Final Prototype ............................................................................................................................ 43
8.2 Deliverables ................................................................................................................................ 43
8.2.1 Fall Semester Deliverables ..................................................................................................... 44
8.2.2 Spring Semester Deliverables ................................................................................................. 44
9. Testing ................................................................................................................................................. 44
9.1 Completed Testing ...................................................................................................................... 44
9.1.1 Raspberry Pi............................................................................................................................ 44
9.1.2 Intel Edison ............................................................................................................................. 45
9.2 Future Testing ............................................................................................................................. 45
9.2.1 WLAN on the Raspberry Pi ..................................................................................................... 45
9.2.2 Send Data from Sensors to Intel Edison ................................................................................. 45
9.2.3 Send Data from Database to Mobile App .................................................................................. 46
9.2.4 Battery Test for Intel Edison Board ........................................................................................ 46
9.2.5 Server Traffic Test................................................................................................................... 46
10. Business Plan................................................................................................................................... 46
10.1 Vision and Mission Statement .................................................................................................... 46
10.2 Industry Profile and Overview .................................................................................................... 46
10.2.1 Industry Background and Overview ..................................................................................... 47
10.3 Regulatory restrictions ................................................................................................................ 47
10.4 Significant Trends ........................................................................................................................ 48
10.4.1 Growth Rate ......................................................................................................................... 48
6
10.4.2 Barriers to Entry and Exit...................................................................................................... 48
10.4.3 Key Factors for Success in the Industry ................................................................................ 48
10.4.4 Outlook for the Future ......................................................................................................... 48
10.5 Business Strategy ........................................................................................................................ 49
10.5.1 Desired Image and Position in Market ................................................................................. 49
10.5.2 Company Goals and Objectives ............................................................................................ 49
10.6 SWOT Analysis............................................................................................................................. 49
10.6.1 Internal Strengths ................................................................................................................. 49
10.6.2 Internal Weaknesses ............................................................................................................ 50
10.6.3 External Opportunities ......................................................................................................... 50
10.6.4 External Threats ................................................................................................................... 50
10.7 Competitive Strategy .................................................................................................................. 50
10.7.1 Cost Leadership and Differentiation .................................................................................... 50
10.7.2 Focus..................................................................................................................................... 51
10.8 Company Products and Services ................................................................................................. 51
10.8.1 Product Description and Service Features ........................................................................... 51
10.8.2 Uniqueness ........................................................................................................................... 51
10.8.3 Customer Benefits ................................................................................................................ 51
10.8.4 Warranties and Guarantees ................................................................................................. 52
10.8.5 Future Product or Service Offerings ........................................................................................ 52
10.9 Marketing Strategy ..................................................................................................................... 52
10.9.1 Target Market ....................................................................................................................... 52
10.9.2 Market Size and Tends ......................................................................................................... 53
10.9.3 Advertising and Promotion .................................................................................................. 53
10.9.4 Pricing ................................................................................................................................... 54
10.10 Competitive Analysis ............................................................................................................... 55
10.10.1 Existing competitors ........................................................................................................... 55
10.10.2 Potential competitors......................................................................................................... 55
10.11 Description of Management Team ......................................................................................... 56
10.11.1 Key managers ..................................................................................................................... 56
10.11.2 Future Additions to Management Team ............................................................................ 57
10.11.3 Operations .......................................................................................................................... 58
7
10.2 Financial Statements ....................................................................................................................... 59
10.2.1 Income Statement (Annual, 3 years) ....................................................................................... 59
10.2.2 Cash Flow Statement (Quarterly, 3 years) ............................................................................... 60
10.3 Break-Even Analysis ........................................................................................................................ 61
10.4 Ratio Analysis .................................................................................................................................. 62
11. Project Management ...................................................................................................................... 63
11.1 Team Organization .................................................................................................................. 63
11.1.1 Documentation Organization ............................................................................................... 63
11.1.2 Division of Work ................................................................................................................... 63
11.1.3 Milestones ............................................................................................................................ 64
11.2 Schedule .................................................................................................................................. 64
11.2.1 Schedule Management......................................................................................................... 64
11.2.2 Critical Path .......................................................................................................................... 64
11.3 Operational Budget ................................................................................................................. 64
11.4 Method of Approach ............................................................................................................... 65
11.4.1 Design Methodology ............................................................................................................ 65
11.4.2 Research techniques ............................................................................................................ 65
11.4.3 Team communication........................................................................................................... 65
12. Conclusions ..................................................................................................................................... 65
12.1 Project Feasibility .................................................................................................................... 65
12.1.1 Technical Aspect ................................................................................................................... 65
12.1.2 Cost Aspect ........................................................................................................................... 66
12.2 Lessons Learned ......................................................................................................................... 66
12.3 Credits and Acknowledgements ............................................................................................. 67
13. References ...................................................................................................................................... 68
8
Table of Figures
Figure 1. Team Photo (left to right) - Brad Kunz, Nick VanDam, Jessica Par, and Carl Cooper .................. 10
Figure 2 - High-level System Diagram ......................................................................................................... 14
Figure 3 – Diagram of Range for Wi-Fi and Bluetooth Over Standard Soccer Field Dimensions ................ 20
Figure 4 - Level One Block Diagram of the Overall System ......................................................................... 26
Figure 5 - Intel Edison Size Comparison ...................................................................................................... 27
Figure 6 - Adafruit FLORA Size Comparison ................................................................................................ 28
Figure 7 – Polar HeartRate Sensor .............................................................................................................. 29
Figure 8 – TI TIDA-00011 Sensor ................................................................................................................. 30
Figure 9 – Pulse Sensor SEN-11574............................................................................................................. 30
Figure 10 - SparkFun Triple Axis Accelerometer - ADXL335 ....................................................................... 31
Figure 11 - STP156 Pedometer ................................................................................................................... 31
Figure 12 – Raspberry Pi B+ ........................................................................................................................ 35
Figure 13 – BeagleBone Black ..................................................................................................................... 36
Figure 14 - Chest-Mounted Wearable Concept .......................................................................................... 40
Figure 15 - Waist-Mounted Wearable Concept .......................................................................................... 40
Figure 16 – Wrist-Mounted Concept View of Face ..................................................................................... 41
Figure 17 – Wrist-Mounted Concept Right Side View ................................................................................ 41
Figure 18 – Wrist-Mounted Concept Side View of Wrist Strap .................................................................. 42
Figure 19 – Wrist-Mounted Wearable Concept Wire View ........................................................................ 42
Figure 20 - Overview of Company Structure (dotted line to show initial organization) ............................. 59
Table of Tables
Table 1 - Decision Matrix for Communication Protocol.............................................................................. 19
Table 2 - Decision Matrix for Device Placement ......................................................................................... 22
Table 3 - Decision Matrix for Device Placement ......................................................................................... 24
Table 4 - Battery type comparison .............................................................................................................. 32
Table 5 - Decision Matrix for Central Hub................................................................................................... 36
Table 6 – Project Deliverables and Timeline ............................................................................................... 43
Table 7 - Income Statement for First Three Years ...................................................................................... 59
Table 8 - Cash Flow for First Three Years (Yearly Overview) ...................................................................... 60
Table 9 – Cash Flow for First Three Years (Quarterly) ................................................................................ 61
Table 10 - Break-Even Analysis ................................................................................................................... 61
Table 11 - Ratio Analysis ............................................................................................................................ 63
9
1. Introduction
This section will provide an introduction to the Senior Design Project by introducing the Calvin College
Engineering Program, giving details of the Senior Design team, breaking down the Project Proposal and
Feasibility Study document, and giving an overview of the team's design norms they are incorporating
into the project.
Figure 1. Team Photo (left to right) - Brad Kunz, Nick VanDam, Jessica Par, and Carl Cooper
10
smartphone apps. He gained experience creating and sending data over wireless networks,
programming microcontrollers and Android apps, and reducing power consumption on both
microcontrollers and smartphones. He understands the benefit of being able to track players on sports
teams from his experience of playing on sports teams all the way through elementary and high school in
Chiang Mai, Thailand, including Varsity Basketball and Volleyball.
In his spare time Carl enjoys pursuing the outdoors through rock climbing and backpacking, as well as all
things audio, from recording to building guitar amps and effects pedals.
Brad enjoys staying active through playing sports such as soccer, tennis, golf, hiking, and going to the
gym. He is also interested in audio projects and music production.
Jessica is currently working as a Student Office Assistance at the Engineering Department. She organizes
documents, updates the engineering website, helps plan the department events, and assists professors
when needed. She is also a student leader for Calvin’s Women and Engineering club. She plans social
events and study groups for the women engineers.
In her spare time, Jessica enjoys being active through going to the gym with friends, rock climbing,
camping.
11
working for Grand Rapids Christian High School Athletics as an Event Manager and Facility Caretaker.
Nick also works as an intern at URS Corporation within the Intelligent Transportation Systems (ITS)
division. He has held this position since May of 2013. This position is concerned with the technology
behind roadways which helps to improve the safety and efficiency of our transportation systems.
Surveillance systems, vehicle detectors, dynamic message signs (DMS), and their means of
communication (Fiber & Wireless) are all things encountered through this position.
In his spare time, Nick is also working on side projects involving mechanical and electrical repairs for
both the Calvin and local communities.
Section 9: Testing
Section 9 outlines how the system components will be incrementally tested.
12
Section 10: Business Plan
Section 10 outlines a business plan for a potential startup company that is developed around
selling this project.
1.4.1 Trust
Trust is something that shall be integral to the design. The users of the devices are relying on them to
improve their fitness. Trust will be achieved by providing reliable data, and constructing a dependable
and comfortable device. The customer should feel comfortable enough to know that the device’s
primary goal is to help improve fitness and not harm them.
1.4.2 Integrity
This fitness tracking device shall have a harmonious form and functionality to it. The users of this device
should feel comfortable using the device in any situation and feel like it is merely an extension of their
body and not something that will hinder their performance in any way.
1.4.3 Caring
Caring is another design norm to be considered in the design process. The team wants the user to know
that this fitness device is for their physical, mental, and emotional benefit.
2. Project Requirements
For the design scope and standards set forth by the team, please refer to the content herein. It is in
these section where the requirements are defined which the team's core values and standards are
present.
13
2.1 Project Statement
With the market for personal fitness tracking devices oversaturated with little variation in product
characteristics, very little has been done on the side of team-oriented fitness trackers. Therefore,
BioBit's goal is to design a team-oriented fitness tracker to provide a better way to gauge the intensity
and effectiveness of workouts. This fitness tracking system is designed for coaches, trainers, athletes,
and sport teams.
The solution that the team proposes provides a team-oriented fitness wearable that will connect to a
centralized hub, where the data from all the wearable devices will be collected. The user will be able to
access the fitness data using an Android app anytime within the local area network (LAN) via Wi-Fi
communication protocol. The product will provide the users the ability to access their data in real time.
A high-level system diagram of this can be seen in Figure 2.
2.2 Requirements
A list of requirements regarding the breakdown of functionality, electrical systems, software,
communication protocol standards, and physical requirements are listed below. It should be noted that
the corresponding requirement name to each definition will be used in the remaining of the report
rather than restating the definition.
REQ 2.2.1.2 All devices shall have power on, off, and reset capabilities.
To provide proper functionality to users, they shall be able to turn on and off the devices when
they are ready to use them and when they are done with the devices. They also need to be able
to reset the devices in case some error occurs or they would like to restart the system.
14
REQ 2.2.1.3 All devices shall indicate status such as ON/OFF and mode.
In order for the users to easily recognize when devices are on or off, there will be an LED to
indicate when the device is on.
The devices will be used outdoors, thus submitting them to wind and rain as well as sweat from
being worn on the body of athletes.
A typical practice session is two hours, so all devices being used shall have adequate power
supplies to last two hours at the minimum.
REQ 2.2.2.3 All devices shall be portable and have internal rechargeable power supplies.
The battery will last a minimum of one practice session and it is inconvenient and expensive to
buy batteries and change them after every practice. To save time and money, each device shall
be rechargeable from a micro USB port.
REQ 2.2.2.4 The first prototype will incorporate a heart rate sensor.
Different data are important to different users so they shall be able to select what data they
want to be displayed. Data can also be grouped in several ways, such as by individual or by the
whole team, so users shall be able to choose what data is displayed and what format it will be
displayed (lists, graphs, charts).
REQ 2.2.3.2 Hub software shall run on an easily customizable operating system.
REQ 2.2.3.3 The hub shall run a database to store the data.
15
The project requires the use of a smartphone for the coach so it shall be compatible with
smartphones, which limits the protocol to Bluetooth (IEEE 802.15), Wi-Fi (IEEE 802.11), or
ZigBee (IEEE 802.15.4) combined with one of the other two.
The project shall be useful to a soccer team with 11 players per team and thereby shall support
a minimum of 22 players at a time.
REQ 2.2.4.3 The protocol needs to work over a minimum range of 88.5 m.
If the hub is centered on the side of a soccer field, the maximum distance a player may be from
the hub is the opposite corner, or 88.5 m away.
REQ 2.2.4.4 The protocol shall use adequate power to last a minimum of two hours.
The device shall be able to last for an entire practice session. Most practices do not last longer
than two hours, so the protocol shall not consume so much power that it will drain the battery
in less than two hours.
REQ 2.2.5.3 The device shall be intuitive for operation and wear.
REQ 2.2.5.4 The design shall consider the environment when selecting materials for construction.
REQ 2.2.5.6 The device and central hub shall be able to resist minor exposure to water.
REQ 2.2.5.7 The device shall be impact resistant from consistent exposure to athletic activity.
3. System Design
This section discusses the approach to the system design and how it serves as a solution to the problem
stated earlier in the document. The section will look at several design alternatives that will affect the
scope of the design. At the end of each section there is a selected best design based on a decision
matrix. These high-level decisions will go into further detail in the following sections of this document.
16
decisions made throughout because the microprocessors that are chosen shall have the capability to use
the protocol or have a way to interface with the protocol. The three most common wireless protocols
are listed below and rated in a decision matrix to determine the most suited protocol for this project. It
was found that Wi-Fi is the best choice for this product because it can be implemented in the most
intuitive and reliable manner.
3.1.1.1 Wi-Fi
Wi-Fi (IEEE 802.11) is a wireless communication based on Ethernet (IEEE 802.1). It was designed to
connect devices together on a wireless local area network (WLAN) and ultimately to a router and the
World Wide Web. It uses collision avoidance (more specifically Carrier Sense Multiple Access with
Collision Avoidance, CSMA/CA) to eliminate communication problems arising from multiple devices
talking at the same time. It is one of the most prevalent forms of wireless communications, being found
in computers and smartphones. This gives it an advantage because there is a wealth of information on
how it works and how to use it. It also gives the project the possibility to post information on the
Internet, thus expanding the accessibility of the data from the WLAN to anywhere in the world there is
Internet.1
3.1.1.2 Bluetooth
Bluetooth (IEEE 802.15) is a form of wireless communication developed to provide a low power
alternative over a short range. It is primarily used to connect peripheral devices to a master, such as
Bluetooth mice and keyboards to a computer. It is also increasingly being used in smartphones to
connect to speakers, other smartphones, and even personal fitness tracking devices. Bluetooth uses
adaptive frequency hopping to prevent data packet collisions. Bluetooth has an advantage that it uses
very little power, thus making devices last longer between charges.2
3.1.1.3 ZigBee
ZigBee (IEEE 802.15.4) was developed to address the shortcomings of Bluetooth and Wi-Fi. It was
designed to create wireless personal area networks (WPAN) for applications that use a lower
transmission of data rate. It has lower power consumption than Wi-Fi but it can also have a larger range
than Bluetooth. ZigBee also uses CSMA/CA to handle issues that could arise from multiple devices trying
to transmit at the same time. It was designed to be used in applications such as home automation or
other wireless communication between devices around the home.3
17
3.1.2.1 Range
Each wireless communication has a different range and this is significant to the decision of which
communication to use. As determined by REQ 2.2.4.3, the protocol shall be able to transmit data from
each player back to the coach over a range of 80 m. Thus a suitable communication will allow players to
cover this distance and still reliably get data back to the coach.
18
with the given requirements. The alternative with the highest summed total from each criterion is to be
considered the best solution4.
19
Figure 3 – Diagram of Range for Wi-Fi and Bluetooth Over Standard Soccer Field Dimensions
20
3.2.1.1 Wrist
The age of smart watches is here and smart fitness devices were only a few steps ahead of them. The
wrist is a go-to location for personal fitness wearables because of its easy placement and it can serve as
a fashion piece. The wrist is also a good location for devices that require personal interaction with it,
such as button pushing, screen reading, and user-program interaction.
3.2.1.2 Chest
Chest mounts have also been used as a location for fitness trackers. The main purpose for placing a
fitness wearable on the chest is to get an accurate reading for a heart rate measure. A fitness tracker
typically requires skin contact, depending on what data it is attempting to collect. The chest mount
would have the bulk of the device placed on the back of the user with the heart rate sensor placed
around the front near the heart on a strap.
3.2.1.3 Head
A fitness wearable could be placed on the head in the form of a headband. This location is capable of
measuring the desired data, but it would be subject to the largest volume of sweat and it would have to
have a very low profile in the headband. Tracking from the head is a possible future design to be
integrated into helmet designs for contact sports.
3.2.1.4 Waist
A wearable device located on the waist has similar capabilities and requirements to the chest mount. It
would be worn like a belt and an adequate location to take heart rate readings would have to be found.
21
3.2.2.4 Unobtrusiveness
The location of the fitness tracking device needs to be placed in such a way that the user feels
comfortable and that it will not hinder their performance. This is based on movement during fitness
activities and whether the user would have to place it on the body under their clothes.
3.2.2.5 Weight
Given that the system would be about the same weight regardless of body placement, this criterion is
based on where the added weight of a wearable would be least noticeable to the user.
22
3.2.3.2 Recognized Weaknesses
For a wrist mounted device, the biggest weakness would be in the physical design. This is because the
design would have to find a middle ground between device functionality and size of the device.
Depending of the resources, budget, and capabilities of the team, a small wrist mounted wearable that
users would be willing to wear may not be capable for a prototype. However, the team is willing to
accept a larger device for a first prototype that could be reduced in a final design. Another issue the
team may face is that the wrist is not the most ideal location to track heart rate as the finger, ear, and
heart are better locations.
The chest mounted design has a few more issues than a wrist mounted design because it again will be
very difficult to design a device that can be mounted on the chest that users would be willing to wear.
This would be overcome by reducing the profile and adjusting where exactly on the chest it would be
located. Other weaknesses include having to deal with more sweat and not restrict movement or
breathing as well as be more adjustable for people of different size and shapes. Furthermore, it would
need to be designed more carefully in the event of a fall because it is important that it would not injure
the athlete or break due to the increased forces compared to a wrist mounted design.
3.3.1.2 Android
Android devices are becoming increasingly popular and now control over 80% of the market5 so
naturally BioBit would like to pursue this option. Android is developed by Google and is distributed as
open-source. One reason it is so popular is that there are a wide variety of devices that run Android with
many different price points and features. This presents a challenge to the developer to make sure that
the app will run on a variety of devices with different size screens and capabilities.
23
3.3.2.1 Usability
The usability of the operating system that is chosen is very important to the success of the project. Not
only does the team need to be able to develop an app in that operating system, but the usability on the
users’ side is also important. Android is developed using Java, which is very user friendly even if the
programmer has never coded in Java before. Android is open-source, which at times can make it easy to
use because there is documentation and it is customizable, but at other times more complicated and
difficult to use. On the other hand, iOS uses Objective C, which is quite different than the programming
languages the team members know and is more complicated than Java.6
3.3.2.2 Implementation
As the developers need to be able to design an app to use, the most crucial issue is whether or not such
an app can even be implemented. Furthermore, the ease of implementation is something that shall be
taken into consideration. Both Android and iOS are able to implement the desired functionality in an
app but Android is most likely easier to implement than iOS because of the programming language and
the rules are not as strict.
3.3.2.3 Customization
Both iOS and Android provide ample customization to the developer and the end user, but iOS has to
follow stricter guidelines than Android. Android is also much more customizable to the end user and
there is a wide variety of device specifications in Android that the developer needs to be aware of when
developing an app.
24
3.3.3.1 Best Solution
From the above discussion, the team shall focus primarily on developing an Android application. If there
is time, it would be a good stretch goal to develop an iOS application because many coaches and
athletes use iPads and iPhones. If BioBit was going to market, an iOS app would be needed, but it does
not fit in the scope of this project.
25
Figure 4 - Level One Block Diagram of the Overall System
4.2 Hardware
This subsection will discuss the design decision process for the hardware of the fitness device.
26
4.2.1.1 Requirements
The processing and communication board shall be fully capable of handling the data load and
computations that it would be processing and it also shall be able to communicate the data. The board
shall have the ability to write custom software on it. The board shall have input and output pins
available to receive or send data to other components. The communication of the board shall be able to
send the data in the size, signal strength, and distance desired. The board shall fill the following
requirements listed earlier in the document: REQ 2.3.1.5, REQ 2.3.2.1, REQ 2.3.2.2, REQ 2.3.3.5, REQ
2.3.4.1, and REQ 2.3.4.2.
4.2.1.2 Alternatives
The two ways to solve these requirements are either to fabricate a custom circuit board with the desired
processing, storage, and communication capabilities, or to purchase a general purpose board that
encompasses the listed requirements.
Two examples of pre-fabricated boards that could solve the listed requirements are the Intel Edison
board and Adafruit’s FLORA. The Intel Edison7 seen below in Figure 5, is a development kit made for
wearables. It features a dual core CPU, a single core microprocessor, integrated Wi-Fi and Bluetooth,
along with memory and storage.
The Adafruit FLORA9, seen in Figure 6, is an Arduino-compatible microcontroller designed for wearable
projects. It has built in USB support and has a modified version of the Arduino IDE. It offers multiple
compatible boards that include components like GPS, accelerometers, sensors, and capacitive touch10.
27
Figure 6 - Adafruit FLORA Size Comparison
4.2.1.4 Decision
The processing and communication board alternative chosen was a prefabricated board in the form of
the Intel Edison. The Edison offers plenty of computing power and the communication protocol desired
for the design. It is also is better suited for the team’s fitness tracker than the Adafruit FLORA because
the FLORA is aimed toward integrating in fabric and requires multiple partner boards to implement the
design. A customized fabricated board will not be pursued due to budget and time constraints.
4.2.1.5 Implementation
The implementation for the Intel Edison board is intended to provide the main capabilities to process
and transmit the data obtained by the sensors back to the centralized hub. This will be done via Wi-Fi
wireless communication protocol in a LAN setup. With the implementation of the board, features such
as physical design, electrical requirements, and wireless communication standards shall be evaluated in
order to ensure consistent and reliable functionality.
4.2.2.1 Requirements
Defined by both the end-user and the device capabilities, the requirements for a heartbeat sensor
would include size, protocol used, and power requirements. With this, the team can look to optimize
these requirements to meet a middle ground on all aspects in order to reach a decision on what
28
manufacturer to choose and how to implement it. The board shall fill the following requirements listed
earlier in the document: REQ 2.2.1.1, REQ 2.2.2.1, REQ 2.2.2.2, REQ 2.2.2.4, REQ 2.2.5.2, and REQ 2.5.1.
4.2.2.2 Implementation
Depending on the application of the device and location on the body, the implementation of the device
is highly variable. What is known at this point, is that the heart rate monitor needs to be incorporated
into the housing of the device as this component does not function properly unless in direct contact
with an individual's skin.
4.2.2.3 Alternatives
Within the exploration of possible sensors for heart rates, there are two major alternative designs for
tracking the information. These two types include both conductive and optical sensors. The conductive
design uses two exposed metal tabs that contact the skin directly. As the blood pulses through the body
of the user, the conductance between these two tabs fluctuates. It is this fluctuation that is registered as
a heartbeat. As for the design of the optical sensor, light is emitted on the skin. With this light, the
amount received or reflected back to the device is dependent on the transparency of the skin. As the
users’ pulse passes through the area, the transparency of the area changes and a different amount of
light is received by the sensor, thus registering a heart beat on the device. For a product evaluation of
sensors on the market, please refer to the contents herein.
The Polar Heart Rate Sensor11, as seen in Figure 7 below, provides a simple 32-bit heart rate buffer
solution. With multiple interfaces, including USB, Logic-Level serial, and I2C, various types of
communication methods can be used to utilize the device. This expands the options of connectivity
between the sensor and the Intel Edison board. Additionally, dual heart rate processing algorithms are
both averaged together and presented as raw data independently, thus providing redundancy and
accuracy.
Secondly, the features of the TI TIDA-0001112, as seen in Figure 8 below, present a new set of options
with measuring the pulse from the veins in the wrist. This heart rate sensor has dual processing
algorithms with both averaged and raw compilations, much like the Polar heart rate sensors as listed
above.
29
Figure 8 – TI TIDA-00011 Sensor
Finally, the Pulse Sensor SEN-1157413, as seen in Figure 9 below, is uniquely set apart from the previous
options as it is Arduino compatible and operates via a simple optical sensor with amplification and noise
cancellation integrated. This sensor draws 4 a milliamp current at 5 volts. With its size, 0.625" diameter
and 0.125" thick, it could certainly become an advantage when looking to make a compact device.
4.2.2.4 Decision
With the team designing the Intel Edison and Raspberry Pi for communication, a heartbeat sensor has
yet to be determined. Following the efficient and reliable establishment of communication between the
two devices, the sensors will be one of the next components to implement into the design.
4.2.2.5 Implementation
Along with the decision of a heart beat sensor, the implementation is dependent on the size of the
device and its means of communication. What is known at this time is that the team will look to
implement the sensor in a discrete manner that is also placed in a way to properly and consistently track
the data it is intended for.
4.2.3.1 Requirements
When scanning the market for potential step sensors and/or accelerometers, the team will again look to
acquire a component that has a minor footprint in both size and weight without compromising quality
and accuracy. The step tracker is dependent on how the device is oriented on the body, while an
30
accelerometer requires maintenance of axis in order to determine motion direction and speed. The
board shall fill the following requirements listed earlier in the document: REQ 2.2.1.1, REQ 2.2.2.1, REQ
2.2.2.2, REQ 2.2.2.5, REQ 2.2.5.2, and REQ 2.5.1.
4.2.3.2 Alternatives
The alternatives listed below are the result of research of the current market. It is outside of the team’s
scope to design customized sensors.
The SparkFun Triple Axis Accelerometer - ADXL335 sensor14, as seen in Figure 10 below, functions with
three axes, allowing for a measure of vertical movement if desired. With its low noise and power
consumption of 320 µA, its g-force sensing range is an impressive ± 3g. The dimensions of the board
and sensor above are 17.8mmx17.8mm.
Similarly to the SparkFun accelerometer, the STP156 pedometer 15, as seen in Figure 11 below, is a triple
axis MEMS G sensor accelerometer. Its working voltage rests between 2.5 volts and 3.3 volts and an
error range of ±5% per step, which is a significant factor to be considered. The dimensions of the board
and sensor come out to be 11.26mmx41.8mm.
4.2.3.3 Decision
With the team designing the Intel Edison and Raspberry Pi for communication, an accelerometer sensor
has yet to be determined. Following the efficient and reliable establishment of communication between
the two devices, the sensors will be one of the next components to implement into the design.
31
4.2.3.4 Implementation
Depending on the application of the device in coordination with location on the body, the
implementation of the device varies slightly. However, what is known at this point is that the step
sensor needs to be oriented in the correct way when placed on the body. This is so the axis being read of
the sensor directly coordinates with an individual’s direction and rate of motion.
4.3 Battery
Due to the needed mobility of the fitness device, a battery will be the source of power. The subsection
below details the requirements, implementation, alternatives, and decision.
4.3.1 Requirements
As a power source is critical to the function of the devices operations, the criterion for the battery set
forth to do this task shall meet all system requirements. As bench testing and current draw
measurements of individual components have yet to be performed, the true voltage and current
requirements of the device are unknown. However, the ranges of voltage requirements are expected to
fall between 3V and 5V. The battery itself shall be compact, efficient (low emission of heat), and
rechargeable. The board shall fill the following requirements listed earlier in the document: REQ 2.2.1.1,
REQ 2.2.2.1, REQ 2.2.2.2, REQ 2.2.2.3, REQ 2.2.4.4, REQ 2.2.5.1, REQ 2.2.5.2, and REQ 2.2.5.4.
4.3.2 Alternatives
The alternatives when regarding the power source for the wearable technology are laid out in Table 4
below. Within this table there is a brief explanation and specification for content such as capacity,
weight, comparative price, and benefits versus disadvantages.
32
[volume energy density]
4.3.3 Decision
With the team designing the Intel Edison and Raspberry Pi for communication, battery has yet to be
determined. Following the efficient and reliable establishment of communication between the two
devices, the battery will be one of the next components to be implemented into the design. At this time,
the team is looking further into rechargeable Lithium Ion batteries between 3.3 volts and 5 volts to
power the wearable device.
33
4.3.4 Implementation
Prior to procurement of the specific power source selected, much of the implementation is left
dependent on the decision made. However, the battery shall be accessible to be recharged and
interchanged if needed. This power source will then connect directly to the PCB boards and the
corresponding components.
4.4 Software
The section herein discusses the requirements pertaining to the systems software and communication
board.
5. Central Hub
This section outlines the central hub architecture, the hardware, and software design and discusses
many aspects of each subsystem that will be implemented within the central hub. The team looked at
several options of single board computers and decided to use a Raspberry Pi as the central hub.
5.2 Hardware
The following sections discuss the design and decision process for the central hub hardware
components.
5.2.1 Requirements
The central hub is a key component in the system as it shall be capable of creating a secure wireless
network, running a Dynamic Host Configuration Protocol (DHCP) server, running a server with a
database to store data, and send data to an Android app. The hub shall fill the following requirements
listed earlier in the document: REQ 2.2.1.1, REQ 2.2.1.2, REQ 2.2.1.3, REQ 2.2.1.4, REQ 2.2.3.2, and REQ
2.2.3.3.
34
5.2.2 Alternatives
There are several options for how the central hub could be implemented. The team could design their
own circuit board with the required functions, use a computer, or buy smaller boards with certain
functions and connect them together to achieve the functions that are required. Designing a circuit
board for this complex a device is out of the scope of the project. Connecting smaller boards is not a
good choice because it can become expensive to buy them all separately and it would result in a larger
device. These issues result in the best option being a computer. There is no need to use a personal
computer (PC) as this would drive up the price, have more functionality than the project requires, and
increase the size of the device, so it was decided that the hub shall be implemented with a single board
computer. A single board computer is a computer all on one circuit board. It has a CPU, memory, and
I/O ports, but does not have as high specifications and processing power as a PC.
5.2.2.1 Raspberry Pi B+
A Raspberry Pi B+17, as seen in Figure 12 below, is a single board computer that is capable of acting as a
central hub. The Raspberry Pi is a small computer that typically runs a version of Linux called Raspbian,
but can run other operating systems. A Raspberry Pi uses a 700 MHz Low Power ARM1176JZFS
Applications Processor CPU and has 512MB of SDRAM. It has 40 pins for connecting inputs and outputs
as well as 4 USB 2.0 ports, but in this application they may not need to be used. To give the Raspberry Pi
Wi-Fi capabilities, a USB Wi-Fi module would need to be connected. Since it runs Linux, it is fully capable
of creating a Wi-Fi network and running a server.
Figure 12 – Raspberry Pi B+
35
Figure 13 – BeagleBone Black
5.2.4 Decision
The team decided to use a Raspberry Pi B+ as the central hub. The Raspberry Pi has been around longer
and is more widely used so it has a much wider community and reference material. While the
BeagleBone may be better in terms of processing power, the Raspberry Pi is slightly cheaper and still has
the power that the team needs. Not only is the base price of the Raspberry Pi cheaper than the
BeagleBone, both would need a USB Wi-Fi module and to get the same amount of storage as the
Raspberry Pi, the BeagleBone would need an SD card as well. There are no exact numbers for the power
consumption of the Raspberry Pi available like the BeagleBone, but generally the reported numbers are
less than the BeagleBone. All of these factors combined with the fact that the team had access to a
Raspberry Pi to do some testing made it the better choice.19
36
5.2.5 Implementation
A Raspberry Pi B+ has been purchased and some initial testing was completed to make sure that it could
set up a server as further explained in section 9.
5.3 Software
The central hub will need to run software developed by the team to achieve the desired functionality. A
wireless network will need to be created with the central hub as the access point. The team will need to
write software on the hub so that when it turns on, it creates a secure network and will allow other
devices to connect to it and start a server.
5.3.1 Server
The hub will need to run a server for the fitness devices to send data to and for the mobile app to
connect and receive data from. To achieve these connections, the hub will need to run a database on
the server and use a scripting language such as Personal Home Page: Hypertext Preprocessor (PHP) or
JavaScript to handle receiving and serving data to and from clients. There is server software available for
free that come equipped with all of these functions, such as a Linux, Apache, MySQL, and PHP stack
(LAMP). Alternatively, Mongo DB and Node.JS could be used. As such, the team will not have to write
code to make a server, but will have to develop code to make the server perform as desired.
The other option the team has is to define a transmission protocol to get a better balance between the
two. UDP could be used with part of the packet defining an acknowledgement and implementing retries
if an acknowledgment is not received, but this may not be in the scope of the project. The team has not
decided yet what route to go or whether defining a protocol is out of the scope of the project.
37
6. End-User Application
For a description of the details of the end-user Android application and how it will be integrated into the
system, please refer to the content below.
6.1.1 Overview
This application is designed to be used by the head of the practice session whether it be the coach,
fitness trainer, or a professor. It will be the final presentation of all data and status from the athletes
wearing the fitness devices. The application will provide easy navigation between stats and the
biometrics the fitness trackers are collecting. This Android application will be available to use on any
Android device, primarily targeting tablets. The decision to go with Android as the desired application
platform can be viewed in section 3.3 End-User Application Platform.
6.1.2 Functionality
The main function of the application is to provide a user interface to the data being recorded in the
fitness devices. The application will be able to be filtered in two ways. First, the whole group can be
viewed with as much data presented as allowed in the space. Team metrics will be available in this view
as well. The other way the data can be viewed is looking at an individual. This will show more metrics on
each player that is not logical to group with the team metrics such as past heart rate levels, step rates,
and trailed location.
6.1.3 Inputs
The inputs to the system will be the user’s touch and the data from the central hub as the application
updates. The user will have complete control of the application through the touch screen on the Android
device. They will be able to navigate the system and they will be able to manually request for updated
data from the central hub. The central hub will also send an input to the application via Wi-Fi. These will
be provided in the form of data packets that the application will be able to decode and use to display
updated information.
6.1.4 Outputs
The system’s output will be primarily in the form of what is seen on the screen of the Android device.
The two ways this data will be shown is as a team and individual data, this is detailed in 6.1.2
Functionality. The team has plans to make it possible to send an individual’s or the team’s data out in
the form of a PDF. This PDF could either be sent via email inside the app or would just be saved to the
Android device, where it could be sent from the host’s Android email application.
38
6.1.5 Software Updates
If there needs to be updates to the application they will be done as quickly as possible to fix the
problem. This will be done by uploading a patch or update to the Google Play Store, where the app was
originally downloaded from. The user will have to be connected to the internet via Wi-Fi or cell service in
order to access these updates.
39
7.1.1.2.1 Chest Mounted
As identified in the consumer survey, five parties identified the concept of a chest mounted wearable as
the most desired fit. With a chest mounted design, as seen in Figure 14, the team would make an effort
to minimize the hindrance of the device as the chest is an area that athletes would prefer to not be
constricted. This design would need to keep in mind all types of individuals and to be a one-size fits-all.
40
Figure 16 – Wrist-Mounted Concept View of Face
41
Figure 18 – Wrist-Mounted Concept Side View of Wrist Strap
42
7.1.2 Material Selection
In coordination of minimizing weight and maximizing comfort, the design is to mainly be constructed of
plastic. Taking advantage of the 3D plastic printer available, an ABS plastic will be used to build the main
body of the wrist-mounted device. The design will also take into account the necessary void space for
electronic components and buttons. These buttons, as shown in the right-side view of the device above,
will control features such as ON/OFF and mode select. As far as the interaction with the user, LEDs are
considered to be arranged in a way to provide information such as heart beat or speed. In short, plastic
will be used from the printer available, with minimal alternative materials in order to properly house the
electronics and operate the device.
8.2 Deliverables
The team will be providing a wide array of deliverables through the project including reports,
presentations, a website and prototypes. A breakdown of what will be provided and the known dates
that will be made available are located in Table 5.
43
management, and budget.
Detailed Business Dec 8, 2014 This document is made in conjunction with senior design in
Plan BUS-357 to outline a business and financial plan as if this
project were to become a profitable business.
Presentation 3 TBD The third presentation of the project giving a status update.
Presentation 4 TBD The final in-class presentation of the project.
Final Report TBD Final report of the project, which will include portions of the
PPFS, design details, progress details, and other updates.
Final Prototype May 9, 2015 The deliverable prototype that will be on display on Senior
Design Night.
Final Presentation May 9, 2015 A presentation given on Senior Design Night about the overall
project.
9. Testing
This section describes some of the completed testing with the processors, and how the team will
approach further testing of the device components.
9.1.1 Raspberry Pi
The Raspberry Pi was used to host a server and run a database. The server that was put on the
Pi ran by was an Apache webserver. An Apache HTTP server is the most common webserver software
used. This webserver ran a MySQL database that was controlled via the web using phpMyAdmin
44
software. This software provided a GUI that made it possible to set up the database in MySQL. The
Raspberry Pi's server hosted a webpage that gave the ability to manually enter data into the database
and displayed all of the data entries. The webpage was written in the PHP and HTML. These languages
can interact easily and they are widely used in web-based applications.
The testing results were encouraging as the Raspberry Pi was set-up as a server and database
easily. This proves that a Raspberry Pi will be a good solution for our central hub. The Raspberry Pi also
allows for external storage expansion which will most likely be needed for the database.
This test gave the team some experience working with the Edison and figuring out what its capabilities
are. It showed that the Edison can send data to a server easily once it is set up properly, thus making it a
feasible solution for the wearable device. The Edison can also be easily programmed by a computer and
send data to a serial monitor for debugging purposes. It will also automatically run the code when it
boots, so it does not have to be reprogrammed every time it starts, which means a coach can simply
turn on the devices and hand them out.
45
9.2.3 Send Data from Database to Mobile App
After the team has a functioning app, there shall be a test that proves that data sent from the central
hub can be received by the mobile app. Once this is proven the team member that is designing the
application can move forward with manipulating the data to be aesthetically pleasing and easy to
understand.
46
10.2.1 Industry Background and Overview
The sophistication of data compilation and analysis has certainly seen major growth in the past century
as electronics and automation have quickly dominated a large spectrum of markets. Specifically, the
market of athletics and training has shown their need for technological advancements in order to better
understand biomechanics and conditioning of athletes and trainees. That being said, BioBit looks to fill a
void in this market by allowing a team or training group to compile and analyze data as both a single unit
and individually.
BioBit will be marketed towards two major customer groups, first being trainers and coaches who could
use our product in their practice and training sessions. The second major customer group the field
academic research.
47
10.4 Significant Trends
Currently, the wearable technology market has quickly grown into an application for a single user in
order to monitor themselves for both workouts and leisure. Current products which fall under the
classification would include, but are not limited to, smart watches and sports bands. The increasing
market value has shown that there has been significant growth in the past decade as the retail market
value has increased ten-fold in less than four years21. Because of this, users have shown that they are
willing to pay high prices for devices similar to BioBit, so the value and market need for an item like
BioBit certainly exists, and this is where BioBit looks to thrive and capitalize within the market.
48
through the year 2025, upon which, the market will see more of a plateau and stabilize itself with price
points and growth.
10.5.2.1 Operational
The operational goal of the company is to bring an ethic of teamwork with efficiency, sustainability,
integrity, stewardship, and caring to the customers who will use the product. The product shall be
designed in such a way to provide maximized quality and minimized cost.
10.5.2.2 Financial
The financial goal of the company is to use the first generation design to make enough profit to repay
both the startup loan and reinvest in the company’s future. BioBit will be financially aggressive when it
comes to paying off its start-up debt. This will help reduce the risk for the company and the employees
in the unfortunate circumstance of economic instability. Once BioBit has its debts taken care of and
starts seeing a profit, the company plans to expand the brand and potentially increase the product
diversity but this will be done in financially responsible means so as to stick to the company’s value of
sustainability.
49
financial responsibility for the company’s success due to their own monetary investment in the
company. Another strength is the product itself. The product will be of the highest quality while
maintaining a low cost, which creates a reputation in the marketplace of a well-engineered product.
50
range products. On the other hand, the company is planning to provide lower prices than competitors
and offer the best value products to the market.
10.7.2 Focus
The focus of the company is creating a quality product with a low cost. Currently Polar, BioBit’s main
competitor in this market, provides an expensive solution for team-oriented fitness tracking. The
company hopes to find a niche in this price range gap while providing a quality product. Most
importantly, the company will focus on marketing to build trust with the customers and continue
competing in the market. Once the company has a returning customer base it can use this leverage to
get into other markets and build the BioBit brand.
The baseline package that will be available on the market will include 15 fitness tracking devices, 1
central hub, and access to the mobile application. This baseline package is customizable based on the
number of devices the customer desires.
10.8.2 Uniqueness
BioBit will differentiate our product from our competitors’ by creating a package of group-oriented
fitness trackers compared to personal fitness trackers. Most fitness trackers currently in the market are
for personal use only and link up to an app on the person’s phone when there is a Bluetooth connection.
Our system will do everything a personal fitness device can do and have the advantage of evaluating the
grouped data in one location. BioBit also allows the user to not be required to be within communication
distance of a phone, as many athletes typically do not have their phone on them when they train.
51
10.8.4 Warranties and Guarantees
BioBit will come with a limited warranty. This warranty will cover any issue that arises with the product
that is determined not to be a customer related issue but is an issue with how the product was
designed, fabricated, or assembled. This warranty will not account for any abuse of the product or if it
becomes dysfunctional from being used outside of the directed method. Customers will be given
updates to the software of the tracking device and frequent updates to BioBit’s tracking app. If there is a
design flaw in the product, BioBit will guarantee a quick product replacement or a full refund.
52
10.9.1.3 Other Significant Customer Characteristics
The significant customer characteristic of BioBit’s product is that the unit can be used in a group setting,
thus connecting multiple customers to the same network. This provides the opportunity for a cohesive
and collaborative environment giving an advantage for easily comparing and monitoring multiple
individuals on a single interface.
This identified plan within BioBit correlates with how other similar companies have entered the market.
As personal fitness trackers did not catch on until they were well established in the market, the majority
of sales took off eight months after the device had been introduced.24
10.9.3.1 Message
The primary message that BioBit wishes to deliver is simply its vision and purpose. BioBit wants to be
known as an innovative company that is delivering the next-generation of fitness devices that center
around teams. Quality and integrity are a part of that message and help convey a sense of trust in both
the company and its products.
53
10.9.3.2 Media
In the first year of the product being on the market BioBit use online and social media as its primary
means of promotion. This is best option due to budget restrictions, as they tend to be cheaper than
print or TV advertising and will be one of the best ways to reach out to the target market. Further into
the BioBit brand, when the budget for marketing has increased, the team will explore any and all
options of advertising in order to expand BioBit’s reach.
10.9.3.3 Budget
As explained in detail below within the financial cash flow section, BioBit views the advertising and
promotion of both the company and its product line very seriously. This is due to the fact that
establishing a presence and maintaining a good reputation among competitors is pivotal to a company’s
success, especially upon the startup of a product line. Because of this opinion, BioBit has chosen to allot
$100,000 annually towards the marketing and advertisement of the company and its products. This
equates to 16% of the company’s total annual fixed operating costs.
10.9.4 Pricing
The pricing for a single unit is dependent on the quantity the company is able to sell annually as well as
the cost of materials and operation. Because of this BioBit intends on offering a single unit for sale for
$13,949.14 the first year, $5,954.17 the second year, and $3,155.94 the third year. It is at these price
points that the company must sell at a minimum. However, because similar devices on the market range
from $14,300 to $16,100 BioBit will look to sell at a maximized price point which that offers the best
value and a lower price than any competitor. With the minimal sale price of a BioBit unit in the first year
being 3% lower than any other competitor, BioBit is confident that they can sell at this price into years
two and three, thus maximizing profit margins while still offering the cheapest price to consumers
compared to direct competitors.
54
10.10 Competitive Analysis
BioBit will have to remain competitive in a rapidly growing market in order to create a sustainable
business. The subsections below will detail who BioBit’s competitors are and what companies have the
capabilities to enter the market and become a competitor.
10.10.1.1 Polar
3Polar has a product called ‘Team2 Pro’ which falls under the necessary classifications in order to
compete directly with our product. This means it is a wearable tracking device that is team-oriented.
However, the price and the lack of variety tracking methods are what hold this product back. The cost of
a single unit is approximately $17,200; which includes a hub, computer interface, and numerous
trackers. In order to compete with Polar, BioBit looks to provide a better value by lower price and
increasing the variety of tracking sensors.
10.10.1.2 LUMOlift
LUMO has a product currently on the market named the LUMOlift. This is an individual-oriented device
which helps aid in tips for posture and muscle energy longevity. The LUMOlift provides competition to
the BioBit through its unique tracking and data gathering. However, this device is for an individual and
thus is not team-oriented. The market price for a single LUMOlift is $210.00.
10.10.1.3 Mayfonk
Mayfonk is a vertical leap tracker with a direct focus towards athletes involved in high jump, basketball,
and volleyball. The Mayfonk competes on the same level with BioBit through its intuitive design on a
mobile application supported through iOS. This device is intended for a single person and is worn on the
hip which tracks only vertical leap. The base price for a single unit and its accompanying mobile
application is $180.00.
10.10.2.1 FitBit
FitBit already is a leader in personal fitness tracking wearables. If this company looks to enter the market
of team oriented devices, it could pose as a threat to BioBit. Fitbit has shown it is very detailed oriented
and efficient in its current market and because of this, may look for additional avenues to increase their
footprint in the fitness tracking market.
10.10.2.2 Nike
Nike also has gotten into the personal tracking systems and is currently in direct competition with the
FitBit. If one of the two companies should choose to explore the production of team-oriented devices,
the chances of the other company to follow would be very high. Nike currently dominates its markets
through strong sales and marketing teams while following through on customer service. If Nike chooses
to join, it could also implement its current products, such as shoes, into its design and essentially double
55
dip in the sales of a device and apparel. If this is the case, it could pose as a challenge for BioBit to
compete on sales and marketing.
10.10.2.3 Samsung
Finally, Samsung may also be interested in similar markets as it has started to include sensors in its
products, such as their smartphones. Samsung could potentially pose as a competitor as it would more
than likely be very strong in its mobile application and intuitive design. While this is an aesthetic
attribute it still hold weight as it bridges the gap between the technology and the user, allowing for ease
of use and efficiency.
In his spare time, Nick is also working on side projects involving mechanical and electrical repairs for
both the Calvin and local communities.
Brad enjoys staying active through playing sports such as soccer, tennis, golf, going hiking and going to
the gym. He also interested in audio projects and music production.
56
programming microcontrollers and Android apps, and reducing power consumption on both
microcontrollers and smartphones. He understands the benefit of being able to track players on sports
teams through playing on sports teams all the way through elementary and high school in Chiang Mai,
Thailand including Varsity Basketball and Volleyball.
In his spare time Carl enjoys pursuing the outdoors through rock climbing and backpacking as well as all
things audio from recording to building guitar amps and effects pedals.
Jessica is currently working as a Student Office Assistance at the Engineering Department. She organized
documents, update the engineering website, help plan the department events, and assist professors
when they need a hand. She is also a student leader for Calvin’s Women and Engineering club. She plans
social events and study groups for the women engineers.
In her spare time, Jessica enjoys being active through going to the gym with friends, rock climbing,
camping. She also likes to watch TV shows such as Castle, Bones.
10.11.2.1 VP of Finance
With the need of a Vice President of Finance, the company would look to stabilize their business
financially and look for consistent growth in an ethical and strategic manner. An individual who is a
Certified Public Accountant (CPA) and a Master of Business Administration (MBA) would best fit the
requirements the company is looking for in this position.
10.11.2.2 VP of Marketing
In this role, the Vice President of Marketing would take on a role to drive the market acceptance and
reputability through the company’s image and its products. An individual who has had past experience
in marketing technological devices and has received a Master’s in Business Marketing would best fit this
role in the company.
10.11.2.3 VP of Sales
When looking to fill the role of Vice President of Sales, the company would look for an individual who
can maintain the image of the company through managing a sales division and its respective
57
geographical regions. The company would prefer to have an individual which has a minimum of 15 years
of experience in a direct or related market.
10.11.3 Operations
58
Figure 20 - Overview of Company Structure (dotted line to show initial organization)
59
10.2.2 Cash Flow Statement (Quarterly, 3 years)
The cash flow statement is an important document because it shows how the cash moves through the
company. This statement for the first three years can be seen in Table 7 and it is expanded into each
quarter in Table 8 and it should be noted that the company ends with a positive cash balance at the end
of each year. The cash flow statement also lists the loan information; including receiving the loan and
the payoff plan. As the company ends each year with a positive cash balance, BioBit LLC will pay off the
loan in the second year split into four payments to be paid out each quarter. As the note under Table 2
states, there are no changes in assets and liabilities other than cash, notes payable, and equipment so a
balance sheet is not needed.
60
Table 9 – Cash Flow for First Three Years (Quarterly)
61
10.4 Ratio Analysis
The ratio analysis for the first three years of business can be seen below in Table 10. It should be noted
that the profit margin ranges from 13% to 43%, which exceeds the minimum of 10% as budgeted each
year. With these numbers comparable to market, the 13% is far too low; however, 43% is a great margin
of value. This means that to improve profits, costs would need to be reduced. It should also be noted
62
that the net asset turnover decreases after years two because the company gains assets over the first
three years so even though the revenue is increasing, the ratio decreases.
63
11.1.3 Milestones
The major milestones for the fall semester in the project are shown below.
Project Selection
Project Proposal and Approval
September 15- PPFS Outline
October 15- First Oral Presentation
October 17- Choose communication: Wi-Fi
October 22- Project website
November 2 - Chose Components: Intel Edison and Raspberry Pi
November 10- PPFS Draft
November 12- Bought Intel Edison and Raspberry Pi
December1- Second Oral Presentation
December 4- Tested processors and communication
December 8- PPFS
11.2 Schedule
64
11.4 Method of Approach
This section is to describe the design methodology, the research techniques, team communication, and
the specific design norms that have influenced the team’s design decisions.
12. Conclusions
This section will discuss the feasibility of the project looking forward, along with a listing of lessons
learned along the way and identifying remaining issues. The document will end by giving credit to those
who have helped the team during this project.
65
One concern with the project looking forward is the sensor network. The team's industrial consultant,
Eric Walstra of Gentex Corporation, warned that this may be the most challenging portion of the project.
He suggested that this not be overlooked as it easily could be when trying to schedule work for the
future. The team plans on making this priority number one during the spring semester to make sure we
give ourselves enough time to fully test and integrate the sensors into the design.
Another technical concern for the team is how to integrate a mobile app into the design. No one on the
team has created a sophisticated mobile app. First and foremost the team needs to develop a fully
functional app and then focus on the aesthetics of the app as if the team were going to release this
application on major app store.
A second learned lesson for the team is the need for weekly meetings. These meetings are important to
touch base, evaluate the current status of the project and to look forward at the near and distant future
goals. This will become increasingly important in the second half of the project as the team will be
breaking apart and working on their own portions of the design. Each teammate will have to give
detailed updates of their progress and communicate with others in the group to successfully integrate
their portion into the system.
The large role of communication within a project of this size is another lesson that the team has
realized. The team has been warned by plenty of professional mentors that communication is key in a
group project. But the best way to learn this is by actually being a part of a large project. Communication
will be key in the rest of the project when the individual components come together to create the whole
working system.
66
12.3 Credits and Acknowledgements
The team would not be as far as we are if it weren't those around us. We would like to thank those
people. First, Professor Mark Michmerhuizen as the team's advisor. He has given us plenty of feedback
from the project design, to formal documents, along with words of advice and encouragement. We
would also like to thank the three other professors, Professor David Wunder, Professor Jeremy
VanAntwerp and Professor Ned Nielsen, who lead the Senior Design class along with Professor
Michmerhuizen. They are quick to help any team that approaches them and have given their respective
lectures that helps teams to grow and become more professional. Team 10 would also like to thank Eric
Walstra for being the team's industrial consultant and providing an outside professional viewpoint to
the project. Finally, we'd like to thank the Calvin College and Grand Rapids Christian High School athletic
departments along with the Calvin College Kinesiology department Professors for their suggestions and
their willingness to help the team’s project development.
The team would also like to thank our friends and family for their continued and unconditional support.
They are the ones that help us get through this tried and testing time in our academic lives and we hope
we can make them proud through our work.
67
13. References
1
Comer, Douglas E. Internetworking with TCP/IP: Vol. I. Upper Saddle River, NJ: Pearson Prentice Hall, 2006. Print.
2
"Welcome to Bluetooth Technology 101." Fast Facts. Bluetooth Technology Website, n.d. Web. 14 Oct. 2014.
3
Lee, Jin-Shyan, Yu-Wei Su, and Chung-Chou Shen. "A Comparative Study of Wireless Protocols- Bluetooth, UWB,
ZigBee, and Wi-Fi." The 33rd Annual Conference of the IEEE Industrial Electronics Society (IECON)(2007): 46-51. A
Comparative Study of Wireless Protocols- Bluetooth, UWB, ZigBee, and Wi-Fi. Acedemia.edu. Web. 18 Oct. 2014.
4
Lee, Jin-Shyan, Yu-Wei Su, and Chung-Chou Shen. "A Comparative Study of Wireless Protocols- Bluetooth, UWB,
ZigBee, and Wi-Fi." The 33rd Annual Conference of the IEEE Industrial Electronics Society (IECON)(2007): 46-51. A
Comparative Study of Wireless Protocols- Bluetooth, UWB, ZigBee, and Wi-Fi. Acedemia.edu. Web. 18 Oct. 2014.
5
Evans, Jon. "Android vs. IOS Development: Fight!" TechCrunch. N.p., 16 Nov. 2013. Web. 04 Dec. 2014.
6
Henneke, Cameron. "Android vs. IOS: Comparing the Development Process of the GQueues Mobile Apps."
GQueues. N.p., 29 July 2013. Web. 05 Dec. 2014.
7
"Intel® Edison Module." Intel. N.p., n.d. Web. 25 Oct. 2014. <http://www.intel.com/content/www/us/en/do-it-
yourself/edison.html>.
8
"Intel® Edison." SparkFun Electronics. N.p., n.d. Web. 25 Oct. 2014.
<https://www.sparkfun.com/products/13024>.
9
"FLORA - Wearable Electronic Platform: Arduino-compatible." Adafruit Industries. N.p., n.d. Web. 05 Nov. 2014.
<http://www.adafruit.com/product/659>.
10
"Adafruit Learning System." Adafruit I. N.p., n.d. Web. 05 Nov. 2014.
<https://learn.adafruit.com/category/flora>.
11
"Polar Heart Rate Monitor Interface." - SEN-08661. N.p., n.d. Web. 08 Dec. 2014.
12
"Optical Heart Rate Monitor Reference Design with BLE Connectivity." - TIDA-00011. N.p., n.d. Web. 08 Dec.
2014.
13
"Pulse Sensor." - SEN-11574. N.p., n.d. Web. 08 Dec. 2014.
14
"SparkFun Triple Axis Accelerometer Breakout - ADXL335." - SEN-09269. N.p., n.d. Web. 08 Dec. 2014.
15
"STP156 Embedded 3D Pedometer Module by Nicerf." Tindie. N.p., n.d. Web. 08 Dec. 2014.
16
"Intel® Edison Module." Intel. N.p., n.d. Web. 25 Oct. 2014. <http://www.intel.com/content/www/us/en/do-it-
yourself/edison.html>.
17
"Raspberry Pi - Model B+." Sparkfun. N.p., n.d. Web. 06 Dec. 2014.
18
"Beaglebone Black - Rev C." Sparkfun. N.p., n.d. Web. 06 Dec. 2014.
<https://www.sparkfun.com/products/12857>.
19
Leonard, Michael. "How to Choose the Right Platform: Raspberry Pi or BeagleBone Black?" MAKE. N.p., 25 Feb.
2014. Web. 25 Oct. 2014.
20
Comer, Douglas E. Internetworking with TCP/IP: Vol. I. Upper Saddle River, NJ: Pearson Prentice Hall, 2006. Print.
21
"Generator Research." Share. N.p., n.d. Web. 01 Nov. 2014. http://www.generatorresearch.com/share/1vcgrss
22
T., An Ihs Whitepaper, and September 20. Wearable Technology – Market Assessment (n.d.): n. pag. Web.
http://www.ihs.com/pdfs/Wearable-Technology-sep-2013.pdf
23
"Generator Research." Share. N.p., n.d. Web. 01 Nov. 2014. http://www.generatorresearch.com/share/1vcgrss
24
"Generator Research." Share. N.p., n.d. Web. 01 Nov. 2014. http://www.generatorresearch.com/share/1vcgrss
25
"Generator Research." Share. N.p., n.d. Web. 01 Nov. 2014. http://www.generatorresearch.com/share/1vcgrss
26
Lawrence, Beth. "LLC Basics." Nolo.com. Web. 31 Oct. 2014. http://www.nolo.com/legal-encyclopedia/llc-basics-
30163.html
68