Note that during the AY2009-10 academic year, the DPM
students did not complete the customer needs during the
fall term, and thus much of the detail regarding customer
needs were deferred to the first several weeks of MSD 1.
As a result, each individual project team in the roadmap
created their own interpretation of the general needs
that were outlined previously by the students in DPM.
Each of the VOC tables generated by the individual
project teams are shown in the tables below.
While the students in the MSD teams have grown to develop
a reasonably complete set of customer needs, and turn
them into engineering performance specifications, this
took several weeks of effort in MSD. For future terms of
DPM, our goal will be to fully develop the customer
needs, including measures of effectiveness, for the
entire roadmap family prior to the conclusion of DPM.
As you review the tables below, please make note of the
following items that future DPM students should do
differently as they prepare roadmaps for other project
families, or as this roadmap is refined.
- Customer Need numbering and/or naming should be
consistent across the family, such that 'Customer Need 1'
means the same thing to all projects in the roadmap.
- The importance scale used for customer needs should
be consistent across all projects within a family. I
recommend the scale as follows:
- 9 = Critical Need that provides basic
functionality for the roadmap. Failure to meet this
need results in a product that does not meet the
customer's basic requirements.
- 3 = Important Need that the customer assigns
significant value to. Failure to meet this need
results in a product that does not meet the
customer's requirements.
- 1 = Preferred Need that the customer would like
to have present in the product, but not at the
expense of failing to meet more important needs.
- Blank = Enhancing Feature, or Desire as opposed
to a customer need. The customer assigns value to
this need, but would have a fully functional solution
without this need being included in the current
generation.
- The Description of the Customer Needs should be clear
and concise, and meaningful to a fourth year engineering
student of any discipline present in the KGCOE.
- Every customer need should have an articulated
measure of effectiveness by which the team can determine
whether or not the need has been satisfied. These
measures of effectiveness are usually
qualitative in nature, and may be somewhat
subjective. These are specifically NOT INTENDED to be
measures of performance, which are more
commonly related to the Voice of the Engineer, and which
typically are quantified in engineering units of
measure.
- The set of customer needs should be agreed to prior
to the end of DPM, by formal review with a DPM faculty
member. Should a subsequent MSD team wish to modify the
customer needs, then ALL AFFECTED ROADMAP teams must gain
the consent of the DPM faculty member, who represents the
stakeholder group at large.
- Every customer need should be traceable to prior
needs assessment activity, having its roots in the
objective tree, which in turn was compiled from the raw
data contained in the affinity diagrams based on customer
interviews, focus groups, and benchmarking.
- Every customer need should be traceable to one or
more stakeholder group.
Land Vehicle Customer Needs
P10201 Platform Integration - Land Vehicle -
Voice of the Customer
|
Need #
|
Importance
|
Description
|
|
CN1
|
9
|
Use with multiple generations of components/modules.
|
|
CN2
|
3
|
Look professionally constructed and well organized.
|
|
CN3
|
3
|
Be as equal in weight or lighter than the previous
generation.
|
|
CN4
|
3
|
Be equal in size or smaller than the previous
generation.
|
|
CN5
|
9
|
Must be stable on a flat surface (i.e. tabletop)
throughout its operating range for a variety of
payloads.
|
|
CN6
|
9
|
Needs to carry and secure a 1kg payload.
|
|
CN7
|
9
|
Be open source.
|
|
CN8
|
9
|
Be open architecture.
|
|
CN9
|
9
|
Provide a portable power source.
|
|
CN10
|
9
|
Operate for a useful period of time on power source.
|
|
CN11
|
9
|
Deliver 1 platform.
|
|
CN12
|
3
|
Deliver 5 platforms.
|
|
CN13
|
1
|
Deliver 25 platforms.
|
|
CN14
|
1
|
Configurable ground clearance.
|
|
CN15
|
9
|
Easy for a first year engineering student to assemble
and use.
|
|
CN16
|
9
|
Can be assembled in more than one configuration.
|
P10202 Motor Module - Land Vehicle - Voice of
the Customer
|
Need #
|
Importance
|
Value to Customer
|
Description
|
|
CN1
|
9
|
Critical Need
|
Modular design
|
|
CN2
|
9
|
Critical Need
|
Lower cost of previous generation MM
|
|
CN3
|
9
|
Critical Need
|
Open architecture
|
|
CN4
|
9
|
Critical Need
|
Robust to damage from inexperienced operators
|
|
CN5
|
9
|
Critical Need
|
Ability to perform on any Indoor RIT floor surface
|
|
CN6
|
3
|
Important Need
|
Safe to human operators
|
|
CN7
|
3
|
Important Need
|
1 kg payload Capacity
|
|
CN8
|
3
|
Important Need
|
Manufacturable in lots of 5-25
|
|
CN9
|
3
|
Important Need
|
Zero turning radius (Must travel laterally)
|
|
CN10
|
3
|
Important Need
|
Stable enough to support big payload contest
|
|
CN11
|
3
|
Important Need
|
Agile and controllable enough for Dance Dance
Robolution
|
|
CN12
|
3
|
Important Need
|
Easy to install and remove modules onto LV
|
|
CN13
|
3
|
Important Need
|
Speed should not under-perform previous generation MM
|
|
CN14
|
1
|
Preferred Capability
|
Professional and organized appearance
|
|
CN15
|
1
|
Preferred Capability
|
Adjustable ground clearance
|
|
CN16
|
1
|
Preferred Capability
|
Lower weight than previous generation MM
|
|
CN17
|
1
|
Preferred Capability
|
Able to climb handicap access ramps (small inclines)
|
P10203 Motor Controller - Land Vehicle - Voice
of the Customer
|
Need #
|
Importance
|
Description
|
Comments / Status
|
|
CN1
|
3
|
The controller is easy to manufacture and assemble.
|
|
|
CN2
|
4
|
The controller is modular, (can be configured in
several different options to support varied
functionality).
|
|
|
CN3
|
5
|
The controller has a low risk implementation and is
stand-alone.
|
Controller operates as intended even if other groups
fail to finish.
|
|
CN4
|
5
|
The controller is able to properly interface with the
other modules of the Land Vehicle Platform.
|
|
|
CN5
|
4
|
The controller is able to be used by first year
mechanical/electrical engineering students.
|
|
|
CN6
|
3
|
The controller is able to make the platform move with
sufficient agility and controllability.
|
Sufficient is described as at the same level or
better than the RP1.
|
|
CN7
|
3
|
The new design shall improve upon the aesthetics of
the RP1.
|
|
|
CN8
|
2
|
The controller makes effective use of the space
provided by the Chassis.
|
Space effectiveness refers to minimizing overall
space requirement without sacrificing cost or
performance.
|
|
CN9
|
5
|
The new design is cost effective, (cheaper than the
RP1 with the same, or improved performance
characteristics).
|
|
|
CN10
|
4
|
The controller is durable and can withstand repeated
use with minimal maintenance.
|
|
|
CN11
|
2
|
The controller has a reasonable battery life.
|
Reasonable refers to a level at or above the RP1.
|
|
CN12
|
2
|
The controller is able to be upgraded by future
Senior Design teams with little redesign or component
replacement needed.
|
Upgrade is used to refer to the fact that a CE team
could be given the controller to add software
functions to the system.
|
|
CN13
|
3
|
The Controller makes use of Prior Generation's
Designs and Research.
|
|
WOCCS Customers Needs
P10205 WOCCS - Voice of the Customer
|
Need Number
|
Importance
|
DPM Rank
|
Harris Rank
|
Description
|
Comment/Status
|
|
Need 1
|
1
|
|
|
Able to manufacture in quantities of 5 (minimum) to
25 (stretch goal)
|
|
|
Need 2
|
3
|
2
|
6
|
Modularity
|
Number of Channels
|
|
Need 3
|
9
|
|
|
Any module has a low risk implementation
|
Wire in place for wireless link
|
|
Need 4
|
9
|
6
|
8
|
Common power for all on board users.
|
Energy efficiency, run time in hours
|
|
Need 5
|
3
|
|
|
Easy to program by first year students
|
Programmable by non-programmers
|
|
Need 6
|
9
|
|
3
|
System is easily re-usable
|
|
|
Need 7
|
9
|
3
|
|
"Plug and Play"
|
Standardize all interfaces
|
|
Need 8
|
3
|
5
|
2
|
Data Transmission Rate
|
Channel Bandwidth (kbps)
|
|
Need 9
|
3
|
|
|
Communication Distance
|
Gordon Field House
|
|
Need 10
|
9
|
1
|
1
|
Reliability
|
Physical & Electrical, Max Power Retained, Range
w/o Connection Problems
|
|
Need 11
|
3
|
|
|
Variety of Mounting Options
|
|
|
Need 12
|
9
|
|
|
Wireless Link for Command and Control
|
|
|
Need 13
|
3
|
4
|
5
|
Compact Size and Weight
|
(kg) and (m^3)
|
|
Need 14
|
3
|
8
|
3
|
Security
|
Encryption Standard
|
|
Need 15
|
3
|
7
|
7
|
Low Cost
|
US Dollars
|
Home
