ISE 583 Syllabus - Fall 2009

Instructor: Richard W. Vawter ISE 583, Fall 2009

Office: OHE 530B Location: OHE 100B

E-Mail: vawter@usc.edu T/Th 2:00-3:20 p.m.

Phone: (213) 740-9541

Office Hours: Mon. 11:00 - 12:00 p.m. Class Web Page:

2:00 - 4:00 p.m. http://www-rcf.usc.edu/~vawter/classes.html

Tues. 11:10 - 12:00 p.m. or

Wed. 10:30 - 12:00 p.m. http://www.uscden.net/

Thurs. 10:30 - 12:00 p.m.

or by appointment

Course Description:

This course is designed to provide the student with a thorough understanding of both the role that Enterprise Resource Planning Systems (ERPs) play in an organization and the challenging task of implementing and managing the Information System (IS) function. During the semester, projects and case studies will be assigned that afford the student the opportunity to work through many real-life business situations using the SAP ECC system and explore the interaction among the different business processes. SAP is the world’s leading provider of client/server software designed to integrate every aspect of a company’s operation. The hands-on exercise, coupled with the in-class discussions of ERPs, will prepare the student with the knowledge sought by businesses looking to use technology to maintain their competitive edge in the market place.

Objective:

At the completion of the course, students will be able to…

• Describe the role of an ERP in carrying out business processes in a company

• Explain how ‘best business practices’ are incorporated in an ERP

• Execute an entire business process chain in the following areas

- Customer Order Management

- Procurement

- Production

- Accounting

• Strategize pricing, production and sales in a competitive commodity market

• Analyze sales data in an ERP to dynamically respond to changing market conditions to maximize profits

• Expedite production planning and control using tools provided in an ERP system

• Report on the reasons for the success (or failure) of production and sales strategy

Required Textbooks:

Class Schedule:

Class		Topic		Reading Assignment		Assignment
1. Aug. 25 Aug. 27		Course Overview ERP Overview		Curran: Introduction and Chapter 1		Case #1 – “SAP America”, due Sept. 1
2. Sept. 1 Sept. 3		Discuss SAP America ERP Systems and Basis Architecture		Curran: Chapters 2, and 14		Project #1 – SAP ECC Introduction, due Sept. 8
3. Sept. 8 Sept. 10		ERP Functionality Best Business Practices		Curran: Chapters 3, 4 and 16.1-16.4		Project #2 – Business Processes, due Thursday Sept. 17
4. Sept. 15 Sept. 17		Best Business Practices The Customer Order Management Process		Curran: Chapter 5		Project #3 – Customer Order Mgmt, due Wed., Sept. 30
5. Sept. 22 Sept. 24		COM Process (cont.) COM Process (cont.)		Continue with Ch. 5		Continue with Proj. #3, due Wed., Sept. 30
6. Sept. 29 Oct. 1		Procurement Process Procurement (cont.)		Curran: Chapter 7		Project #4 Procurement, due Wed. Oct. 7
7. Oct. 6 Oct. 8		Complete Procurement Midterm Exam		none		Midterm Project, Due, Oct. 15, 2:00 pm Case #2 – “Information Flows in Manufacturing”, due Oct. 13
8. Oct. 13 Oct. 15		Discuss the Info Flows in the MFG Case Begin Manufacturing: Planning & Execution		Curran: Chapter 6		Project #5 – Manufac-turing, due Oct. 27
9. Oct. 20 Oct. 22		Manufacturing (cont.) Manufacturing (cont.)		Continue with Ch. 6		Continue with Proj. #5, due Oct. 27
10. Oct. 27 Oct. 29		Complete MFG Accounting and the General Ledger		Curran: Chapter 8		Project #6 – Accounting, due Nov. 3
11. Nov. 3 Nov. 5		Accounting (cont.) Discuss Vandelay Case		Class notes		Case #3 – “Vandelay Industries”, due Nov. 5
	12. Nov. 10 Nov. 12		ERP Implementation Discuss Timberjack Case		Curran: Chapter 16.5 - 16.7		Case #4 – “Timberjack Parts”, due Nov. 12
	13. Nov. 17 Nov. 19		Configuration and the IMG		Curran: Chapter 16 - 16.5 Class notes		Project #7 – Configur-ation, due Wed. Nov. 25 by 2:00 pm.
	14. Nov. 24 Nov. 26		Programming ERP systems using ABAP *Thanksgiving Holiday*		Curran: Chapter 15 Class notes		Project #8 – ABAP/4 , due Wed. Dec. 2 by 2:00. Final Project – due Friday, Dec 4, 5:00 pm
	15. Dec. 1 Dec. 3		ABAP (cont.) Course Review		Class notes		Final Project due Friday, Dec. 4, by 5:00 pm

Lab Policies

· The SAP GUI is installed on the computers in the GER 309 lab and in the ITP computer labs. In the third week of class I will post the hours of the ITP labs.

· Lab assistants are not familiar with SAP, nor with class assignments, so please don’t expect them to be able to help answer questions regarding the projects.

· Note: Before logging off any lab computer, you must ensure that you have either emailed or saved your work created during your time in the lab. Any work saved to the computer will be erased each evening and after restarting the computer. The School of Engineering is not responsible for any work lost.

Lab Projects:

· After the 3^rd day of class, Sept. 1^st, each of you will be given an account on the R/3 system and assigned a number for working on the projects.

· Projects will be available via the “Assignments” section of the DEN class web site.

· It is your responsibility to turn in the lab projects by the beginning of lecture on the dates indicated above and verify that your assignment is in the class “assignment box”.

· You are to only turn in the “Answer sheet” and “Summary” portion of the project write-up as one document.

· You are to submit your “Answer sheet / Summary” document via the “Assignments” section of the DEN class web site (from where you originally obtained the project write-up).

· Verify that your document is in the class “assignment box” and double-click on it to open it up. If you can’t see or open your document, neither can the grader!

· Failure to correctly submit projects will result in a 5% penalty.

· Answers to the projects will be posted on the Class Web page after the due date of the projects for your review.

Late Projects

· The “Assignments” section of the DEN class web site “closes” after the due date and time.

· You will no longer be able to submit your project and your project will be considered late.

· Late projects must be e-mailed to me directly (vawter@usc.edu), not the grader.

· I will then make a note of receiving your late project and then forward the project on to the class grader for grading.

· Projects that are turned in after the deadlines will automatically have ½ of the possible points deducted prior to grading. No excuses!! So, please turn in your projects at the beginning of lecture on the dates indicated above!

· No projects will be accepted for credit after 2 weeks beyond the project’s original due date nor after the last day of the semester (Dec. 4).

· Please note: No late Midterm Projects will be accepted for credit.

Handling Project Questions (in order of steps to be taken)

1. Re-read the instructions carefully and try referring to: http://help.sap.com

2. Review the “Discussion Board” section of the DEN class web site’s forum for other students’ questions and comments or post a question yourself to begin the forum.

3. E-mail the class TA your question, being sure to be clear in your question and detailed in your explanation of the situation. Replies may take some time, since e-mail is really not an efficient method for working a “help desk”.

4. And, of course, you’re always welcome to stop by my office during my office hours or contact me and arrange for an appointment.

Please note: I do not address “project problems” via e-mail. I am happy to discuss the problems with you in person, and guide you to solving them yourself during my office hours; but my e-mail address is not to be used as a simple “help desk”.

Case Studies

· Two case studies will be assigned during the semester. These are simply studies of business experiences similar to the topics being discussed in class.

· You are to read over the cases and type up a one page, double-spaced analysis, explaining the business situation, concerns, and possible suggested actions to take.

· Case studies are to be submitted by the beginning of the lecture on the dates indicated on the syllabus via the “Assignments” section of the class web site (just as you do for submitting your project write-ups).

· Please note: No late case studies will be accepted for credit.

Examinations: Exams cover material from the reading assignments, lectures, lab projects, and the simulation game. The questions will be of the form: short answer, short essay, and short problem solving. The exams are all closed book and closed notes. The exams will include material presented up to the date of the exam. The “Final” exam will contain questions covering topics throughout the semester, but will be weighted more heavily toward the topics discussed after the midterm and results of the ERP simulation game.

Midterm: Thursday, Oct. 8, 2:00-3:20 p.m. in room TBA

Final Exam: Thursday, Dec. 10, 2:00-4:00 p.m. in room TBA

Note: No make-up exams will be offered nor will there be any changes made to the Final Exam schedule as established by the University.

Grading:

Grading will be on a straight scale (as opposed to a class curve/average).

The final grades will be based upon the University standard:

94% and above A

90% - 94% (not including 94%) A-

87% - 90% (not including 90%) B+

83% - 87% (not including 87%) B

etc.

The grades are calculated by weighing the following work as described here:

Case Studies submitted 10%

Average of Lab Projects Scores 20%

Midterm grade 20%

Midterm Project score 10%

Final Project 15%

Final Exam grade 25%

100%

Students with Disabilities:

Any student requesting academic accommodations based on a disability is required to register with Disability Services and Programs (DSP) each semester. A letter of verification for approved accommodations can be obtained from DSP. Please be sure the letter is delivered to me (or to your lab assistant) as early in the semester as possible. DSP is located in STU 301 and is open 8:30 a.m. - 5:00 p.m., Monday through Friday. The phone number for DSP is (213) 740-0776.

Student Conduct:

The use of unauthorized material, communication with fellow students during an examination, attempting to benefit from the work of another student, and similar behavior that defeats the intent of an examination or other class work is unacceptable to the University. It is often difficult to distinguish between a culpable act and inadvertent behavior resulting from the nervous tension accompanying examinations. When the professor determines that a violation has occurred, appropriate action, as determined by the instructor, will be taken.

Although working together is encouraged, all work claimed as yours must in fact be your own effort. Students who plagiarize the work of other students will receive zero points and possibly be referred to Student Judicial Affairs and Community Standards (SJACS).

All students must read, understand, and abide by the University Student Conduct Code listed in SCampus, and available at:

http://www.usc.edu/student-affairs/SJACS/nonacademicreview.html

Excerpts taken from SC Campus Student Guidebook, 04/05:

§11.00 Behavior Violating University Standards and Appropriate Sanctions

“…individual work will be submitted [by the student], and [it’s the student’s] obligation both to protect one’s own academic work from misuse by others as well as to avoid using another’s work as one’s own.”

§11.11 Plagiarism (Definition)

“The submission of material authored by another person but represented as the student’s own work, whether that material is paraphrased or copied in verbatim or near verbatim form.”

§11.14 Plagiarism (Definition continued)

“Obtaining for oneself or providing for another person a solution to homework a project or other assignments, or a copy of an exam or exam key without the knowledge and expressed consent of the instructor.”

Any violation will be immediately reported to the Office of Student Judicial Affairs and Community Standards. The alleged violation will then be reviewed by the board. If the student is determined to be responsible for the violation, appropriate disciplinary action will be determined and then implemented by the University.