Don't Forget Me: Passenger Safety System
SBIR
Blue Team
CS 410
October 22, 2007
Don’t Forget Me: Passenger Safety System
Table of Contents
Document
Pg. No.
Table of Contents ................................................................................................................................. 2
NSF Cover Sheet (Form 1207) .......................................................................................................... 4
Project Summary (Brandon Fields) ................................................................................................. 6
NSF Table of Contents (Form 1359) (Brandon Fields) ............................................................... 7
Project Description .............................................................................................................................. 8
Identification and Significance of the innovation (Brandon Fields) ............................................................. 8
Societal Problem (Brandon Fields) ..................................................................................................................................8
Proposed Solution (Brandon Fields) ................................................................................................................................9
Customer (David Ballentine) .........................................................................................................................................10
Background and Phase I Technical Objectives (David Ballentine) ............................................................. 11
Proposed Implementation (David Ballentine) ................................................................................................................12
Hardware Description (Brandon Fields) ........................................................................................................................17
User Interface Description (David Ballentine) ...............................................................................................................19
Expert Interviews (David Ballentine) ............................................................................................................................19
Consultants (Daniel Holloway) ...................................................................................................................... 20
References Cited (All) ....................................................................................................................... 22
Biographical Sketches (All) ............................................................................................................. 23
Budget (Hernan Gonzales) .............................................................................................................. 25
Current and Pending Support (Patrick Markham) ..................................................................... 31
Facilities, Equipment, and Other Resources (Patrick Markham) .......................................... 32
Special Information: .......................................................................................................................... 33
Listing of Key Words or Phrases (Brandon Fields) ..................................................................................... 33
Commercial Potential (Daniel Holloway) ..................................................................................................... 33
Appendix Items ................................................................................................................................... 39
Management Plan (Patrick Markham) ......................................................................................................... 39
Evaluation Plan (Patrick Markham) ............................................................................................................. 52
Resource Plan (David Ballentine) .................................................................................................................. 60
Marketing Plan (Daniel Holloway) ................................................................................................................ 63
Funding Plan (Hernan Gonzales) .................................................................................................................. 75
Staffing Plan (Patrick Markham) .................................................................................................................. 78
Schedule Plan (Brandon Fields)..................................................................................................................... 90
Risk Management Plan (Daniel Holloway) ................................................................................................... 93
2
Don’t Forget Me: Passenger Safety System
3
Don’t Forget Me: Passenger Safety System
NSF Cover Sheet (Form 1207)
COVER SHEET FOR PROPOSAL TO THE NATIONAL SCIENCE FOUNDATION
PROGRAM ANNOUNCEMENT/SOLICITATION NO./CLOSING DATE/If not in response to a program announcement/solicitation enter NSF 00-2
FOR NSF USE ONLY
NSF PROPOSAL NUMBER
FOR CONSIDERATION BY NSF ORGANIZATIONAL UNIT(S) (Indicate the most specific unit known, i.e., program, division, etc.)
DATE RECEIVED
NUMBER OF COPIES
DIVISION ASSIGNED
EMPLOYER IDENTIFICATION NUMBER (EIN) OR
FUND CODE
DUNS # (Data Universal Numbering System)
SHOW PREVIOUS AWARD NO. IF THIS IS
FILE LOCATION
IS THIS PROPOSAL BEING SUBMITTED TO ANOTHER
FEDERAL
TAXPAYER IDENTIFICATION NUMBER (TIN)
A RENEWAL
000-00-0000
AN ACCOMPLISHMENT-BASED RENEWAL
AGENCY?
YES
NO
IF YES, LIST ACRONYM(S)
NAME OF ORGANIZATION TO WHICH AWARD SHOULD BE MADE
ADDRESS OF AWARDEE ORGANIZATION, INCLUDING 9 DIGIT ZIP CODE
Computer Productivity Initiative
E & CS Building
4700 Elkhorn Ave Suite 3300
Norfolk, VA 23529-0162
AWARDEE ORGANIZATION CODE (IF KNOWN)
NAME OF PERFORMING ORGANIZATION, IF DIFFERENT FROM ABOVE
ADDRESS OF PERFORMING ORGANIZATION, IF DIFFERENT, INCLUDING 9 DIGIT ZIP
CODE
PERFORMING ORGANIZATION CODE (IF KNOWN)
IS AWARDEE ORGANIZATION (Check All That Apply)
(See GPG II.D.1 For Definitions)
TITLE OF PROPOSED PROJECT
FOR-PROFIT ORGANIZATION
SMALL BUSINESS
MINORITY BUSINESS
WOMAN-OWNED BUSINESS
Don’t Forget Me
REQUESTED AMOUNT
PROPOSED DURATION (1-60 MONTHS)
REQUESTED STARTING DATE
6
December 19, 2007
SHOW RELATED PREPROPOSAL
NO.,
IF APPLICABLE
months
CHECK APPROPRIATE BOX(ES) IF THIS PROPOSAL INCLUDES ANY OF THE ITEMS LISTED BELOW
BEGINNING INVESTIGATOR (GPG I.A.3)
VERTEBRATE ANIMALS (GPG II.D.12) IACUC App. Date
DISCLOSURE OF LOBBYING ACTIVITIES (GPG II.D.1)
PROPRIETARY & PRIVILEGED INFORMATION (GPG I.B, II.D.7)
HUMAN SUBJECTS (GPG II.D.12)
Exemption Subsection
or IRB App. Date
NATIONAL ENVIRONMENTAL POLICY ACT (GPG II.D.10)
INTERNATIONAL COOPERATIVE ACTIVITIES: COUNTRY/COUNTRIES
HISTORIC PLACES (GPG II.D.10)
SMALL GRANT FOR EXPLOR. RESEARCH (SGER) (GPG II.D.12)
FACILITATION FOR SCIENTISTS/ENGINEERS WITH DISABILITIES (GPG
V.G.)RESEARCH OPPORTUNITY AWARD (GPG V.H)
PI/PD DEPARTMENT
PI/PD POSTAL ADDRESS
Computer Science
925 Brandon Ave Apt 5A
Norfolk, Va 23517
PI/PD FAX NUMBER
757-555-1234
NAMES (TYPED)
High Degree
Yr of Degree
Telephone Number
Electronic Mail Address
M.S.
1987
757-683-4832
brunelle@cs.odu.edu
PI/PD NAME
Janet Brunelle
CO-PI/PD
pmark003@odu.edu
Patrick Markham
4
Don’t Forget Me: Passenger Safety System
CERTIFICATION PAGE
Certification for Principal Investigators and Co-Principal Investigators
I certify to the best of my knowledge that:
(1) the statements herein (excluding scientific hypotheses and scientific opinions) are true and complete, and
(2) the text and graphics herein as well as any accompanying publications or other documents, unless otherwise indicated, are the original work of the
signatories or individuals working under their supervision. I agree to accept responsibility for the scientific conduct of the project and to provide the
required project reports if an award is made as a result of this proposal.
I understand that the willful provision of false information or concealing a material fact in this proposal or any other communication submitted to NSF is a
criminal offense (U.S.Code, Title 18, Section 1001).
Name (Typed)
PI/PD
Signature
Social Security No.*
Janet Brunelle
Date
000-00-0000
Co-PI/PD
Patrick Markham
000-00-0000
Certification for Authorized Organizational Representative or Individual Applicant
By signing and submitting this proposal, the individual applicant or the authorized official of the applicant institution is: (1) certifying that statements made herein
are true and complete to the best of his/her knowledge; and (2) agreeing to accept the obligation to comply with NSF award terms and conditions if an award is
made as a result of this application. Further, the applicant is hereby providing certifications regarding Federal debt status, debarment and suspension, drug-free
workplace, and lobbying activities (see below), as set forth in the Grant Proposal Guide (GPG), NSF 00-2. Willful provision of false information in this application
and its supporting documents or in reports required under an ensuing award is a criminal offense (U.S. Code, Title 18, Section 1001).
In addition, if the applicant institution employs more than fifty persons, the authorized official of the applicant institution is certifying that the institution has
implemented a written and enforced conflict of interest policy that is consistent with the provisions of Grant Policy Manual Section 510; that to the best of his/her
knowledge, all financial disclosures required by that conflict of interest policy have been made; and that all identified conflicts of interest will have been
satisfactorily managed, reduced or eliminated prior to the institution’s expenditure of any funds under the award, in accordance with the institution’s conflict of
interest policy. Conflicts that cannot be satisfactorily managed, reduced or eliminated must be disclosed to NSF.
Debt and Debarment Certifications
(If answer “yes” to either, please provide explanation.)
Is the organization delinquent on any Federal debt?
Is the organization or its principals presently debarred, suspended, proposed for debarment, declared ineligible,
or voluntarily excluded from covered transactions by any Federal Department or agency?
Yes
No
Yes
No
Certification Regarding Lobbying
This certification is required for an award of a Federal contract, grant or cooperative agreement exceeding $100,000 and for an award of a Federal loan or
a commitment providing for the United States to insure or guarantee a loan exceeding $150,000.
Certification for Contracts, Grants, Loans and Cooperative Agreements
The undersigned certifies, to the best of his or her knowledge and belief, that:
(1) No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned, to any person for influencing or attempting to
influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in
connection with the awarding of any federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative
agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan, or cooperative agreement.
(2) If any funds other than Federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or
employee of any agency, a Member of Congress, and officer or employee of Congress, or an employee of a Member of Congress in connection with this
Federal contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form LLL, “Disclosure of Lobbying
Activities,” in accordance with its instructions.
(3) The undersigned shall require that the language of this certification be included in the award documents for all subawards at all tiers including
subcontracts, subgrants, and contracts under grants, loans, and cooperative agreements and that all subrecipients shall certify and disclose accordingly.
This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into. Submission of this
certification is a prerequisite for making or entering into this transaction imposed by Section 1352, Title 31, U.S. Code. Any person who fails to file the
required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure.
AUTHORIZED ORGANIZATIONAL REPRESENTATIVE
NAME/TITLE (TYPED)
TELEPHONE NUMBER
SIGNATURE
ELECTRONIC MAIL ADDRESS
DATE
FAX NUMBER
*SUBMISSION OF SOCIAL SECURITY NUMBERS IS VOLUNTARY AND WILL NOT AFFECT THE ORGANIZATION’S ELIGIBILITY FOR AN AWARD. HOWEVER, THEY ARE AN
INTEGRAL PART OF THE NSF INFORMATION SYSTEM AND ASSIST IN PROCESSING THE PROPOSAL. SSN SOLICITED UNDER NSF ACT OF 1950, AS AMENDED.
5
Don’t Forget Me: Passenger Safety System
Project Summary (Brandon Fields)
Each year young children are left in automobiles while their parent(s) or caregiver is away.
Unfortunately it does not take long for a car to become dangerously hot and endanger the life of a child
inside. Likewise, any person or pet left in a car for an extended period of time is at risk of being
seriously harmed. Modern cars do not yet have the capability to determine when the conditions of its
interior could pose a danger to its passengers, nor do many vehicles have the ability to register that a
child has been left inside.
The goal of the Don't Forget Me (DFM) system is to eliminate such instances of unintentional
child endangerment. By implementing a series of sensors that will determine if a vehicles is occupied,
the system can begin to take corrective action. A heartbeat sensing system is one of the primary
components; the data it collects is analyzed for a verifiable pattern. Secondly, pressure sensors will be
installed beneath the seats to determine if anyone is occupying the vehicles. Once again the output of
the sensors will checked by the accompanying software to ensure it is a person and not an obstruction
detected. There will also be careful monitoring of the temperature inside the car. Since the
temperature can rise to fatal levels in minutes, a high temperature reading will initiate an aggressive
check of the vehicle for persons who may be in danger. This device is autonomous and does not
require the activation of the car's operator. It seeks to eliminate instances when one can let even
important issues pass their attention.
Lastly, the use of several different types of sensors (pressure, temperature, motion, heartbeat,
CO2) will drastically reduce the risk of invoking a false-alarm. An emergency alarm will not go off
until the danger is confirmed by the other sensors in the system. This will help to ensure that rescue
personnel can trust that their service is really needed and that parents/caregivers do not feel that they
should ever have to disengage the DFM system for reasons of inconvenience.
6
Don’t Forget Me: Passenger Safety System
NSF Table of Contents (Form 1359) (Brandon Fields)
TABLE OF CONTENTS
For font-size and page-formatting specifications, see GPG Section II.C.
Section
Total No. of
Page No.*
Pages in Section
(Optional)*
Cover Sheet (NSF Form 1207) (Submit Page 2 with original proposal only)
A
Project Summary (not to exceed 1 page)
1
6
B
Table of Contents (NSF Form 1359)
1
7
C
Project Description (including Results from Prior NSF Support)
(not to exceed 15 pages) (Exceed only if allowed by a specific
program announcement/solicitation or if approved in advance by the
13
8
D References Cited
1
22
E Biographical Sketches (Not to exceed 2 pages each)
2
23
F Budget
(NSF Form 1030, plus up to 3 pages of budget justification)
6
25
G Current and Pending Support (NSF Form 1239)
1
31
H Facilities, Equipment and Other Resources (NSF Form 1363)
1
32
I
6
33
54
39
appropriate NSF Assistant Director or designee)
Special Information/Supplementary Documentation
J Appendix (List below)
Include only if allowed by a specific program announcement/
solicitation or if approved in advance by the appropriate NSF
Assistant Director or designee)
K
L
M
N
O
P
Q
R
Appendix Items:
Management Plan
Evaluation Plan
Resource Plan
Marketing Plan
Funding Plan
Staffing Plan
Schedule Plan
Risk Management Plan
*Proposers may select any numbering mechanism for the proposal. The entire proposal, however, must be paginated. Complete
both columns only if the proposal is numbered consecutively.
NSF Form 1359 (10/99)
46
7
Don’t Forget Me: Passenger Safety System
Project Description
Identification and Significance of the innovation (Brandon Fields)
Societal Problem (Brandon Fields)
According to the EPA the following people are at risk for heat related illness; older persons (age
> 65), infants (age < 1), people taking certain medications (e.g., for high blood pressure, depression,
insomnia). Likewise, people who are mentally disabled or physically handicapped may be unable to
help themselves if a caregiver has left them alone in a vehicle. Currently 23% of all non-traffic related
deaths for children under the age of 15 are caused by hyperthermia as a result of being left in vehicles.
In the mid 90s child safety seats were moved from the front passenger side to the back rear. This was
an attempt to mitigate the number of deaths being caused by air bags. While the air bag related deaths
did decrease the number of hyperthermia deaths have steadily increased ever since. Unless some form
of technology is used to mitigate this risk, there is no indication that the problem will ever go away.
8
Don’t Forget Me: Passenger Safety System
Proposed Solution (Brandon Fields)
The Don't Forget Me system incorporates several sensors in order to (1) determine if the
temperature in the vehicle is rising at a rate that will soon become hazardous to passengers, and (2)
determine that there is a person or animal in the vehicle that may be harmed if the situation is not dealt
with. The DFM system is designed to run when the car has been parked. Readings from the sensors
are most accurate when the car is not actively being driven. Also a driver acting in the best interest of
their passenger(s) would not allow the conditions in the vehicle they are driving to become so
hazardous.
There are three different types of hardware used in the DFM; sensors to detect the state inside
the vehicle, sensors to detect the driver relative to the vehicle, a micro-computer to perform operations
on the sensor readouts and the emergency alert system. The sensors used to detect the passenger(s)
state are the pressure sensors, a temperature sensor, a CO2 sensor, and a heartbeat sensor. Lastly, the
hardware used to detect the driver is a remote, and a range sensor.
First of all the pressure sensors are installed beneath the seats to determine if the seat is
occupied. Since a person would move slightly over a short period of time variations in the pressure
would indicate that there is in fact a person in the seat rather than clutter. The sensor is given the
lowest priority since it is used primarily to verify the results of the other sensors. Next, there is a
temperature sensor in the vehicle that will continuously update the stored temperature values; output
will also be used to calculate the rate at which the temperature in the car is changing. If the
temperature has reached a critical point or temperature-rate combination and it has been verified
through the software that a person is in the car then the emergency protocol will be activated. Lastly,
the heartbeat and CO2 sensors create the initial passenger detection. While the vehicle is parked the
heartbeat sensor will be able to generate a pattern based on its readings, the pattern is analyzed by the
software and it if matched a specific tolerance then there will be a positive passenger detection. The
9
Don’t Forget Me: Passenger Safety System
detection is then verified with the aforementioned pressure sensors and the CO2. For each of the three
passenger detection sensors a value of certainty is generated and then weighted. If the overall certainty
is high enough and the critical point has been established by the readings on the temperature sensor
than emergency actions will take place.
The driver detection system relies on two pieces of hardware, the remote and range sensor. The
DFM will always calculate the distance the driver is from the car using the strength of the signal it
receives from the key chain remote. Assuming the driver has their keys on them and the remote is with
the keys this device will initiate the car's alarm system if driver goes too far from the vehicle without
removing the child.
Lastly the emergency alert system is also based on two pieces of hardware, the car's internal
alarm and a 911 caller. If the software has determined that the situation is critical then it will set off the
car's alarm and dial 911. First of all the car alarm will sound for a short period of time to alert the
driver or anyone in the proximity of the situation. If the incident is not immediately remedied the 911
caller goes into action. The 911 caller will have a message to the dispatcher which will have to be
triangulated in order to determine the car's location; this is a common feature in enhanced 911.
Since the software can determine the rate at which the temperature is increasing it can
determine an appropriate response time. Based on the data it receives from the sensors the time is
different for each scenario.
Customer (David Ballentine)
The primary customer of the Don’t Leave Me will be the car manufacturers. They will be sold
the software, and the rights to use it per vehicle. They themselves will buy the sensors and install them
how they see fit while in accordance to the Don’t Leave Me specifications. The benefit to the car
manufacturer is the fact that it shows a dedication to safety, it can improve car sales, and it will reduce
the number of fatalities or injuries occurring in that vehicle. Safety is becoming one of the top priorities
10
Don’t Forget Me: Passenger Safety System
for car manufacturers, and the Don’t Leave Me will help in this goal.
The secondary customer is the end users that will be buying the car. It is important to keep this
secondary costumer in mind, as they are the ones who will actually be using the system. The benefits
for the secondary customer includes lives saved, no legal action, and it will reduce family distress.
Background and Phase I Technical Objectives (David Ballentine)
The primary object in phase 1, is to create a simulation of the Don’t Forget Me. A lab prototype
will be developed and demonstrated to the potential customer. Initial development of product software
will also be completed in this phase. As outlined in the Evaluation Plan, the success of this phase will
be measured by the satisfactory completion of the software as well as the prototype. Also being
developed in this phase is the documentation for our product which includes the requirements
document, test simulation documentation user manual, and refinement of our plans.
11
Don’t Forget Me: Passenger Safety System
Proposed Implementation (David Ballentine)
The Don’t Forget Me will be implemented right into a vehicle at the time of manufacturing.
Although the vehicle manufacturer will decide the exact specifications on how to implement it
successfully with the specific car make and model, the following modals will depict and abstract view
of a proposed implementation.
The following image shows a general proposed location of the five sensors. The Pressure
Sensor is located on the seat to sense if there is an object or person on the seat. The Heartbeat Monitor
is placed on the back of the seat to detect if there is a person on the seat, or just a backpack. The CO2
Sensor in the back serves a similar purpose and is used with the Heartbeat Monitor, instead detecting
CO2 levels from a person breathing.. The Motion Sensor is placed ahead of the seat to get the best
field of vision to detect any motion from a person sitting in the seat. The Temperature Sensor will
detect how dangerous an environment it is currently inside the car, and thus how deadly. These five
sensors work in unison to accurately access the situation inside and react accordingly.
The following images will demonstrate both the goal, and the exact need for the Don’t Forget Me
12
Don’t Forget Me: Passenger Safety System
implementation. The first will be a process flow of what would normally happen without a Don’t
Forget Me installed in the Vehicle.
In this Scenario, we have a businessman who has just arrived at work. Earlier in this day, his
wife had to run out on an emergency, and thus he was charged with the responsibility of dropping off
their child to the daycare center. Unfortunately for him, this was a very unusual event. With the child
asleep in the back seat, he instead drove strait to work completely forgetting about his child.
13
Don’t Forget Me: Passenger Safety System
With the father gone off to work, the child is trapped. This particular day happens to be about
85 degrees outside. Normally this temperature is very nominal, and not very life threatening.
Unfortunately for the child, a car is the perfect greenhouse. At that temperature, in just 7 – 10 minutes,
the inside temperature of the car will be about 100 degrees, and in about 30 minutes, the inside
temperature will be 120 degrees. [2] The father will not be back for at least a few hours. The car
becomes a prison for the poor child, with no chance for escape. When the father gets back, no only
will he have a horrible surprise, he will also face major legal problems.
14
Don’t Forget Me: Passenger Safety System
With a Don’t Forget Me Installed within the vehicle, this will not happen. The following will
show the exact same scenario with an entirely different outcome.
Just as before, we have a businessman who has just arrived at work instead of dropping his
child off at the daycare. Fortunately for him, his car is implemented with a Don’t Forget Me. As he
walks away, the Don’t Forget Me in the car detects that there is in fact a baby in the car, and that the
keys to the car, which the man holds, are now 10 feet away. It triggers the car alarm, alerting the
businessman.
15
Don’t Forget Me: Passenger Safety System
Because of the Don’t Forget Me, the father remembers his mistake, and is able to go retrieve the
child before harm can come to the child. The child is now safe.
The alarm will continue to go off until the car is started, the baby is removed, or a button is
pushed in the back seat of the care. This button will ensure that if the child left is old enough to safely
stay in the car, the alarm can be deactivated. The system will continue monitoring conditions in the car
though, and if conditions become too hazardous, the alarm will sound again, and cannot be shut off
until the child is removed.
16
Don’t Forget Me: Passenger Safety System
Hardware Description (Brandon Fields)
Since a patent will be licensed out the customer rather than an entire self-contained product no
hardware will be sold to the customer. Rather, specifications for recommended hardware will be
supplied to the client so that he or she can purchase hardware that most appropriately fits his or her
needs.
The best hardware will be determined in the testing phases of development. First the software
that runs the DFM will be run using virtual sensors to ensure a cost-effective simulation. Once all the
virtual testing is complete real world sensors and other hardware will be introduced to the simulation to
ensure that each component performs as expected. The final stages of testing will not use virtual data,
instead the product will be implemented fully to ensure that the virtual testing results are congruent to
the real-world results.
In order for the DFM to be successful it will require the hardware listed as follows:
Sensor
Role
Temperature Sensor
Records the temperature and sends value to the
main program which checks to make sure the
value is in an appropriate range.
Pressure Sensor
Each time one of these sensors changes state the
main program will record that that section of the
car is occupied. It the pressure is constant it may
be assumes there are object on top of it. If it
varies to a specific tolerance a person may be
registered as an occupant.
Vibration Sensor (Heartbeat detection)
One or more of these sensors will be placed where
a child seat is supposed to sit. The main program
will read the output from the sensor and generate a
wave pattern. If the wave pattern is congruent to
that which reflects a heart beat the main program
will register that there is an occupant.
Motion Sensor
These sensors will be placed on the ceiling and the
back of head rests in the car to detect motion
relating to passengers. They will validate
information collected by the other sensors.
17
Don’t Forget Me: Passenger Safety System
CO2 Sensor
This sensor detects a critical level of CO2. The
main idea is that if a car is vacant the amount of
CO2 it contains will decrease since no one is there
to create more. If the level of CO2 increases it
may be because a person is still occupying the
vehicle.
User Interface Device
Role
Remote Receiver
The receiver will work in the same manner that a
modern electric key receivers do. The main
difference is that the receiver will measure when
the key is about go out of range while the car is
“occupied” and set the alarm to alert the driver.
Key Fob
The key fob is a device that will go on ones key
chain that can measure the distance between the
keys and the car and interact with the DFM
remotely. If the user correctly installs their key
fob next to the vehicle's key on a ring then the fob
will be able to determine if the passenger has left
the vehicle and how far from the vehicle they are.
Deactivate Switch
There will be a switch located in the center-back
section of the car that can be pushed down in
order to prevent false alarms. If the user is
leaving a capable passenger in the car, or a false
alarm occurs activating this spring loaded switch
will deactivate the system. The system is once
again activated when the car doors open back up.
Emergency Alert System
Role
Alarm
The alarm if not standard for the vehicle will have
to be installed. When an emergency is indicated
by the DFM the alarm system will activate in the
same manner it would if the was being broken
into. This should immediately get the drivers
attention or at the least get the attention of
bystanders who can alert emergency authorities.
Microcontroller
The CPU and ROM will be housed on a
microcontroller that is capable of accessing the
stored program. The microcontroller will take the
input values for each device and supply their
values as input to the main program. The main
program will assess the conditions in the car and
activate the alarm if necessary.
18
Don’t Forget Me: Passenger Safety System
User Interface Description (David Ballentine)
There will be two very basic user interfaces. The first is the simple switch in the back. This is
used to temporarily disable the proximity alarm. The alarm will still go off if conditions become too
hazardous. The second interface concerns the readout when a car mechanic runs a diagnostic on the
car’s internal computer. If there is a malfunction with the Don’t Forget Me, it will be included in this
diagnostic.
Expert Interviews (David Ballentine)
The following is a list from two interviews. This list contains important information that has
impacted the direct of the Don’t Forget Me development.
Roger Kelly from Gloucester County Public Schools
School buses in the state of Virginia do not have seat belts with the exception of the Special Needs
buses

Compartmentalization is the standard used in the school bus industry

Average price for a standard 64 passenger conventional school bus is approximately $70,000
and special Needs bus averages approximately $78,000

There are one or two incidents of this nature very year here in Hampton Roads
Chris Edward from NASA

System uses a transmitter and receiver

Have yet to market it

Gives advice to get it quickly from the design stage to market.

Cost is around $35
19
Don’t Forget Me: Passenger Safety System
Company Information (Daniel Holloway)
The Computer Productivity Initiative (CPI) was created in 1995 as part of the Computer
Science Undergraduate Degree Program at Old Dominion University in Norfolk, Virginia. The goal of
CPI is to identify and implement modifications to the curriculum that will help students better
understand how to apply their education to real world problems. In CS410, students would develop
solutions to real world problems and take the necessary steps to develop a solution and show that it is
feasible. The Don’t Forget Me product is a viable solution to a real world problem utilizing sensor
technology and complex algorithms. Our company will provide a patent on our technology available
for a company to license. We will provide specifications with our system but the manufacturer will
provide the optimization and installation of the product. The knowledge we have gained from the
Computer Science program at Old Dominion University as well as utilizing the expertise from our
consultants will help foster our company’s success. Our company started with five undergraduates in
the positions of project manager, software manager, hardware manager, financial manager, web
designer, and marketing manager. We produce the technology to save lives utilizing a system of sensors
and complex algorithms. We will pursue a major car manufacturer to license our technology and our
return on investment comes from the royalties of units installed in their vehicles.
Consultants (Daniel Holloway)
Professor Janet Brunelle: Professor Janet Brunelle received her Bachelors of Science degree in
Computer Science from Old Dominion University in 1980 and her MS in Computer Science from Old
Dominion University in 1987.
William C. Edwards: Mr. Edwards is a manager in the Laser Remote Systems Branch for National
Aeronautics and Space Administration (NASA). He is a co inventor of a Child Protective Device. His
expertise in a similar technology is beneficial for our success. Mr. Edwards met with our key personnel
20
Don’t Forget Me: Passenger Safety System
from our company and gave us an overview of his product from the conception to the finished product.
He also provided us advice on what he learned and what he would do different.
Roger Kelly: Roger Kelly is Director of Transportation for the Gloucester County Public School
System. His knowledge on school bus safety and transportation is beneficial for our understanding of
the potential need for such a devise as the DFM. Mr. Kelly provided us with Gloucester County School
division’s purchasing model for school buses.
21
Don’t Forget Me: Passenger Safety System
References Cited (All)
[1] Kids and Cars http://www.kidsandcars.org/
[2] EPA Gov http://www.epa.gov/hiri/about/pdf/EHEguide_final.pdf
[3] Thingamababy http://www.thingamababy.com/baby/2007/07/babysafety.html
[4] Public School Buses http://www.schoolbusinfo.org/
Supt’s Memo http://www.pen.k12.va.us/VDOE/suptsmemos/2006/reg010.html
Bus Regulations http://www.pen.k12.va.us/VDOE/Finance/VAPT/regulations.htmBaby alert
instructions http://www.babyalert.info/howitworks.php
Child Passenger Deaths http://www.luhs.org/depts/injprev/Transprt/tran2.htm
NASA Device http://www.kidsandcars.org/NASAPressRelease.pdf
National Transportation Statistics
http://www.bts.gov/publications/national_transportation_statistics/
Baby Bee Safe http://www.babybeesafe.net/
Child Minder https://www.babyalert.info/home.php
Definition “Caregiver” http://www.merriam-webster.com/dictionary/caregiver
Definition “Hyperthermia” http://en.wikipedia.org/wiki/Hyperthermia
22
Don’t Forget Me: Passenger Safety System
Biographical Sketches (All)
Patrick Markham - Project Manager
Patrick Markham was born in Norfolk, VA and is now a Senior at Old Dominion University in
Computer Science. He plans to pursue his Masters Degree here at ODU. Patrick was certified a Novell
NetWare 6 Administrator in high school and has experience working several years as the network
administrator for an international small business and as a web administrator for a national political
office.
David Ballentine - Software Specialist and Web Development Team
Team's Software Specialist as well as part of the Web Development Team. He specializes in
languages such as Java and PHP, but also programs in C++, C, Perl, Python, Auto-It, Prolog, as well as
many others. He is also very experienced in Database Modeling, and in using such programs as
MySQL, Oracle 9i, and Microsoft SQL. Hobbies include anime, sci-fi, online role playing, video
games as well as side programming jobs.
Brandon Fields – Hardware Specialist and Documentation Coordinator
Records group activities and progress, as well as researches of applicability of specific
hardware components. Has a minor in electrical computer engineering, and modeling and simulation.
His current interests are operating systems design, principles of programming languages and compilers,
as well as computer graphics programming.
Hernan Gonzales - Financial Representative and Web Development Team
Financial specialist and Web Designer of blue team. Computer skills include programming
C++, Java, PHP/MySQL, Perl, Visual Basics, Javascript, C#/MS SQL, etc. Computer related hobby
includes building websites and online advertising strategy. He plans to be a reseller online after
graduation. Other hobbies include basketball, swimming, pool, video games, traveling, hang-out with
friends, and many more.
23
Don’t Forget Me: Passenger Safety System
Daniel H. Holloway - Marketing Manager and Risk Assessment
Daniel Holloway is the marketing manager of the group. He is currently employed by the
Gloucester County Public School system. His interests include data management and developing
school related software.
24
Don’t Forget Me: Passenger Safety System
Budget (Hernan Gonzales)
Phase I: Personnel Cost (5-6 months)
Employee Type
Qty
Jr. Project Manager
Jr. Software Manager
Jr. Hardware Manager
Jr. Financial Manager
Jr. Documentation Specialist
Subtotal
Sr. Software Consultant IV
Sr. Hardware Consultant IV
Electrical Engineer Consultant IV
Subtotal
1
1
1
1
1
Employment Yearly Salary
Duration
Paid as
intern
120 days
$24,000
60 days
$24,000
120 days
$24,000
50 days
$24,000
50 days
$24,000
1
1
1
Based on
Salary.com
$87,756
$80,124
$86,235
30 days
50 days
30 days
Employee Cost
$7,920
$3,960
$7,920
$3,300
$3,300
$26,400
$7,200
$11,000
$7,080
$25,280
Subtotal
Overhead – 40%
$51,680
$20,672
Total
$72,352
Phase I: Hard Resource Cost (5-6 months)
Hard Resource
Processing unit prototype
Car key remote with beeper prototype
Accelerometer sensor prototype
Motion sensor prototype
Vibration sensor prototype
Temperature sensor prototype
Co2 sensor prototype
Subtotal
Number
Of Units
1
1
1
1
1
1
1
Price Per
Unit
$70
$60
$50
$45
$35
$6
$19
2
1
$899
$695
$1,000
$1,798
$695
$1,000
6
1
$20
$40
$120
$40
Dell Inspiron Advanced
3-D modeling software
Other software (e.g. MS Visio, Quicken,
etc)
Sensors housing
CPU housing prototype
25
Total
$70
$60
$50
$45
$35
$6
$19
$285
Don’t Forget Me: Passenger Safety System
Installation tools/equipment
Sensors cables (5 meters)
Electronic wires (100 inches)
Other supplies (tapes, screws, bolts, etc)
Workstation (ODU Campus)
Dummy used car for testing
Misc.
Subtotal
7
5
1
$2,000
$10
$89
$500
$5,000
$10,000
Total
$2,000
$70
$445
$500
Free
$5,000
$10,000
$20,668
$21,953
Phase I
Total Personnel Cost
Total Hard Resource Cost
Total
$72,352
$21,953
$94,305
Phase II overview: In phase II, we have to beta test our product in a car, bus, suv, van, and pickup, total
of 5 vehicles. So, the number of sensors purchased is based on the number of vehicles.
Phase II: Personnel Cost (2 years)
Employee Type
Project Manager
Software Manager level II
Hardware Manager level II
Financial Analyst level II
Marketing Manager
Subtotal
Hardware Engineer IV
Hardware Engineer II
Hardware Engineer II
Hardware Engineer II
Hardware Engineer II
Software Engineer IV
Software Engineer II
Software Engineer II
Software Engineer II
Software Engineer II
Electrical Engineer IV
Qty
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Employment
Duration
180
100
180
100
100
180
180
180
180
180
180
90
90
90
90
180
26
Yearly Salary
days
days
days
days
days
Based on
Salary.com
$77,495
$62,227
$59,373
$55,069
$73,384
days
days
days
days
days
days
days
days
days
days
days
Based on
Salary.com
$80,124
$59,373
$59,373
$59,373
$59,373
$87,756
$62,227
$62,227
$62,227
$62,227
$86,235
Employee Cost
$38,160
$17,000
$29,340
$15,100
$20,100
$119,700
$39,600
$29,340
$29,340
$29,340
$29,340
$43,200
$15,300
$15,300
$15,300
$15,300
$42,480
Don’t Forget Me: Passenger Safety System
Assembly crew
Subtotal
5
60 days
$23,728
$19,500
$323,340
Subtotal
Overhead – 40%
$443,040
$177,216
Total
$620,256
Phase II: Hard Resource Cost (2 years)
Hard Resource
Number Of
Units (for 5
vehicles)
Processing unit
Car key remote with beeper prototype
Accelerometer sensor prototype
Motion sensor prototype
Vibration sensor prototype
Temperature sensor prototype
Co2 sensor prototype
Subtotal
Additional Dell Inspiron Advanced
Sensors housing
CPU housing prototype
Additional sensors cables (5 meters)
Additional electronic wires (100 inches)
Additional supplies (tapes, screws, bolts,
etc)
Used GMC School Bus (15-30 capacity)
Used Chrysler Voyager Van
Misc.
Subtotal
Total
Phase II
Total Personnel Cost
Total Hard Resource Cost
Total
Price Per
Unit
Total
5
5
6
10
60
10
14
$70
$60
$50
$45
$35
$6
$19
$350
$300
$300
$450
$2,100
$60
$266
$3,826
5
100
5
100
50
5
$899
$20
$40
$10
$89
$500
$4,495
$2,000
$200
$1,000
$4,450
$2,500
1
1
$12,000
$6,900
$12,000
$6,900
$10,000
$43,545
$47,371
$620,256
$47,371
$667,627
Phase III: Personnel Cost (6 months basis)
27
Don’t Forget Me: Passenger Safety System
Employee Type
Project Manager
Software Manager level II
Hardware Manager level II
Financial Analyst level II
Marketing Manager
Subtotal
HR
Lobbyist
Technical Writer
Hardware Engineer Manager
Software Engineer Manager
Research/Test Engineer
(Hardware)
Research/Test Engineer
(Software)
Technical Support 1
Technical Support 2
Subtotal
Qty
Employment
Duration
1
1
1
1
1
120
60
120
50
50
Yearly Salary
Employee Cost
days
days
days
days
days
Based on
Salary.com
$77,495
$62,227
$59,373
$55,069
$73,384
$7,650
$13,770
$14,040
$19,800
$24,480
$19,800
$26,560
$11,350
$20,680
$7,550
$8,670
$74,810
1
1
1
1
1
1
90
90
90
90
90
90
days
days
days
days
days
days
Based on
Indeed.com
$31,000
$56,000
$57,000
$80,124
$99,431
$80,124
1
90 days
$99,431
$24,480
1
1
180 days
180 days
$34,000
$34,000
$16,740
$16,740
$157,500
Subtotal
Overhead – 40%
$232,310
$92,924
Total
$325,234
Phase III: Hard Resource Cost (6 months basis)
Hard Resource
Workstation
Misc.
Advertising/Marketing budget
Office supplies
Additional office equipments
Number
Of Units
6 months
lease
Total
Price Per
Unit
Total
$1,000
$6,000
$150,000
$1,000
$10,000
$20,000
$150,000
$1,000
$10,000
$187,000
28
Don’t Forget Me: Passenger Safety System
Phase III
Total Personnel Cost
Total Hard Resource Cost
Total
$325,234
$187,000
$512,234
Summary Phase I-III:
TOTAL BUDGET
Phase I
Phase II
Phase III
Total
$94,305
$667,627
$512,234
$1,274,166
Out Years (based annually)
Note: The research budget cost for the out years will depend on the future technology. Its cost is only
based on our prediction and estimation. Misc. cost includes petty cash, traveling fees, any
unpredictable expenses, and others.
Out Year: Personnel Cost
Employee Type
Project Manager
Software Manager level II
Hardware Manager level II
Financial Analyst level II
Marketing Manager
Subtotal
HR
Lobbyist
Technical Writer
Hardware Engineer Manager
Software Engineer Manager
Research/Test Engineer
(Hardware)
Research/Test Engineer
(Software)
Technical Support 1
Qty
1
1
1
1
1
Employment
Duration
120
60
120
50
50
Yearly Salary
Employee Cost
days
days
days
days
days
Based on
Salary.com
$77,495
$62,227
$59,373
$55,069
$73,384
$7,650
$13,770
$14,040
$19,800
$24,480
$19,800
$26,560
$11,350
$20,680
$7,550
$8,670
$74,810
1
1
1
1
1
1
90
90
90
90
90
90
days
days
days
days
days
days
Based on
Indeed.com
$31,000
$56,000
$57,000
$80,124
$99,431
$80,124
1
90 days
$99,431
$24,480
1
180 days
$34,000
$16,740
29
Don’t Forget Me: Passenger Safety System
Technical Support 2
Subtotal
1
180 days
$34,000
$16,740
$157,500
Subtotal
Overhead – 40%
$232,310
$92,924
Subtotal
Total (multiply by 2 to get annual cost)
$325,234
$650,468
Out Year: Hard Resource Cost (annually)
Hard Resource
Workstation
Misc.
Research Budget
Office supplies
Additional office equipments
Number
Of Units
6 months
lease
Subtotal
Total (multiply by 2 to get annual cost)
Est. Out Year
Total Personnel Cost
Total Hard Resource Cost
Total
Price Per
Unit
Total
$1,000
$6,000
$1,000
$10,000
$20,000
$200,000
$1,000
$10,000
$237,000
$474,000
$650,468
$474,000
$1,124,468
30
Don’t Forget Me: Passenger Safety System
Current and Pending Support (Patrick Markham)
Industry experts, consultants and numerous specialists are essential to the success of this
project. Such aide will be sought in Phase 1, pending acquisition of appropriate SBIR funding. The
expertise necessary to oversee development on an intimate level, however, can already be found in the
team's Senior Personnel, comprised of the Project Manager and four additional directors. All five are
currently completing work on a B.S. in Computer Science at Old Dominion University (ODU) in
Norfolk, VA and expect to receive said degree prior to development of the Don't Forget Me system.
They will then begin to pursue a M.S. in Computer Science at ODU. The undergraduate degree fully
prepares individuals to excel in a range of technical positions, work environments and challenging
scenarios, and demands flexibility to meet new computer-related challenges for which they were not
specifically prepared, as they arise. The program also prepares individuals to generate reports, produce
technical writing and, ideally, handle positions of management within their area of expertise. The
graduate degree further solidifies the knowledge base acquired in the undergraduate program. Finally,
the senior personnel represent more than 15 years in combined work experience in computer sciencerelated positions.
31
Don’t Forget Me: Passenger Safety System
Facilities, Equipment, and Other Resources (Patrick Markham)
For the initial phases of the project (Phases 1 & 2), all necessary overhead will be provided
courtesy the Old Dominion University Computer Science Department, including, but not limited to,
office and workspace, telephone and Internet access, computers and printers.
During this time, all facilities and equipment will be located at:
Old Dominion University
Engineering & Computer Science (E&CS) Building
4700 Elkhorn Ave. Suite 3300
Norfolk, VA 23529-0162
32
Don’t Forget Me: Passenger Safety System
Special Information:
Listing of Key Words or Phrases (Brandon Fields)
Caregiver – a person who provides direct care (as for children, elderly people, or the chronically ill)
CPU – Central Processing Unit, device capable of performing calculations and completing a finite set
of instructions.
DFM – Don’t Forget Me, the current name of the project.
Hyperthermia - an acute condition which occurs when the body produces or absorbs more heat than it
can dissipate. It is usually due to excessive exposure to heat. The heat-regulating mechanisms of the
body eventually become overwhelmed and unable to effectively deal with the heat, and body
temperature climbs uncontrollably.
ROM – Read Only Memory, data storage device capable of housing data and programs. It does not
require a constant source of power to maintain data integrity.
Commercial Potential (Daniel Holloway)
Millions of passenger vehicles are produced and sold annually and over 400,000 school buses
transport millions of children to and from schools every school day. Safety is a major consideration
when designing vehicles that transport people on our roads and national highways. With the
diminishing car sales in recent months, each car makers are looking for ways to gain an edge over their
competitors. Vehicle safety will provide manufacturers with a unique marketing tool that emphasizes
safety. People who purchase vehicles that transport young children and the elderly can benefit from
features that enhance safety.
Target Market:
Primary customers are the car manufactures and the secondary customers are the
consumers buying vehicles with “Don’t Forget Me” installed.
33
Don’t Forget Me: Passenger Safety System
The number of passenger vehicles produced annually is around 4.8 million with around 5 million
sold annually. The reason for more cars being sold than produced in a year is attributed to the fact that
cars that were not sold in previous years are sold later then counted in current year statistics. School
buses are the largest mass transit program in the US. There are over 440,000 school buses that transport
more than 24 million children every day of the school year. This indicates that there exists a large
potential passenger vehicle market. Safety is a concern with both markets including passenger car
manufacturers, and bus manufacturers. With non-traffic fatalities due to heat on the rise, our device will
help prevent this tragedy from occurring. School buses using seat belts is a recent topic under debate.
While most states do not enforce school bus seat belts because of the effort involved in maintaining
them, our device will help prevent incidents involving leaving children on buses unattended, and can
be used to help keep children in their compartment.
Successfully marketing our technology and finding a major car manufacturer to license our
technology is vital for our success. We will present our technology at conferences, trade shows, and to
car manufacturers. Furthermore, we will advertise our technology in auto and safety magazines. Also,
we plan to find advocates for our technology by Beta testing our product in buses and passenger
vehicles. We will provide our technology and installation free of charge in a handful of vehicles and
conduct Beta testing for one year. This method will aid in gaining advocates to help market our
technology which should foster confidence in our product with major car manufacturers.
34
Don’t Forget Me: Passenger Safety System
Competition -
(Diagram: Competition Matrix)
The competition matrix above, diagram 4, shows some of the current products that attempt to tackle the
problem of people being left in vehicles for extended amount of time.
Child Presence Device from NASA
The Child Presence Device utilizes pressure and distance sensors, and has a means for alarming the
caregiver. NASA patented the technology and is presently trying to market the technology. The Child
35
Don’t Forget Me: Passenger Safety System
Presence Device cost is approximately $35, however, it has not reached the market yet.
Halo Baby Seat Safety System
The Halo Baby Seat Safety System provides all that the Child Presence Device has to offer, plus it
detects the inside vehicle temperature. The Halo Baby Seat Safety System retail cost is $129; however,
one can purchase it from the internet for a reduced price of $89.
Baby Alert’s Child Minder System
The Baby Alert’s Child Minder System provides all that the Child Presence Device has to offer and
provides an automatic self-test. It does not utilize temperature sensors to detect the interior vehicle
temperature. The Baby Alert’s Child Minder System can be purchased for $89.99.
Volvo S80 Heartbeat Sensor
The Volvo S80 Heartbeat Sensor only offers a means for detecting a heartbeat. It does not have a way
to tell the difference between a human heartbeat and another living animal. The Volvo heartbeat sensor
comes standard with the Volvo S80 and adds $400 to the cost of the vehicle.
VTI heartbeat sensor
The VTI heartbeat sensor offers the same as the Volvo S80 heartbeat sensor. It uses accelerometers to
detect small vibrations and utilizes software to specifically detect a heartbeat. Our Don’t Forget Me
System offers everything the competitors offer plus a light and vibration indicator, auto temperature
control, and a CO2 sensor.
Advantages the DFM has over other competitors is that the DFM system offers a more accurate
36
Don’t Forget Me: Passenger Safety System
method of detecting an unattended child’s’ presence in a vehicle by analyzing multiple sensors and
information, thus mitigating the chance of a false alarm. The DFM offers a better solution where
accuracy is greater for the car and bus manufacturers plus minimizing the fatalities or person being
serious injured in one of their vehicles can be devastating to there existence. Added safety features in
buses have been discussions between school agencies, and bus manufactures as they are always
looking for safer school buses, though school buses are one of the safest transit programs.
Distribution –
Our customers are the car manufacturers, thus we need to prove to them we have a quality
product that will enhance safety features in their vehicles and increase sales. We will patent the DFM
system and have the car manufacturer license the technology paying a fee for every unit installed in a
vehicle over the lifetime of the patent. In the initial phase, we will provide an exhibit at national safety
conferences such as the Lifesavers 2008 Conference ( http://www.lifesaversconference.org/).
Lifesavers conference is the premier national highway safety meeting in the United States and is
dedicated to reducing deaths and injuries on our nation's roadways. The Lifesavers conference drew
over 2,400 participants in 2007. The Lifesavers Conference is an excellent means for finding someone
looking for a solution for fatalities and injuries due to elements that our technology addresses. Some of
the sponsors include AAA, Advocates for Highway and Auto Safety, The Alliance of Automobile
Manufacturers, Coalition for Traffic Safety, DaimlerChrysler Corporation, General Motors
Corporation, Governors Highway Safety Association, Harley-Davidson, Mothers Against Drunk
Driving, National Automobile Dealers Association, National District Attorneys Association, National
Highway Traffic Safety Administration, and Toyota Motor Sales, USA, Inc.
We also will provide an exhibit at safety conferences for school transportation such as the annual
conference held by National Association for Pupil Transportation
(http://www.napt.org/displaycommon.cfm?an=1&subarticlenbr=69). Trade shows, conferences, and
37
Don’t Forget Me: Passenger Safety System
advertising in auto magazines will also offer opportunities for manufacturers to become familiar with
our technology, ultimately leading to licenses.
Also we plan to Beta test our product and will provide it free to the Gloucester County Public Schools
to Beta test our product in several of their buses.
Furthermore, we will install free of charge our DFM system into several passenger vehicles for
additional Beta testing. We will recruit Beta testers at Old Dominion University’s daycare center.
Professors will be more willing to let us demo the DFM in their vehicle. Also, we can recruit expecting
women in Lamaze classes held by hospitals. We can also find Beta testers by going to other public
services that are advocates for safety like fire stations. After Beta testing for one year, we can use
Gloucester County Public Schools and owners of the demo passenger vehicles as advocates to help
promote our product to a much larger market in the auto industry.
38
Don’t Forget Me: Passenger Safety System
Appendix Items:
Management Plan (Patrick Markham)
Don’t Forget Me
Management Plan
1.0
November 13, 2007
Final
Version:
Date:
Status:
Program Identification
This Program Management Plan (PMP) is for the “Don’t Forget Me” system for ensuring that no child
is left in a vehicle unattended. The program will deliver the hardware – including all sensors (pressure,
heartbeat, temperature and CO2), processors, key rings and communication devices – software and
documentation for the Don’t Forget Me system. The Don’t Forget Me Project Team (DPT) is
responsible for the integration, acceptance testing and training of the Total Computing Environment.
Program Management Overview
Execution of the Program will be performed in accordance with the procedures defined by the set of
planning documents. These documents include Program Management Plan*, System Quality Program
Plan (SQPP), Software Management Plan (SMP), Configuration Management Plan (CMP),
Engineering Management Plan (EMP), Manufacturing Plan (MP), and Risk Management Plan (RMP)
(see Figure 1). The responsibilities of the Program Team, the capabilities of the system, and the
Program deliverables are detailed under the contractual provisions, as well as DPT’s technical,
management, and cost proposals.
39
Don’t Forget Me: Passenger Safety System
* This Program Management Plan shall be deemed to meet the contractual requirement of a Project
Management Plan.
Quality Program
Management
System Quality
Program Plan
Program
Management
Program
Management Plan
Engineering
Management Plan
Software
Management Plan
Data Management
Plan
Integrated Logistics
Support Plan
Configuration
Management Plan
Acceptance Plan
Installation Plan
Risk Management
Plan
Figure 1. Program Management
This Program Management Plan describes the management philosophy, program organization,
schedule, and major milestones that serve as the guide for execution of the Program. The PMP also
provides the customer and the quality team with the information they need to monitor and evaluate the
progress of the effort. This plan provides the following pertinent information:

Corporate Organization

Program Team Organization With Areas of Responsibility

Work Breakdown Structure

Program Planning

Progress Reporting and Team Management

Detailed Program Schedule and Milestones

Program Reviews
The Program Management Plan provides guidance for the content and execution of the following
plans:

Risk Management
40
Don’t Forget Me: Passenger Safety System

Engineering Management

Software Management

ILS Support

Data Management

Installation

Configuration Management

Acceptance Management
Corporate Structure
The entirety of Computer Productivity Initiative supports the Don’t Forget Me Program. In 1995, Old
Dominion University started the Computer Productivity Initiative from a grant by the National Science
Foundation to give Computer Science students the opportunity to develop solutions to real world
problems. The Don’t Forget Me Project Team formed in the Fall semester of 2007. The team will
either be directly involved in the development process of the Don’t Forget Me system or outsource
responsibilities on a contract basis. The following is Don’t Forget Me’s organizational structure:

Consultant – Janet Brunelle, Old Dominion University

Project Manager – Patrick Markham

Don’t Forget Me Program Office – The Don’t Forget Me Program Office will execute the
program and provide day-to-day senior management supervision, management, engineering,
and administrative resources necessary to manage and administer the Don’t Forget Me system.
Management Approach
Don’t Forget Me’s management goal is to work closely with the customer to fully understand the
system requirements and field a system that meets those requirements. The management approach to
executing contracts at Don’t Forget Me is based on the philosophy that successful Programs are delivered
41
Don’t Forget Me: Passenger Safety System
by goal-oriented teams. A Program Manager (PM) will lead the Don’t Forget Me team. The PM is
responsible for all planning, programmatic, technical, and financial aspects of the Program. The PM is the
primary Point of Contact (POC) for the customer. The primary duties include supervision of all planning,
scheduling, financial, and technical activities, and customer liaison. The PM is responsible for all
Program-related decisions and commitments with approval, as required, from the Corporate Management
Team.
A key element of Don’t Forget Me’s program management approach is customer involvement. Don’t
Forget Me encourages the customer to retain an active role in monitoring the progress of all aspects of the
Program. The customer is encouraged to discuss technical details directly with members of the Program
team, provide planning and schedule recommendations, and assist in resolution of technical and
programmatic issues. In order to facilitate customer involvement, Don’t Forget Me will provide access to
program information including, but not limited to:

Program Plans and Schedules

Program Status

Earned Value

Formal Review Material

Action Items

System Drawings and Documentation
Program Team
The Program Team is committed to provide the best value by delivering COTS, open architecture, and
low-risk systems at the lowest cost. This commitment is attainable because it is based on the re-use of
existing technology that is field-proven. Through strategic teaming and an extensive system selection
process, Computer Productivity Initiative has assembled a cohesive Program Team that is experienced
with the implementation of each component that will comprise the Don’t Forget Me system.
42
Don’t Forget Me: Passenger Safety System
Program Manager. Overall management responsibility for Don’t Forget Me is assigned to a Program
Manager who is responsible for planning and coordination of the day-to-day technical, contractual, and
financial aspects of the program. He is responsible for the generation and management of all program
schedules, for the coordination of program staff assignments and for coordinating all program
activities. His principal assistants are:

Hardware Specialist. The HS is responsible for system-level activities to ensure system
hardware meets the specification requirements. The HS is also responsible for the development
of system specifications, system design documents, interface documents, test plans, and
procedures.

Software Specialist. The SS is responsible for the development of system software functions as
defined in the system specifications. The SS is also responsible for integration of all system
components to meet the performance requirements of the system.

Documentation Specialist. The DS provides overall documentation direction for the Program
Team. The DS will ensure that everyone on the team has met the required documentation
specifications, and that each person is aware of the tasks he/she has been assigned. The DS will
also provide documentation of each meeting in which an overview of tasks assigned is given.

Risk Director. Responsibilities include managing the project risks. The RD must determine
what risks exist in the project, evaluate the severity and probability of those risks, and direct
efforts to mitigate them.

Financial Manager. The FM works in coordination with the rest of the team to devise a
specific and schedule based budget plan, that will be reviewed by each of the team members
and approved by both the PM and the customer. The FM will also determine the best agency to
pursue to get funding for the project.
43
Don’t Forget Me: Passenger Safety System

Marketing Director. The MD is responsible for developing a marketing plan that includes the
specification of an initial target market. The MS is responsible for the development of an indepth plan on how to advertise and sell Don’t Forget Me to the specified target market. The MD
must also determine the various risks involved and the best way to mitigate them.

Web Developer. The WD is responsible for the creation and maintenance of a product website
which will include the display of all relevant documents and presentations. The WD will update
the website as needed.
Program Duration
The Don’t Forget Me program is a 3-year project through delivery of the first vehicle fully
integrated with the Don’t Forget Me system. The Phase 0 schedule consists of a preliminary design
selection milestone in third quarter 2008. Production of the first fully integrated system will require
approximately two years, delivery of the first fully integrated system occurring in fourth quarter 2009.
Work Breakdown Structure
The program Work Breakdown Structure (WBS) reflects the budgeted cost versus resources
required to complete each task. The WBS phase numbers are integrated as part of the master program
schedule. Assuming SBIR funding, the budget will be carefully planned out against the set deadlines
set by SBIR guidelines. The budgets are created by the Financial Manager, reviewed by the Don’t
Forget Me program and set by the Program Manager. The WBS will be used to mark the different
milestones throughout the phases and to make sure that the team in on time and on budget. The WBS
management tool that Don’t Forget Me will use is Microsoft Project 2003.
Program planning
The Don’t Forget Me Program Team office will maintain the program master schedule. The
master schedule contains a line item for each WBS element and will be used to track the progress of
44
Don’t Forget Me: Passenger Safety System
each element. All deviations from the master schedule must be coordinated with the program office. It
is the responsibility of each team member to call attention to possible schedule deviations at the earliest
opportunity. The program office will coordinate the program schedule with Computer Productivity
Initiative. The program will be developed in phases; within each phase, formal reviews will play an
integral part in monitoring program progress. All formal reviews will be announced four weeks in
advance of the starting date.
Don’t Forget Me will take a “top down approach” to the Program Schedule, meaning that we
will pace our workload to fit the overall Program requirements. Particular attention will be given to
timely milestone completions. It is recognized that the schedule is particularly tight, containing critical
program milestones during the first year, and adequate personnel will be available in order to keep the
program moving forward.
Progress Performance Assessment
All Don’t Forget Me team members will participate in progress reporting and team management.
Don’t Forget Me will track technical and financial progress of the program. Reviews will be held
monthly or as mutually agreeable between Computer Productivity Initiative and Don’t Forget Me.

Report on progress to date

Present work to be performed during the next month

Present status of all deliverables and review planned delivery dates

Plan and coordinate activities, including new review date

Discuss technical or programmatic issues as necessary.
In preparation for the meetings the Don’t Forget Me Program Manager will collect the current status
data on relevant on-going activities, progress against schedule and budget, and planned activity for the
next reporting period. Quality reviews of all program documentation and procedures will be held
periodically. In particular, the quality program will be involved with program deliveries and milestones
45
Don’t Forget Me: Passenger Safety System
and will work off of the master program schedule to plan program audits. Technical, financial and
quality progress and status reporting will be conducted according to the following general guidelines.
Technical Progress and Reporting
The schedule for the program is established during the planning phase and monitored
throughout the performance period. The schedule contains an entry for each WBS element. The
percentage of completion for each WBS element is determined as necessary to manage program
progress and is reviewed at least quarterly during the General Manager’s review.
Financial Management and Reporting
The financial profile for the Program is established during the planning phase and monitored
throughout the performance period. This profile is generated by assigning accounting phase numbers to
every Program activity that has been identified as a scheduled event. A budget representing labor costs,
materials purchase, and other expenditures (such as travel expenses) is then prepared for every phase. The
schedule and budgets are then integrated to provide a spending profile for the phase. The Program
spending profile represents a summary of phase spending profiles.
The PM is provided an information package that identifies the phase numbers assigned to each activity,
the corresponding budgets and schedules, the overall spending profile for the program, and a synopsis of
all major deliverables and milestones specified in the contract. The PM uses this information, combined
with an on-line financial summary of the Program to track its financial status on a weekly basis. An
updated spending profile is provided automatically by the Contracts Administrator on a monthly basis, or
upon request from the PM. The PM uses the financial summary in conjunction with his assessments of
technical progress to track the overall status of the efforts (please see the Financial Plan for more
information).
46
Don’t Forget Me: Passenger Safety System
Earned Value
Earned Value Ratios will be reported as required. At a minimum, Don’t Forget Me will
determine earned value quarterly at the overall Program level and will report at the 2nd level of WBS
indenture in order to provide additional information.
Ratios will be reported in the form of the Schedule Performance Index (SPI) and the Cost Performance
Index (CPI). Ratios below 0.90 will be explained in further detail.
SPI is to be calculated as follows:
SPI = BCWP (Budgeted Cost of Work Performed)
BCWS (Budgeted Cost of Work Scheduled)
CPI is to be calculated as follows:
CPI = BCWP (Budgeted Cost of Work Performed)
ACWP (Actual Cost of Work Performed)
Don’t Forget Me will use Microsoft Project Program Manager software in order to calculate the ratios.
On a monthly basis, actual costs will be entered into the software for comparison with the budget. A
baseline of work to be performed will be established in the software and will provide the BCWS.
Milestones will be applied against the various WBS elements, and % complete status of the milestones
will be updated on a monthly basis. Based upon % complete, the software will calculate BCWP, or
earned value, at the individual WBS level and determine the earned value at the overall program level.
Please see the Financial Plan for more information.
Quality Process and Reporting
Quality management on the program will be a team effort. The Quality System Manager will
coordinate conduct, quality reviews, and audits. The PM is ultimately responsible for the development
and implementation of the System Quality Program Plan. The SQPP is an umbrella plan which
incorporates the quality programs of the program team members. The SQPP describes a team quality
47
Don’t Forget Me: Passenger Safety System
concept, including Process Coordination and Quality Evaluators. Team members are responsible for
performing the processes required to complete Program tasks. Quality Evaluators are responsible for
verifying that the development, production, and handling of all documentation, software, and hardware
are performed in accordance with the SQPP and its component processes. The team is also responsible
for conducting periodic reviews and evaluations of work-in-process; attending in-house test events, and
supporting in-house Program reviews. All planned quality program activities and quality evaluations
(internal audits) are submitted to the PM for review. Please see the Evaluation Plan for more details.
Monthly Progress Report
Don’t Forget Me will submit a monthly progress reports. The report shall cover, at a minimum, the
following:

Progress Summary;

The variance statement;

Critical Path Analysis;

Milestone Deliverables, planned actual and forecast;

Earned Value Schedule and Cost Performance Indices;

Dependencies: a ‘critical items list’ of all items, whether or not the Contractor’s direct responsibility,
which could jeopardize timely completion of the work or any significant parts of the programme;

Risk Status: update of risk register;

Look Ahead (Future action and Forecast);

Resource Profile;

Work Package/Activities planned, actual & forecast status;

Milestone/Deliverables planned, actual & forecast status;

Configuration Change Control issues;

Quality Actions (Reviews, audits);

One Page Plans and Reports summarising the above for inclusion in the Purchaser’s monthly report; and
48
Don’t Forget Me: Passenger Safety System

Commercial: amendments to Contract status report; No later than meeting + 10 working days.
Reviews
Reviews will play an integral part in the management and monitoring of all phases of the Don’t
Forget Me Program. Informal reviews with the Program team members will be held at all levels on a
weekly basis to ensure that the program stays on track. Formal technical reviews will be held to ensure
that the program is proceeding as planned. The types of reviews, their purpose and presented
information are addressed in the following paragraphs.
Program Management Reviews
Program Management Reviews (PMRs) will be conducted with Don’t Forget Me and subcontract
representatives. The first PMR will be conducted in January 2008; thereafter PMRs will be conducted
approximately every six months (immediately preceding each technical review). The PMRs are
scheduled to discuss programmatic issues related to the development and implementation of the Program.
The reviews will provide the opportunity to review the progress of the effort; as well as to conduct
milestone reviews of deliverables, and identifies and resolves any issues that may arise during the
execution of the tasking.
The PM will ensure that all program-related information required to meet the objectives of the
review are prepared and delivered not later than two weeks prior to the scheduled review date. The PM
will also be responsible for identifying the Don’t Forget Me Program Team personnel who will attend
the review. The PM will attend all Program Management Reviews. The following information will be
prepared in support of each PMR. Recorded during the review and delivered before the completion of
the review.
49
Don’t Forget Me: Passenger Safety System
Technical Reviews
Formal technical reviews will be conducted on the dates specified in the master schedule. The
reviews will be held jointly with Computer Productivity Initiative, Don’t Forget Me team members and
sub-suppliers as necessary. An agenda and review material will be submitted to Computer Productivity
Initiative two weeks prior to the scheduled meeting. Review meeting minutes will be delivered before
the completion of the review. The objectives for each review are outlined below.
Reviews will be held to validate the direction taken for the design, development and test of the system.
The System Requirements Review (SRR), Preliminary Design Review (PDR), and Critical Design
Review (CDR) will be formal reviews held at Dont Forget Me’s facility. The Test Readiness Reviews
(TRR) will be formal reviews held prior to HAT & SAT.
System Requirements Review is conducted to ensure that the Program team fully understands the
system performance requirements specified in the System/Segment Specification. A detailed review of
requirements for the system and each subsystem will be reviewed. The System/Segment Specification
(Technical Specification) will be used in the review.
System Design Review is conducted to present and review the system design. System requirement
allocation to each system component will be discussed. The general approach to be taken for the
integration of each system component will be presented. The documents listed below will be used in the
review. This will be an informal review. The data will be included in the PDR.

System/Segment Design Document

System Interface Design Document
Software Requirements Review is conducted to review the software specification and interface
requirement specifications. This review will be conducted as part of the PDR.
50
Don’t Forget Me: Passenger Safety System
Preliminary Design Review is conducted to present the preliminary design of the Program System. The
functional requirements of each subsystem will be discussed in detail. The following documents will be
used in the review:
Critical Design Review is conducted to review system integration issues. In particular the review will
focus on system interfaces in preparation for Subsystem FAT.

Test Readiness Reviews are held to determine if the system is ready to proceed to the next level
of test. Test configurations and results from the previous test efforts will be presented. The test
report from the previous test will be used in the review.
Quality Reviews
The PM supported by the quality system manager (QSM) will establish the time and identify
attendees for all formal reviews. He will also coordinate with the appropriate managers to conduct quality
reviews at key program milestones, and in preparation for formal reviews with the customer. Informal
peer review and engineering planning meetings will also be held at the discretion of each subsystem
manager to discuss technical issues, conduct internal comment reviews, and provide technical guidance
to members of the Program team. As part of the quality activities for the program, the quality team will
conduct informal reviews to:

Evaluate the processes used by the Program team members to perform program tasks;

Evaluate deliverable products for compliance with contract requirements;

Evaluate work-in-process during engineering reviews;

Document results of each evaluation; and

Recommend corrective and preventive actions if necessary.
51
Don’t Forget Me: Passenger Safety System
Evaluation Plan (Patrick Markham)
Don’t Forget Me
Evaluation Plan
1.0
November 13, 2007
Final
Version:
Date:
Status:
Purpose
This document defines the top-level parameters to measure success for each phase of the Don’t
Forget Me project. Phase deliverables will be evaluated based on the project management criteria of
time, cost, scope, and quality.

Time, as measured by the baseline project plan.

Cost, as measured by the budget plan by phase.

Scope, as measured by the requirements document.

Quality, as measured by quality control plan, customer adoption rate and customer satisfaction.
Phase 0
The project idea was developed in Phase 0 and research was performed to clearly identify our
objectives, goals, and risks. The Work Break Down Structure (WBS) was created for each Phase of the
project. Plans have been developed to guide each phase of the project.
In this phase the initial SBIR proposal will be created along with a final proposal presentation
and product website.
52
Don’t Forget Me: Passenger Safety System
Main Deliverables
SBIR Proposal
Proposal Presentation
Product Website
Time
The project plan developed in Microsoft Project contains the WBS, schedule, and cost
estimates. The project plan defines the date at which these deliverables should be completed. If these
deliverables are completed by the estimate completion date, then the criteria will have been deemed
successful. The team leader ensures all project members are completing tasks within the deadlines of
the milestones (for CS410) in the WBS. To prepare for the main deliverables, listed above, there have
been milestones that delivered presentations: conception (individual), feasibility (team), and milestone
(team). Assignments have been posted to the team's Wiki Page website to prepare for the Product
Website and development team coherence and communications.
Cost
Since there is no cost for this phase, this criteria will not be used to measure success.
Scope
The scope will be measured by comparing the grading criteria against each deliverable. If each
deliverable meets each graded criteria, and Phase 1 funding acquired, then this criteria is deemed a
success.
53
Don’t Forget Me: Passenger Safety System
Quality
An independent panel will determine quality of the proposal presentation. This panel will
evaluate the presentation based on the grading criteria established. An average score of 90 will
determine that success of this deliverable.
The SBIR proposal and product website will be evaluated by the CPI advisor. A grade of 90 or more
for each deliverable based on the grading criteria will indicate a success.
Peer evaluations have been completed after each team milestone. Evaluation is performed by team
members to measure participation, quantity and quality of each team member. Weekly discussions and
constructive criticism take place in CS410 class to improve quality of deliverables.
Phase 1
In this phase a lab prototype will be developed and demonstrated to a potential customer(s). In
addition, SBIR Phase 2 proposal will be developed. Success will be measured by the satisfactory
completion of these three deliverables. Evaluation during this phase will also consists of bi-weekly
team meetings to ensure that the project is progressing as planned and the procured hardware and
software components are correctly implemented. Formal evaluations will be conducted each month or
as often as necessary to ensure we stay within the guidelines of the WBS.
Initial development of product software will be completed in this phase. Our initial product
software includes:

Don’t Forget Me Product Website (HTML)

Prototype of the Processor’s Software for Simulation

Prototype of the Key Ring’s Software for Simulation
54
Don’t Forget Me: Passenger Safety System
We will follow the work flows of analysis, design, implementation and validation.
We will also be developing documentation for our product: requirements document, test simulation
documentation user manual, and refinement of our plans.
Main Deliverables
Lab Prototype
Customer Demonstration
SBIR Phase 2 Proposal
Time
The project plan developed in Microsoft Project contains the WBS, schedule, and cost
estimates. The project plan defines the date at which these deliverables should be completed. If these
deliverables are completed by the estimate completion date, then this criteria will have been deemed
successful.
Cost
The funding plan determines the cost estimates of each phase. The human and hard resource
actual costs will be compared to the budgeted costs in the funding plan. If the actual costs are with 5%
of the budgeted costs, then this criteria will be deemed successful.
Scope
The scope will be measured by comparing the grading criteria against the SBIR Phase 2
requirements. If SBIR contains all the required items, then the criteria will be deemed successful. The
lab prototype will be measured against the requirements document developed in Phase 1. If the
55
Don’t Forget Me: Passenger Safety System
prototype contains all of the required functionality and Phase 2 funding acquired, then the criteria will
be deemed successful.
Quality
The SBIR decision board will determine quality of the proposal presentation. If the decision
board grants the proposed funding, then the SBIR proposal will be deemed successful. This criteria for
the lab prototype will be deemed successful if it meets all of the requirements in the requirements
document and meets the performance requirements also in that document.
We will begin evaluation with code reviews of each module for proper structure and syntax. After
successfully passing code reviews, we will begin testing of each module. We will end the evaluation for
each module after successful testing. We will have evaluations for every module being integrated into
the system. We measure success when we have completed each evaluation successfully and in
accordance with the WBS time frame, and the prototype passes all tests in the test plan.
Phase 2
Phase 2 is where the project shifts into refinement and development of the actual Don’t Forget
Me system. Evaluation during this phase will continue much like in Phase 1. Bi-weekly meetings will
be held to determine if the project is on schedule and within budget. Testing plans for the production
(non-prototype) version of Don’t Forget Me will be drafted to ensure quality assurance and software
components will be vigorously tested and the results of those tests will be discussed at the bi-weekly
meetings to work out any problems. In this phase we will also conduct a beta test and success will be
declared when the beta test results in few errors or errors that are of little significance. Feedback will
also facilitate refinements to our product and support materials. Formal evaluations will be conducted
56
Don’t Forget Me: Passenger Safety System
each month or as often as necessary to ensure we stay within the guidelines of the WBS.
Further development of the product software will occur in this phase. This development includes:

Enhanced Don’t Forget Me Product Website

Finalization of Software Process Flow, given testing results
Main Deliverables
A vehicle with an operational Don’t Forget Me system fully integrated.
Time
The project plan developed in Microsoft Project contains the WBS, schedule, and cost
estimates. The project plan defines the date at which these deliverables should be completed. If these
deliverables are completed by the estimate completion date, then this criteria will have been deemed
successful.
Cost
The funding plan determines the cost estimates of each phase. The human and hard resource
actual costs will be compared to the budgeted costs in the funding plan. If the actual costs are with
10% of the budgeted costs, then this criteria will be deemed successful.
Scope
The prototype will be measured against the requirements document. If the prototype contains
all of the required functionality from the document, then the criteria will be deemed successful.
57
Don’t Forget Me: Passenger Safety System
Quality
The criteria for Don’t Forget Me in Phase 2 will be deemed successful if it meets all of the
requirements in the requirements document, including performance. The prototype must pass all tests
in the test plan. Once the test plan execution has been completed with no known bugs, then the criteria
will be deemed successful. The criteria for Don’t Forget Me will be determined by a beta test market.
After the beta test, a study will be conducted by surveying the test market participant(s). The support
materials must also undergo a satisfaction beta test survey.
Phase 3
In this phase, the main focus will be on further refinement of the Don’t Forget Me product
based on the beta testing and moving the project into full time production. To ensure quality, evaluation
of the production process will be a key factor. Additionally, evaluation of the marketing strategy will be
conducted to ensure that we are targeting the correct market. Formal evaluations will be conducted
each month or as often as necessary to ensure we stay within the guidelines of the WBS. Success in this
phase will be determined by sales volume and profit margin. In addition, we will be evaluating
customer feedback to gage customer satisfaction.
Main Deliverables
Enhanced Don’t Forget Me Website
Product Rollout
Time
The project plan developed in Microsoft Project contains the WBS, schedule, and cost
estimates. The project plan defines the date at which these deliverables should be completed. If these
58
Don’t Forget Me: Passenger Safety System
deliverables are completed by the estimate completion date, then this criteria will have been deemed
successful.
Cost
The funding plan determines the cost estimates of each phase. The human and hard resource
actual costs will be compared to the budgeted costs in the funding plan. If the actual costs are with
10% of the budgeted costs, then this criteria will be deemed successful.
Scope
The scope of the rollout is measured by the number of vehicle models in which manufacturers
install the Don’t Forget Me system, and by the Marketing Plan which calls for a 10 year strategy to
target and acquire 10% of all vehicle models sold in the United States. To help reach this 10 year goal,
the break even analysis plans for $2.8 million in sales in a two year period. If we accumulate $2.8
million in sales after two years, and capture 10% of the market after 10 years, this criteria will be
deemed successful. Refer to the Funding and Marketing Plans for additional details.
Quality
If the test market survey of the product’s quality and usefulness as compares to the goals and
objectives of the project is favorable, then this criteria is deemed successful.
59
Don’t Forget Me: Passenger Safety System
Resource Plan (David Ballentine)
Don’t Forget Me
Resource Plan
1.0
November 13, 2007
Final
Version:
Date:
Status:
The purpose of this plan is to show what resources are needed, and the costs attributed to each.
The resources needed in the development of the Don’t Forget Me are outlined here, broken up by the
different phases.
Phase 0:
There is no resources needed in phase 0.
Phase 1:
60
Don’t Forget Me: Passenger Safety System
This phase is the first phase of the project with actual resources. Many of these resources go
towards the prototype that will be built during this phase. These include the section at the top of this
chart. The other resources needed include computer hardware and software to work on the software
and algorithms of the product. Installation equipment will also be needed in this phase to install and
test the finished prototype. A Test Dummy will be used to test the prototype.
Phase 2:
In this phase, several more prototypes will be built for actual real world cases. For this reason
there will need to be many prototype sensors. Additionally, assembly supplies will be needed to install
these prototypes. Both a Bus and a Van will also be purchased for the purpose of installing the
prototype into these vehicles.
61
Don’t Forget Me: Passenger Safety System
Phase 3:
In this final phase, six workstations are needed for continued development. Additional supplies,
such as office equipment, will is also be accounted for. The most money is allocated towards
marketing.
62
Don’t Forget Me: Passenger Safety System
Marketing Plan (Daniel Holloway)
Don’t Forget Me
Marketing Plan
1.0
December 5, 2007
Final
Version:
Date:
Status:
Purpose
The purpose of this document is to provide a plan to identify the market and to define strategies
in marketing our product.
Market Analysis
In the year 2007, there were 652 incidents involving kids and automobiles. There were reports of
804 children involved in which there were 202 fatalities. Furthermore, there were reports of 9,100
children treated in emergency rooms due to non-traffic incidents. There are several issues contributing
to non-traffic incidents involving vehicles and children. These include children left in a vehicle’s
passenger compartment in hot weather or who lock themselves in the trunk of a vehicle, children
strangled by a vehicle’s power window or sunroof, children killed or injured as a result of a vehicle
backing up, and children killed or injured as a result of vehicle-generated carbon monoxide. Out of the
total number non-traffic fatalities in the year 2005, 23% were due to children left alone in vehicles
during hot conditions. Also, it is important to point out that the 49% of child fatalities due to being
backed over by a vehicle will diminish because of new solutions coming on line that utilize camera
technology. This information was not present at the time these statistics came out; therefore, the
63
Don’t Forget Me: Passenger Safety System
percentage will decrease for being backed over by a car, however, the percentage due to hyperthermia
will increase. One can see the percentages in the chart below.
(Diagram: Nontraffic noncrash fatalities)
It is life threatening when someone’s body temperatures reaches above 104°F. Also, when
someone’s body temperature reaches 106°F, brain death begins. When one’s body temperature
reaches 113°F, death is nearly certain. It does not take long for a vehicle to reach these conditions in
the summer. When the temperature outside is 80°F the temperature inside is 80°F, in 10 minutes the
temperature inside inceases to 99°F, within 20 minutes the temperature is 109°F, within 30 minutes
the temperature inside is 114°F, within 40 minutes the temperature is 118°F, within 50 minutes the
temperature is 120°F, and within 60 minutes the temperature is 123°F.
Internal temperatures above 122°F will cause rigidity in the muscles and certain, immediate death.
64
Don’t Forget Me: Passenger Safety System
Temperature vs Time
Temperature
140
120
100
80
Temperature outside
is 80 degrees
60
40
20
0
0
10
20
30
40
50
60
Time
(Diagram: Chart of temperature vs. time (time in minutes))
The amount of passenger vehicles produced annually is around 4.8 million and around 5 million
sold annually. The reason for more cars being sold than manufactured, is cars that were not sold in
previous years are sold in current year statistics. School buses are the largest mass transit program in
the US. There are over 440,000 school buses transporting more than 24 million children every day of
the school year. This indicates that there exists a large potential market for enhanced child safety
features. Safety is a concern in both markets including passenger car manufacturers, and bus
manufacturers. With non-traffic fatalities due to heat on the rise, we represent a new safety system to
help prevent this tragedy from occurring in vehicles. School buses and seat belts are a recent topic
under debate. While most states do not enforce school bus seat belts because of the effort involved in
maintaining them, our device will help prevent incidents involving leaving children on buses
unattended, and can be used to help keep children in their compartment.
There are a large number of new vehicles sold yearly including cars and buses. Our system
installed in a vehicle offers an enhanced safety solution for new vehicles. Furthermore, we will focus
on obtaining a car manufacturer to license our patent on our technology. In our license agreement, we
will receive royalties on the number of our systems installed in their vehicles.
65
Don’t Forget Me: Passenger Safety System
Table 1-15:
Annual U.S. Motor Vehicle Production and Factory (Wholesale)Sales (Thousands
of units)
1997
1998
1999
2000
2001
2002
2003
2004
2005
Production, total
12,131
12,003
13,025
12,774
11,425
12,280
12,087
11,960
11,947
Passenger cars
5,934
5,554
5,638
5,542
4,879
5,019
4,510
4,230
4,321
Commercial vehiclesa
6,197
6,448
7,387
7,231
6,546
7,261
7,577
7,731
7,625
12,223
12,112
12,127
12,527
11,108
U
U
U
U
Passenger cars
6,070
5,677
5,428
5,504
4,884
U
U
U
U
Commercial vehiclesa
6,153
6,435
6,699
7,022
6,224
6,964
7,143
7,467
7,767
Factory (wholesale) sales, total
(Table: number of vehicles produced and sold)
The two class types that capture 90% of school buses sold are Class C and Class D. Type C is
identifiable by the engine that protrudes at the front of the vehicle, ahead of the front windshield. It
typically weighs 12-15 tons. The driver's seat and main student entrance door are located behind the
front axle. Type D is identifiable by a body that extends the full length of the chassis, giving it a
characteristic "flat-nose" design. The driver's seat and primary entrance door are forward of the front
wheels, with the engine located at either the front or rear of the vehicle.
Below, one can see two charts indicating the number class C buses manufactured, and the class D
school buses manufactured. They both show an increase over the past years. This indicates that the
market for school buses is increasing not decreasing.
66
Don’t Forget Me: Passenger Safety System
Type D transit-style production saw 8,505 buses built, an increase of 789 units or 10.2
percent over a year ago.
Price Point for Customer
With the diminishing car sales in recent months, each car maker is looking for ways to gain an edge
over their competitors. Vehicle safety can give them edge. The cost compared to the average cost of a
passenger vehicle of $25,000 is minimal. The sales increase for a vehicle installed with our safety
67
Don’t Forget Me: Passenger Safety System
system out weighs the cost for them. Also, the consumer buying the vehicle from the dealership will
not be affected greatly because the cost is negligible. With car sales decreasing in recent months, our
safety system installed in a vehicle will show the consumer their dealerships are dedicated to producing
a safe vehicle that will help increase sales by gaining the consumer’s confidence.
There has been a debate recently about installing seat belts into school buses, which indicates a
more concern for safety on, buses, though buses maintain a good safety record of our school bus transit
program. Additionally, school bus manufactures may want to show a safety commitment with their
buses and may want to offer a better product. The DFM will provide bus manufacturers with a less
intrusive system, and one that requires little assistance from the bus driver. Schools buses are being
critiqued for their safety features. School bus manufacturers will gain an edge by installing the DFM,
and having a device to monitor students in a compartmentalize environment. Also, the cost compared
to the average cost of a school bus of $70,000 is minimal.
Profit
With the available passenger vehicles of 4.8 million being produced annually, there are around $1.3
billion dollars available to be made in the passenger car market. The cost to have enough systems to
cover the available vehicles will be $2.8 billion. In the licensing agreement, we will receive in
royalties $50 per system installed in vehicles. With estimates capturing around 1 % of the market
available (50,000 vehicles) for the first out year and deducting the total cost of $1,636,702, the total
profit will be $863,298. For the second out year, expecting 100,000 vehicles to have the DFM installed
and deducting the total cost of $1,124,468, the total profit will be $4,738,830. Furthermore, in the third
out year, expecting 125,000 vehicles to have the DFM installed and deducting the total cost of
$1,124,468, the total profit will be $9,864,362. The number of school buses that were manufactured has
risen to 47,915 in the year 2006 from 25,690 buses in the year 2005. This shows a 4.6 percent increase
68
Don’t Forget Me: Passenger Safety System
in buses made. A typical class C 64 passenger bus cost around $70,000. Using the year 2006 numbers,
there is $5.9 million to be made in profit the first year if the increase is the same in production, there is
$6.1 million to be made the second year. The cost to have enough systems available will be $65
million. We estimate capturing around 1 % of the market available (500 buses) for the first two years,
the total made will be $25,000 the first year. We will have $512,000 invested in hardware, personnel,
and other cost including patent processing cost of $10,000.Estimates are for the car manufacturers to
pay a $50 royalty fee and for each installation of the system. The money left over should be put back
into the system for the year. After enduring the cost of $512,000 from phase III and anticipating other
costs for the first out years, we anticipate we will still show profits close to $863,298 in the passenger
vehicle market.
The cost for Phase I includes $21,953 for hardware/software development, and $72,352 for labor
which totals $94, 305. During Phase II the hardware/software development will cost $47,371 and
$620,256 for labor. The total cost comes to $667,627 for Phase II. The Phase III hardware/software cost
will be $187,000 and labor cost will be $325,234. The total cost for the first 6 months into Phase III
will be $512,234. During Phase I, we will develop a prototype and prepare the Phase II grant proposal.
During Phase II, we will conduct extensive testing of the system and approach potential customers.
From the start of Phase III we anticipate showing a profit after the first year. The total cost for Phase I
and II will be $761,932 which the SBIR grants for Phase I and II will cover all the cost. Furthermore,
the profit after deducting the cost for Phase III the first year after the start of Phase III will be $863,298
from the car manufacturing industry. Most of this money should be put back into research and
developing new innovative enhancements to our technology so we can pursue additional patents.
Furthermore, we will show large profits the second year which could close in on $1 million. Below is a
chart showing the return on investment for the out years.
69
Don’t Forget Me: Passenger Safety System
40000000
35000000
30000000
25000000
20000000
15000000
10000000
5000000
0
Out Year 4
Out Year 3
Out Year 2
Sy
st
em
s
I
RO
To
ta
lC
os
To
t
ta
lR
ev
en
ue
Out Year 1
So
ld
Dollars
Out Years ROI
(Diagram: Chart showing profits over 24 month period)
Passenger
Vehicles
Bus
Number of units
50,000
500
Profit ($50/unit)
$2,500,000
$25,000
Total Cost
$1,636,702
0
Total Net Profit
$863,298
$25,000
(Diagram: Chart showing total profits for first year)
In the above chart, one can see the how much it takes to produce, how much the profit, and the
total cost for the vehicles we plan to market for the DFM. These are minimal compared to anticipated
sales with the systems installed. The average cost of a passenger vehicle is $25,000 and the average
cost of a $64,000 school bus is $70,000.
70
Don’t Forget Me: Passenger Safety System
Benefits for the Customer
Advantages for Car Manufacturers

Improves car sales that have dropped in recent months.

Improves confidence in consumers that safety is a priority for their vehicles.

Reduces number of fatalities/injuries occurring in vehicles they manufacture.
Advantages for Bus Manufacturers

Improves confidence in school districts that safety is a priority for their buses.

Improves confidence in the transporting and delivery of the school’s precious cargo.

Reduces liability cases occurring from students being killed or injured.

Reduces risks from school bus driver’s negligence.
Advantages for Consumers

Reduces fatalities and injuries due to leaving children behind in vehicle.

Improves confidence of parent/caregiver for transporting and delivery of children/elderly.

Reduces the number of liability suits due to caretaker’s negligence.

Possible vehicle insurance discount for added safety features.
Marketing Strategy Advertisement
We will patent the DFM system and have the car manufacturer license the technology paying a
fee for every unit installed in a vehicle over the lifetime of the patent. In the initial phase, we will
provide an exhibit at national safety conferences such as the Lifesavers 2008 Conference (
http://www.lifesaversconference.org/). We also will provide an exhibit at safety conferences for school
transportation such as the annual conference held by National Association for Pupil Transportation
(http://www.napt.org/displaycommon.cfm?an=1&subarticlenbr=69). Also we will need to Beta test our
product and will provide it free to the Gloucester County Public Schools to Beta test our product in
71
Don’t Forget Me: Passenger Safety System
several of their buses. Furthermore, we will install free of charge our DFM system into several
passenger vehicles for further beta testing. We will recruit these Beta testers at Old Dominion
University’s daycare center. Professors will be more willing to let us demo the DFM in their vehicle.
Also, we can recruit expecting women in Lamaze classes held by hospitals. We can also find Beta
testers by going to other public services that are advocates for safety like fire stations. After Beta
testing for one year, we can use Gloucester County Public Schools and owners of the demo passenger
vehicles as advocates to help promote our product in a much larger market in the car industry.
Competition
72
Don’t Forget Me: Passenger Safety System
(Diagram – Competition Matrix)
The above competition matrix shows what is offered from the competition compared to what
the Don’t Forget Me system has to offer. The Child Presence Device utilizes pressure and distance
sensors, and has a means for alarming the caregiver. The Halo Baby Seat Safety System provides all
that the Child Presence Device has to offer plus it detects the temperature. The Baby Alert’s Child
Minder System provides all that the Child Presence Device has to offer and provides an automatic selftest. It does not utilize temperature sensors to detect the temperature. The Volvo S80 Heartbeat Sensor
only offers the means for detecting a heartbeat. It does not have a method to differentiate between a
human heartbeat and another living animal. The VTI heartbeat sensor only offers the same as the Volvo
S80 heartbeat sensor. It uses accelerometers to detect small vibrations and utilizes software to detect
that it is a heartbeat. Our Don’t Forget Me System offers everything the competitors offer plus a light
and vibration indicator, auto temperature control, and a CO2 sensor.
The Child Presence Device, Halo Baby Seat Safety System, and Baby Alert’s Child Minder
System offer a low cost product. The Child Presence Device cost is around $35 but has not reached the
market yet. The Halo Baby Seat Safety System retail cost is $129 but one can purchase from the
Internet for $89. The Baby Alert’s Child Minder System can be purchased for $89.99. The Volvo
heartbeat sensor comes with the Volvo S80 and it adds $400 to the cost of the vehicle.
Advantages our DFM offers over other competitors is a more accurate way of detecting an
unattended child’s’ presence in a vehicle by analyzing more information and mitigating the chance of a
false alarm.
The cost of our DFM will be $50 a unit installed in the car manufacturer’s vehicles which is
minimal cost compared to the vehicle plus the accuracy is better than our competitors. With better
accuracy, the DFM minimizes chances for fatalities or people being serious injured in one of their
73
Don’t Forget Me: Passenger Safety System
vehicles that can be devastating to there existence. Added safety features in buses have been
discussions between school agencies, and bus manufactures as they are always looking for safer school
buses even though school buses are one of the safest transit programs.
Conclusion
DFM will target safety conscious car and bus manufacturers by offering a system to monitor
numerous vital conditions using sensor technology and complex software. The purpose is to reduce
fatalities and serious injuries and improve vehicle sales and due to individuals being left unattended in
the vehicle for an extended period of time. There is not a product on the market to sense all vital
conditions in order to accurately detect the presence of a child in a vehicle unattended over time. The
DFM will provide everything our competitors have plus add additional features including CO2 sensor,
light/vibe indicator, and an auto temperature control mechanism. With the DFM monitoring all of these
conditions, it will mitigate the chance of false alarms. We will patent the DFM system and have the car
manufacturer license the technology paying a fee for every unit installed in a vehicle over the lifetime
of the patent. By Beta testing in passenger vehicles owned by professors utilizing ODU’s daycare, we
will gain advocates to help our credibility. The potential for large profits exist in an industry where
safety is a priority. Furthermore, the DFM offers a better solution and the cost is minimal to the
vehicles cost.
References
Kids and Cars http://www.kidsandcars.org/
EPA Gov http://www.epa.gov/hiri/about/pdf/EHEguide_final.pdf
Thingamababy http://www.thingamababy.com/baby/2007/07/babysafety.html
Public School Buses http://www.schoolbusinfo.org/
Supt’s Memo http://www.pen.k12.va.us/VDOE/suptsmemos/2006/reg010.html
Bus Regulations http://www.pen.k12.va.us/VDOE/Finance/VAPT/regulations.htm
Temperature over time in a vehicle http://ggweather.com/heat/hot_car_00min.jpg
74
Don’t Forget Me: Passenger Safety System
Children left on School Buses http://www.stnonline.com/stn/top_stories/left_behind1.htm
Funding Plan (Hernan Gonzales)
Don’t Forget Me
Funding Plan
1.0
December 5, 2007
Final
Version:
Date:
Status:
In order to make Don’t Forget Me a success, we must provide enough revenue to cover the cost
of the project. The Blue team will submit a Small Business Innovative Research (SBIR) grant proposal
for Phase I & Phase II to the National Science Foundation (NSF). Phase III funding will be provided
though venture capital investment.
Phase 0
The initial phase (phase 0) does not have any amount involved since Old Dominion University
supply the Don’t Forget Me project with the resources needed. This phase will end when the semester
ends on December 14, 2007.
Phase I
The Don’t Forget Me team will submit a proposal for funding to The National Science
Foundation (NSF) SBIR. The maximum amount that the agency will grant us for the Phase I is
75
Don’t Forget Me: Passenger Safety System
$100,000. Our expected cost for the personnel and hard resource is $94,305 (see DFM budget chart
document for itemized budget). We will use the funding to build a single prototype to make sure every
device in the system works perfectly. Our estimated time to finish the project is 5-6 months.
Phase II
After the Phase I, we will request more funding from National Science Foundation (NSF) SBIR
again to develop the next phase, which is phase II. The maximum amount that NSF will grant us for
this phase is $750,000. This phase is the continuation of the previous phase, but the testing will be
more intense and detailed. We will test the system in a wide variety of vehicles, which include a regular
car, pickup, SUV, van, and bus, to study the effectiveness of our system in different conditions. The
intense testing will last for 2 years, and our expected cost for this phase is $667,127 (see DFM budget
chart document for itemized budget).
Phase III
We will begin contacting the car or bus manufacturers to make a preliminary contract
agreement with them. Our income will be based on the licensing of our product. Basically we make
percentage profit for each vehicle that has implementation of our product. However, if we still need
more funding, we will apply for a small business loan. Contacting the manufacturers and making
contract will be approximately 6-12 months. Our expected cost for the Phase III is $512,234 (see DFM
budget chart document for itemized budget).
TOTAL BUDGET
Phase I
Phase II
Phase III
Total
$94,305
$667,627
$512,234
$1,274,166
OUT YEARS
76
Don’t Forget Me: Passenger Safety System
Outyear
1
2
3
4
Systems Sold
50,000
100,000
125,000
137,500
Total Cost
$1,636,702
$1,124,468
$1,124,468
$1,124,468
Total Revenue
$1,987,766
$5,863,298
$10,988,830
$16,739,362
ROI
$863,298
$4,738,830
$9,864,362
$15,614,894
* Assumes a licensing fee of $50/vehicle, that a deal to install the system on 50,000 vehicles will be
reached by the end of Phase 3, and that revenue will already begin to accumulate by the beginning of
the first outyear.
Beyond these years, the total cost will be very hard to predict due to the possibility of research price
increase, salary increase, technology price increase, increase number of employees, company
expansion, and more.
16,000,000
14,000,000
12,000,000
10,000,000
8,000,000
ROI
6,000,000
Total Cost
4,000,000
2,000,000
0
Year 1
Year 2
Year 3
77
Year 4
Don’t Forget Me: Passenger Safety System
Staffing Plan (Patrick Markham)
Don't Forget Me
Staffing/Organizational Plan
2.0
December 10, 2007
Final
Version:
Date:
Status:
Purpose
This document defines the staffing requirements per phase. This document describes the staff
that will be needed and what that staff will be needed to do. A detailed list of all tasks per team
member is available in the Appendix.
Salaries used in the budget plan were obtained by taking the 25 th percentile for each job
description as reported at http://www.salary.com for the Norfolk zip code of 23529.
Phase 0
During this phase, the product team will consist of five seniors in the Computer Science
department at Old Dominion University. The students will also seek outside sources as needed to
assist in the research and idea development. These consultants and the students will not be paid
for their work.
78
Don’t Forget Me: Passenger Safety System
Diagram – Phase 0 Staffing Plan
Documentation Specialist
The responsibilities include creating and maintaining documents required to fulfill deliverable
requirements during development.
Financial Specialist
The responsibilities include receiving funding, creating the budget, and determining the product
cost. The financial specialist is responsible for the financial and funding plans.
Hardware Specialist
The responsibilities include identifying the hardware needed for the Don't Forget Me system,
estimating costs, and determining the best methods for developing or attaining the components.
Marketing Specialist
The responsibilities include determining the target market and supporting the marketing aspects
of the project. The marketing specialist will determine the overall marketing plan.
Project Manager
The responsibilities include making sure that all tasks are assigned and are performed with high
quality. The project manager must also resolve difference between team members and facilitate
team member communications. The project manager also must assist in the development of the
79
Don’t Forget Me: Passenger Safety System
WBS, assign resources, prioritize tasks, and define task dependencies.
Risk Specialist
The responsibilities include managing the project risks. The risk specialist must determining what
risks exists in the project, evaluate the severity and probability of the risk, and attempt to
mitigate the risks.
Software Specialist
The responsibilities include identifying the software needed for the Don't Forget Me service,
estimating costs, and determining the best methods for developing or attaining the components.
Web Specialist
The responsibilities include creating the team and product websites, as well as managing
additional web developers in future phases.
Phase 1: Proof of Concept
In this phase a lab prototype will be developed and the SBIR Phase 2 proposal will be developed.
Success will be measured by the successful completion of those two deliverables.
The following staff will be needed in Phase 1 of this project:
80
Don’t Forget Me: Passenger Safety System
Documentation Specialist
Diagram – Phase 1 Staffing Plan
The responsibilities include creating and maintaining documents required to fulfill deliverable
requirements during development.
Financial Specialist
The responsibilities include receiving funding, creating the budget, and determining the product
cost. The financial specialist is responsible for the financial and funding plans.
Hardware Specialist
The responsibilities include identifying the hardware needed for the Don't Forget Me service,
estimating costs, and determining the best methods for developing or attaining the components.
Marketing Specialist
The responsibilities include determining the target market and supporting the marketing aspects
of the project. The marketing specialist will determine the overall marketing plan.
Project Manager
The responsibilities include making sure that all tasks are assigned and are performed with high
quality. The project manager must also resolve difference between team members and facilitate
team member communications. The project manager also must assist in the development of the
WBS, assign resources, prioritize tasks, and define task dependencies.
Risk Specialist
The responsibilities include managing the project risks. The risk specialist must determining what
risks exists in the project, evaluate the severity and probability of the risk, and attempt to
mitigate the risks.
Software Manager
The responsibilities include identifying the software needed for the Don't Forget Me system,
estimating costs, and determining the best methods for developing or attaining the components.
Web Developer
The responsibilities include creating the team and product websites, as well as managing
additional web developers in future phases.
Senior Software Consultant
81
Don’t Forget Me: Passenger Safety System
The responsibilities include providing expert opinions on how best to solve problems encountered
in the development and testing of the software behind the Don't Forget Me system.
Senior Hardware Consultant
The responsibilities include providing expert opinions on what hardware to purchase, as well as on
how best to solve problems encountered in the testing of all hardware, both individually and as a
complete system.
Electrical Engineer Consultant
The responsibilities include providing expert opinions on how best to implement the system in an
actual vehicle, all electrical engineering factors considered.
Phase 2: Critical Design
82
Don’t Forget Me: Passenger Safety System
In this phase, the actual prototype of the product will be developed.
The following staff will be needed in Phase 2 of this project:
Diagram – Phase 2 Staffing Plan
Documentation Specialist
The responsibilities include creating and maintaining documents required to fulfill deliverable
requirements during development.
Financial Specialist
The responsibilities include receiving funding, creating the budget, and determining the product
cost. The financial specialist is responsible for the financial and funding plans.
Hardware Specialist
The responsibilities include identifying the hardware needed for the Don't Forget Me system,
estimating costs, and determining the best methods for developing or attaining the components.
Marketing Specialist
The responsibilities include determining the target market and supporting the marketing aspects
of the project. The marketing specialist will determine the overall marketing plan.
Project Manager
The responsibilities include making sure that all tasks are assigned and are performed with high
83
Don’t Forget Me: Passenger Safety System
quality. The project manager must also resolve difference between team members and facilitate
team member communications. The project manager also must assist in the development of the
WBS, assign resources, prioritize tasks, and define task dependencies.
Risk Specialist
The responsibilities include managing the project risks. The risk specialist must determining what
risks exists in the project, evaluate the severity and probability of the risk, and attempt to
mitigate the risks.
Software Manager
The responsibilities include identifying the software needed for the Don't Forget Me system,
estimating costs, and determining the best methods for developing or attaining the components.
Web Developer
The responsibilities include creating the team and product websites, as well as managing
additional web developers in future phases.
Safety Expert
The responsibilities include working with the development team and the organization's lawyer(s)
to define what is an acceptable level of liability for which the organization can be held responsible,
identifying necessary criteria to ensure that the Don't Forget Me system meets this level, and
verifying that the development team's functional prototype meets this criteria.
Advertiser
The responsibilities include developing presentations and actually marketing the Don't Forget Me
system to various vehicle manufacturers.
Lobbyist
The responsibilities include working with the organization's lawyer(s) to draft proposed legislation
that, if passed, would require vehicle manufacturers to incorporate a system like Don't Forget Me
in all future models. Responsibilities also include developing personal relationships with high
ranking or otherwise influential members of both houses of Congress, especially those on relevant
committees and subcommittees, to lobby said members of Congress to pass the proposed
legislation, and to work together with relevant Political Action Committees (PACs) and non-profit
organizations.
Software Engineer (5)
84
Don’t Forget Me: Passenger Safety System
The responsibilities include assisting in developing, testing and updating the software behind the
Don't Forget Me system.
Hardware Engineer (5)
The responsibilities include developing hardware components not readily available for purchase,
testing all hardware (e.g., all sensors) and developing and improving the installation design as
necessary.
Electrical Engineer
The responsibilities include identifying installation criteria, all electrical engineering factors
considered, and working with the hardware engineers to develop and improve the installation
design.
Assembly Crew Member (5)
The responsibilities include assembling the system both in part and as a complete system during
the lengthy testing process and in the development of the functional prototype.
85
Don’t Forget Me: Passenger Safety System
Phase 3: Production and Out Years
The phase is the main rollout of the product. In this phase, the authentication servers and the
website are brought online and actual production begins. The marketing campaign also begins in
this phase.
86
Don’t Forget Me: Passenger Safety System
The following staff will be needed in Phase 3 of this project:
Diagram – Phase 3 Staffing Plan
Documentation Specialist
The responsibilities include creating and maintaining documents required to fulfill deliverable
requirements during development.
Financial Specialist
The responsibilities include receiving funding, creating the budget, and determining the product
cost. The financial specialist is responsible for the financial and funding plans.
Hardware Manager
The responsibilities include identifying the hardware needed for the Don't Forget Me system,
estimating costs, and determining the best methods for developing or attaining the components.
Marketing Specialist
The responsibilities include determining the target market and supporting the marketing aspects
of the project. The marketing specialist will manage the advertising campaigns and determine the
overall marketing plan.
Project Manager
87
Don’t Forget Me: Passenger Safety System
The responsibilities include making sure that all tasks are assigned and are performed with high
quality. The project manager must also resolve difference between team members and facilitate
team member communications. The project manager also must assist in the development of the
WBS, assign resources, prioritize tasks, and define task dependencies.
Risk Specialist
The responsibilities include managing the project risks. The risk specialist must determining what
risks exists in the project, evaluate the severity and probability of the risk, and attempt to
mitigate the risks.
Software Specialist
The responsibilities include identifying the software needed for the Don't Forget Me system,
estimating costs, and determining the best methods for developing or attaining the components.
Web Developer
The responsibilities include creating the team and product websites, as well as managing
additional web developers in future phases.
Safety Expert
The responsibilities include working with the development team and the organization's lawyer(s)
to define what is an acceptable level of liability for which the organization can be held responsible,
identifying necessary criteria to ensure that the Don't Forget Me system meets this level, and
verifying that the development team's functional prototype of all updated versions of the Don't
Forget Me system meets this criteria.
Advertiser
The responsibilities include developing presentations and actually marketing the Don't Forget Me
system to various vehicle manufacturers.
Lobbyist
The responsibilities include working with the organization's lawyer(s) to draft proposed legislation
that, if passed, would require vehicle manufacturers to incorporate a system like Don't Forget Me
in all future models. Responsibilities also include developing personal relationships with high
ranking or otherwise influential members of both houses of Congress, especially those on relevant
committees and subcommittees, to lobby said members of Congress to pass the proposed
legislation, and to work together with relevant Political Action Committees (PACs) and non-profit
organizations.
88
Don’t Forget Me: Passenger Safety System
Human Resources Manager
The responsibilities include hiring personnel and handling employee benefits plans.
Software Engineer (5)
The responsibilities include assisting in developing, testing and updating the software behind the
Don't Forget Me system.
Hardware Engineer (5)
The responsibilities include developing hardware components not readily available for purchase,
testing all hardware (e.g., all sensors) and improving the installation design as necessary.
Electrical Engineer
The responsibilities include identifying installation criteria, all electrical engineering factors
considered, and working with the hardware engineers to develop and improve the installation
design.
Assembly Crew Member (5)
The responsibilities include assembling the system both in part and as a complete system during
the lengthy testing process and in the development of the functional prototype of all updated
versions of the Don't Forget Me System.
89
Don’t Forget Me: Passenger Safety System
Schedule Plan (Brandon Fields)
Don’t Forget Me
Schedule Plan
1.0
December 5, 2007
Final
Version:
Date:
Status:
Purpose
The purpose of this document is to provide a detailed plan for the future of the project.
Work Breakdown Structure
The following are the phases and tasks that must be completed to ensure the success of our
product. The tasks are enumerated with and approximation of the amount of time required to complete
each one. Corresponding to each task is a Gantt chart that was constructed according to the precedence
of each task:
90
Don’t Forget Me: Passenger Safety System
91
Don’t Forget Me: Passenger Safety System
92
Don’t Forget Me: Passenger Safety System
Risk Management Plan (Daniel Holloway)
Don’t Forget Me
Risk Management Plan
1.0
December 5, 2007
Final
Version:
Date:
Status:
Purpose
The purpose of this document is to provide a plan
Detailed Risk Management Plan
To manage risks, we will use the following procedure:

Identify project risks

Identify the phase that the risk occurred

Categorize risks according to probability and impact

Mitigate risks before or as they happen

Look out for new risks
We will reduce the risks by using the most appropriate risk management strategy.
Strategies
1. Acceptance –This strategy will be chosen if the cost to deal with the risk is greater than the cost
of the risk occurring. .
93
Don’t Forget Me: Passenger Safety System
2. Mitigation – This strategy is chosen will be chosen when it is necessary to decrease the severity
of the risk and/ or the probability that the risk will occur. We can accomplish this by making
contingency plans.
Item
A
B
C
D
Risk
Customer buy in
Cost prohibitive for the customer
Product malfunctions and baby dies
Caretaker becomes complacent
Probability
3
3
1
1
Impact
5
4
5
2
Impact
Detailed Risk Management Plan
Item
Risk
A
Customer buy in
If our customer does not buy in
on our product the return on
investment diminishes or
evaporates.
B
Cost prohibitive for the
customer
If the device is too expensive for
Mitigation
Provide a marketing plan to demonstrate the
return on investment for the customer.
Demonstrate to the customer how this system
will increase sales. Through effective
marketing by advertising and providing an
exhibit at conferences will help obtain
customer buy in. Knowing who are your
competitors what they have to offer will help
provide knowledge to mitigate the risk.
Ensure that we find the best price for hardware
needed and to keep labor cost down to
minimum. Labor is the biggest cost and can be
mitigated by having well thought out design
94
Don’t Forget Me: Passenger Safety System
C
D
the customer, sales will suffer.
plan and leveraging off of existing technology.
The customer needs a low cost
device to be negligible to the cost
of the vehicle.
Product malfunctions and baby Implement vigorous test procedures and have
the device perform self diagnostic test when
dies
engine is started.
If the product malfunctions and
results in the death of the vehicle
occupant, the loss of confidence
will diminish sales and increase
liability.
Complacency is the hardest risk to reduce. To
Caregivers becomes
mitigate this risk, the device regularly
complacent
communicates with caregiver at specific time
The caregiver becomes
intervals.
complacent and less observant of
the occupant because of the
autonomy of the device
monitoring the presence of the
child.
95