The purpose of this ERPsim report is to facilitate reflection on ERPsim lab activities to maximize the learning outcomes for each activity. The simulation activity will not be a graded exercise, however the report submitted based on the activity will be graded.
Reports will be graded based on the following criteria:
•Presence of required elements
•Communication effectiveness (clear, well-written, professional, etc.)
•Quality of content
•Degree of detail and specificity in observations
•Evidence of insight and learning
The report should be based on your most recent simulation activity and is to be an individual activity. The report should be 1-2 pages long at most, and contain the following information:
1. Your name, your team name, the date of the simulation, and what your team's finishing position was in the simulation.
2. An explanation of the strategy and methodology your team employed (i.e. what did you do to compete and why?)
3. What did you think went well? (Strengths)
4. What could be improved for the future? (Weaknesses)
5. List two things you learned during this activity. (Outcomes)
6. Identify which role you were responsible for in your team. Provide a brief explanation of how you used the information in the SAP system to perform your role. What information would help you perform your role better.
Please note:
Keep in mind that we are using ERPsim as a class activity for various reasons: to learn more about Enterprise Information Systems, to gain skill at working with SAP, to develop personal experience in business decision making, to gain skill at working with teammates in a time-and-communication sensitive project, and others. In your report as you discuss strategies, strengths, weaknesses, and outcomes, all of these elements are valid elements for inclusion. In other words "I learned SAP transaction code xxxx" might be a valid outcome, but "I observed that having the same person do activity xxxx and yyyy created a bottleneck in our strategy execution" would show much more evidence of insight and meaningful learning. Candor in reporting is valued. Discussing mistakes made by the team or problems during task execution will not lower the report score, but rather may show evidence of thoughtful evaluation.
For this report, team members should not work together. After all team members have submitted their individual reports, team discussion of observations and activities may be desired to achieve improvement.
Please save your report as a Word file with the following file name. username-S302ERPsim_Reflection2.docx.