ENMA
6060: Innovation and Technology
Projects
– Fall 2009
Student
team projects form a major element of this course. Projects enable student teams to apply
materials learned in course lectures and tutorials to real-world problems.
Projects
for this course offering are outlined below:
|
Sponsor |
Team |
Description |
Sponsor |
Ph. |
e-mail |
|
Marquette University - University
Advancement |
Malin, Riccaboni, Parikh |
Increase alumni donations
with targeted fundraising campaign. |
Todd McMahon |
414-288-0346 |
todd.mcmahon@mu.edu |
|
Briggs & Stratton |
Hickey, Cooke, De Avila |
Improve surface finish of
engine cylinders. |
Ross Hickey |
|
|
|
Briggs & Stratton |
B. Schneider, Brady |
Improve surface finish of
engine pistons. |
Ben Schneider |
|
|
|
Andis |
J.Y.
Schneider, Mozee, Rueckert |
Improve performance of
heat treatment process. |
Jeff Marcheske |
262-884-2600x2779 |
jeff.marcheske@marquette.edu |
|
Warsaw University of Technology |
Saginus, Kuta, Darling |
Improve quality of foundry
castings – gas porosity. |
Mark Polczynski |
262-364-6609 |
mark.polczynski@mu.edu |
|
Warsaw
University of Technology |
Hebert,
Konkel, Pavaskar |
Improve quality of foundry castings – material properties. |
Mark Polczynski |
262-364-6609 |
mark.polczynski@mu.edu |
Projects
will be conducted in accordance with the CRISP-DM process model. Over the course of the semester,
project teams will submit project deliverables per the schedule shown below
(dates shown are due dates). Team
project deliverables correspond with the output reports defined in Section IV
of the CRISP-DM 1.0 model (http://www.crisp-dm.org/Process/index.htm). See Section IV for details if the contents of
each output deliverable report.
Deliverable
Output Reports – Fall 2009
|
Week |
Due Date |
CRISP-DM Phase |
Deliverable Output Report |
|
5 |
21-Sep |
Business understanding |
1. Business understanding |
|
7 |
5-Oct |
Data understanding |
2.1 Initial data
collection |
|
|
|
2.2 Data description |
|
|
|
|
2.3 Data exploration |
|
|
|
|
|
2.4 Data quality |
|
9 |
19-Oct |
Data prediction |
3. Dataset description |
|
13 |
23-Nov |
Modeling |
4. Modeling deployment
plan |
|
14 |
30-Nov |
Evaluation |
5. Monitoring and
maintenance |
|
15 |
7-Dec |
Deployment |
6. Final report (.ppt) |
|
16 |
14-Dec |
Deployment |
7. Final report |
Deliverables
will be prepared as follows:
·
Each
deliverable should be created as a Microsoft .doc document except as noted.
·
It
may be that certain deliverables do not apply well to all projects. Deliverables may be deleted or modified after
consulting with your instructor.
·
Teams
should be prepared to discuss their deliverables in class on the due dates.
·
The
final report should contain a summary of the deliverables, and should include
all of the deliverables as appendices.
There is no minimum or maximum length for the .doc final report.
·
The
final presentation should consist of a 20 minute max. summary
of the final report.
·
Teams
will make final presentations to the class and sponsors on the date shown above
during the regularly-scheduled class time.
·
All
documents should contain no references to the name of the project sponsor, and
should not contain any information that would allow the sponsor company to be
identified.
·
All
reports should be submitted before 5:00 on the due date by depositing in the
associated D2L discussion section.