1. Executive Summary - WordPress.com

sunglowmaizeMobile - Wireless

Dec 10, 2013 (3 years and 7 months ago)

107 views

Product Proposal

Project CarFi






























Ma
rch 21, 2012

Team Formal Report Project


Team Omega

Sam Crooks

Bach Dao

Ryan Lear

Shailza Sharma

Athanasios Spiropoulos


Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
2

Document Control


Version Control


Version Number

Date

Author

Description of
Change

0.
0
1


䑲慦琠t

〳⼰㌯30ㄲ


p⸠䍲o潫s

䥮ftial⁤牡 琠tf⁰牯灯sal⁤潣畭敮琠


䍡Cci

〮〲0


䑲慦t


p⸠䍲o潫s

䍬敡湥d⁵ 灬慮 lay潵t

〮〳0


䑲慦t


p⸠䍲o潫s

A摤敤⁥ e
c畴uv攠e畭m慲yI⁣潮cl畳i潮

〮〴0
-

䑲慦t

〳⼱㠯80ㄲ

p⸠䍲o潫s

䥮f潲灯o慴敤⁕ ⁤ 慧r慭sⰠIys瑥t⁤ a杲慭s

〮〵0


䑲慦t

〳⼱㠯80ㄲ

p⹃.潯ks

A摤敤⁃慲ai l潧o

〮〶0


䑲慦t

〳⼱㠯80ㄲ

p⹃.潯ks

A摤敤 ilp i湴敲e慣攠
m潣k
-
異u

ㄮ〠


剥view†

<摡瑥>†

<湡m放


ㄮ〠


Ap灲pv敤

<摡瑥>

<湡m放



ㄮㄠ


剥view†


<摡瑥>†

<湡m放




ㄮㄠ


Ap灲pv敤


<摡瑥>

<湡m放





Pro
ject

CarFi
Team

The individuals whose names appear
below authored and contributed to this proposal.

Name

Title

Sam Crooks

Project Engineer

Bach Dao

Project Engineer

Ryan Lear

Project Engineer

Shailza Sharma

Project Engineer

Athanasios Spiropoulos

Project Engineer





Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
3

Contents



1. EXECUTIVE SUMMARY

................................
................................
...........................
4

2. INTRODUCTION

................................
................................
................................
.......
5

3. PRODUCT DESCRIPTI
ON AND USE CASES

................................
.........................
7

4. SYSTEM COMPONENTS

................................
................................
.........................
9

5. ASSUMPTIONS DEPEN
DENCIES AND RISKS

................................
......................
10

6. ALPHA SYSTEM DEVE
LOPMENT PLAN

................................
...............................
11

7. RECOMMENDATIONS

................................
................................
.............................
12

8. APPENDIX A


DIAGRAMS

................................
................................
.....................
13


Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
4


1.

Executive Summary

This document is a proposal for a new
product that

fills a gap in functionality present in modern
vehicles. New
vehicles come with sophisticated entertainment systems and on
-
board diagnostic
capabilities, but these features are not easily accessible to the consumer and are difficult and
tedious to use through existing products on the market. We propose to design a
nd market the
CarFi system which is a combination of a base unit and OBD
-
II remote unit which connect to the
vehicle, a web service provided by Omega Corporation as part of the product, as a variety of
product interfaces including PC, mobile phone and web
interfaces.


1.1

Audience

The intended audience is the
business stakeholders and the technical teams responsible for
development and implementation the proposed system, components and products.

Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
5


2.

Introduction

2.1

Problem: OBD
-
II Data Access


V
ehicles sold in
the United States have been required
by

the EPA to be equipped with the OBD
-
II
system since 1996. This requirement was updated in 2008 and all cars sold in the Unite
d

States
are now also required to support the CAN protocol running on the OBD
-
II bus
, in a
ddition to

the
earlier manufacturer proprietary prot
ocols which also run in some ve
hi
c
le.

The OBD
-
II and
CANBUS systems in modern vehicle provide access to a wealth of diagnostic and operations data
about the systems running in the vehicle. A 2012 model y
ear car may have as many as 30+
separate embedded
computers that

operate various automotive systems such as the engine, the
windows, the transmission and many others. It is essential to read the data from these computer
systems to diagnose problems with a

modern automobile.


The computer revolution in the automotive industry has been very beneficial on many fronts, and
has been the primary means by which vehicles have been made more fuel
-
efficient, more reliable
and longer lasting, with lower pollution emi
ssions over the past 35 years since the computerization
of automobiles began. This computer revolution has not been without its downsides. The
increasing use of computing technology critical to operating vehicle systems has made it much
more difficult fo
r the regular person to diagnose and repair a vehicle.


Automobile repair is not that difficult. It usually involves identifying the problem,
and then

replacing
failed,
worn
-
out

or damaged parts with new ones. Many of these parts are easily replaced wi
th
inexpensive
hand tools
, and some require no tools at all. For a person willing to get their hands
dirty and spend a little bit of time learning how a car works, there is a significant amount of money
that they can save by diagnosing vehicle problems an
d replacing the parts themselves.


OBD
-
II and CANBUS codes may easily be read by attaching a device to the bus connector in the
vehicle (required to be within 2 feet of the steering wheel). A person must have a
tool that

connects
to this special bus conne
ctor to read the data. They also must then understand what the OBD
-
II
and CAN codes mean, and what could be causing those codes to be registered by the vehicle.
In
the recent past,

lack of
access to the special tools as well as the knowledge to understan
d the
codes put automotive diagnostics of modern cars out of the reach of the average person.


The tools and information to read and understand vehicle diagnostic information is no longer out of
reach of the average person.

OBD
-
II and CANBUS are standard
s, developed and published by the
standards

body related to the automotive industry, the Society of Automotive Engineers (SAE).
All
O
BD
-
II and CANBUS codes and asso
ciated descriptions
are available to SAE members for a fee.
Some people have made the data
in the standard available publicly. The OBD
-
II and CAN codes
Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
6

and descriptions
can be accessed from hundreds of websites by anyone with an Internet
connection and a web browser. In recent years, Bluetooth OBD
-
II bus adapters
have been sold in
the
marketpl
ace, which

plug into the OBD
-
II connector under the steering wheel and make the data
available to any computing device which pairs to the Bluetooth adapter
.
Bluetooth
OBD
-
II adapters
range in price from $12
-

$50.


Mobile smart phones are nothing more th
an a computer with touchscreen
interfaces
, a variety of
data connection options and
faster processors and more storage than prior mobile phones. Smart
phones have taken over the mobile phone market.

There are essentially 2 dominant mobile
platforms toda
y: Apple i
OS and Google Android. On the

Apple
ITunes

App Store, there are 45
apps that

have OBD
-
II functionality, ranging in price from free to $50. On the Android Market, there
are more than 191 different
apps that

have OBD
-
II functionality.


When y
ou compare the price of a Bluetooth OBD
-
II code reader + smartphone app or computer
application to read the vehicle codes to the cost of a dedicated vehicle scan tool in the late 1990s
(about $3000), you can see that there is no longer a cost and technolog
y barrier for the average
person to diagnose and repair modern automobiles.


2.2

Problem: Tedious Vehicle Entertainment System
Media Management


Modern automobiles are being equipped with sophisticated audio and video entertainment
systems
that allow the consu
mer to connect their mobile devices to the vehicle to play media

content
through the
on
-
board

entertainment system. The media formats many entertainment systems
support include CD, DVD, SD card, USB
-
attached storage, mobile devices attached via USB, Apple

IPod

interface, and Bluetooth as well as local storage embedded within the entertainment system.
Vehicle occupants may also tether their mobile devices to the vehicle to access the mobile device
address book and place voice calls using the mobile device.


One of the issues with these entertainment systems is that it takes significant time to transfer media
to their internal storage
and that it is a very tedious, manual process by the vehicle owner to
transfer and maintain a copy of a set of media files on

the vehicle.



Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
7


3.

Product Description

and Use Cases

3.1

Product Description


The project team believes that there is an opportunity for marketing a
product that

combines a
number of existing technologies in a single
package that

interface
s

the vehicle to exte
rnal systems.
The primary issue is that each discrete system in an automobile has a unique, specialized interface
,
and that with one exception (Bluetooth), these interfaces are wired, not wireless.


We propose the design and market, CarFi, a product
tha
t

network
-
enables a vehicle.

The
consumer will purchase the CarFi system and attach the base unit to the vehicle via USB or
Bluetooth
. The base unit will contain a small rechargeable
battery that

allows the base unit to be
powered even if all input power

to the base unit is off (such as when the vehicle is sitting in the
garage, turned off overnight). The battery will provide enough battery life for 6 hours of active
operation (radios transmitting and receiving data) and 168 hours of sleep time without a
ny
additional power input. An OBD
-
II remote reader will be connected to the vehicle’s OBD
-
II port,
typically located under the steering wheel and left there permanently. The OBD
-
II remote unit will
be powered by the OBD
-
II port when the vehicle is turned
on and running.


3.2

Use Case: Vehicle Diagnostics


The OBD
-
II remote will be tethered to the base unit as a Bluetooth client for data exchange. When
the vehicle is running, the base unit will constantly monitor and log data about the vehicle’s
operating para
meters to make them available for historical analysis. Additionally, the base unit will
keep a log of any OBD
-
II or CANBUS codes which are triggered during vehicle operation.


Once configured, the CarFi base unit will join its home
Wi
-
Fi

network when in r
ange
.
The consumer
will have the option of using any of several clients
to connect to the CarFi base unit over the
wireless network, including iOS, Windows and a basic web interface. Using these clients on their
computer or smartphone, the consumer can l
ook at active OBD
-
II fault codes as well as historical
data about the vehicle operating parameters. The software client and web interface will query a
web service that

returns information about the OBD
-
II fault codes and suggest possible courses of
action

to further diagnose the issue.

3.3

Use Case: Vehicle On
-
board Media File Management


The CarFi base unit will be connected to the vehicle entertainment system either via USB or
Bluetooth tethering. The storage on the CarFi base unit will appear to the enter
tainment system as
Bluetooth
-
attached or USB
-
attached media storage, just as a mobile device or USB flash stick does.

The CarFi base unit has USB ports and SD card slots to enable the consumer to attach flash
Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
8

storage to the base unit ranging from 2GB


2T
B, and to replace and expand
the storage

as
he or
she

require
s
.

The CarFi base unit will join a configured
Wi
-
Fi

SSID when in range, and will be
accessible over the wireless network to other systems on the same wireless network. This
capability enables a

software client running on the consumer’s phone or computer to keep the set
of media files in the CarFi base unit in sync with a set media files on a mobile device or with a
personal computer.


3.4

Use Case: Vehicle Reporting

and Notifications

Exposure of
t
he CarFi

base unit through an open API allows clients with rich functionality to be
written by 3
rd

party developers. There are many applications that would be enabled by such an
API, including:



Automatic

tracking and reporting of mileage and fuel
-
efficie
ncy



Automated

reminders of vehicle service



Predictive

notification of impending failures based upon historical data about the vehicle
operating parameters and comparison to data warehouse information of other similar
vehicles


3.5

Use Case: OEM Vehicle Data Ac
quisition

If we can develop the system and bring it to market quickly enough, there is opportunity to work
directly with the OEM vehicle manufacturers to integrate the CarFi system directly into the vehicle
entertainment system and enable rich features to

the OEMs and the consumers. For example, by
network
-
enabling the vehicle through integrated
Wi
-
Fi

and tethered mobile devices, the OEM
manufacturers may track vehicle operating information, driving patterns, location data and thereby
offer proactive serv
ice notification and vehicle fault monitoring, remote firmware updates to vehicle
systems, as well collect data with which to build future products better suited to the driving patterns
of consumers


3.6

Use Case: Mobile Internet

The embedded router/access po
int capability of the CarFi base unit will enable it to enhance the
capability of the existing vehicle entertainment system by enabling the vehicle to provide
mobile
Internet access to other devices in the vehicle such as tablets, mobile devices, handheld
gaming
units
, personal

computers and nearly anything else you can imagine which has wireless networking
capabilities.

Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
9


4.

System Components



CarFi system will have the following components:

1)

A CarFi base unit containing:

a.

An embedded 802.11a/b/g/n wireless n
etwork adapter

b.

An IPv4 and IPv6 router/access point (AP) which makes use of a tethered mobile
device to provide Internet access to AP clients

c.

An SD Card slot which supports SDHC and SDXC card formats

i.

Up

to 2TB of storage possible

d.

One micro USB port supp
orting USB 3.0 standard

e.

One standard USB port supporting USB 3.0 standard

f.

Two embedded Bluetooth radios which allows for simultaneous master and client
operation

g.

Two embedded ZigBee radios

h.

A built
-
in lithium ion battery giving 168 hours of sleep time and 6

hours of active
operation time without any input power.

i.

An embedded web server

2)

A remote OBD
-
II/CANBUS
reader that

connects to the CarFi unit as a Bluetooth client.

3)

Software clients for iOS, Windows platforms which enable media files to be maintained in
sync with the files on a storage volume accessible to the client.

4)

Access to the underlying operating system of the CarFi base unit to allows scripts to be run
on the base unit itself.

5)

Open APIs to allow 3
rd

party clients to be written which exchange data a
nd upload media to
the CarFi base unit. Initially, access to OBD
-
II and CAN bus by
CarFi

will be read
-
only.

6)

A web service which returns responses to client queries about the description of OBD
-
II
codes as well as provides an expert system for helping to
diagnose vehicle operation issues
based upon OBD
-
II fault codes and operating data the client sends into the web service.

7)

Optionally, a 12 VDC
-
to
-
USB power adapter will be sold which allows the CarFi base unit to
be powered from the 12 VDC accessory power
in a vehicle.

Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
10


5.

Assumptions

Dependencies and Risks

1)

A key assumption is that the OEM manufacturers are not planning to incorporate the
functionality
of the CarFi
directly into the vehicle
s they sell
.

2)

The CarFi base unit will have Read
-
Only access to the O
BD
-
II bus of the vehicle. The
proposed process is that the CarFi system will not be opened for Read
-
Write access until a
prototype system with Read
-
Write access enabled undergoes full source code review,
vulnerability scanning and penetration testing.




Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
11

6.

Alpha
System Development

Plan



Document Initial System Requirements



2 weeks



Review and Revise System Requirements with
B
usiness
S
takeholders



6 weeks



Finalize System Requirements



1 week



System Design



16 weeks



System Design Validation against require
ments



6 weeks



Functional Specification of System Componen
ts


3 weeks



System Component Prototype Development



12 weeks



Component
-
level Alpha Testing



2 weeks



System
-
level Alpha Testing


4 weeks



Functional Use Case Testing


4 weeks



Decision Request fo
r Further System Development
-

1 week

Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
12


7.

Recommendations

We recommend that the company
conduct further market research into this product idea and determine
the feasibility of producing and marketing this
product based

on a financial cost analysis of the
pr
oduction costs. We also recommend further study of the risks and dependencies inherent with a
product that

interfaces to a vehicle’s on
-
board bus system.

The product team is confident that the
product can be developed as a working system in the outlined
timeframe, and we recommend that the
company proceed to the next step in product development, marketing feasibility study.

Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
13


8.

Appendix A


Diagrams

8.1

System Diagram







Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
14


8.2

User Interface
Mockups



W
indows Client
User Interface Mockup



Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
15

W
eb Client
User In
terface Mockup



Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
16

iOS Client
User Interface Mockup






Project CarFi


_________________________________________________________________________________________


March 21, 2012





Team Omega




Product Proposal

|
P
age
17