This unit provides both a theoretical and practical overview of real time enterprise systems. Real time enterprise systems are configurable information systems packages, implemented on-line that integrate people, technology and information processing. The three integrated processes within and across functional areas are seamlessly interconnected and almost time-lag free in an organisation. Topics include systems and technology background, ES evolution, ES lifecycle, implementation and configuration, ES and electronic commerce and ES success and failure factors. The theoretical component will be augmented by detailed case studies which focus on problems faced by real-life companies. For the practical component, laboratory exercises using a well-known enterprise system will be used to deepen student understanding.
2 hrs lectures/wk, 2 hrs laboratories/wk
Students will be expected to spend a total of 12 hours per week during semester on this unit as follows:
For on-campus students:
Lectures: 2 hours per week
Tutorials/Lab Sessions: 2 hours per week per tutorial
and up to an additional 8 hours in some weeks for completing lab and project work, private study and revision.
Off-campus students generally do not attend lecture and tutorial sessions, however, you should plan to spend equivalent time working through the relevant resources and participating in discussion groups each week.
FIT3012, FIT3133, FIT3068
Completion of 12 points of level two units from Information Technology, Science or Engineering or equivalent.
Susan Foster
Jayantha Rajapakse
Jayantha Rajapakse
Examination (2 hours) 60%; In-semester assessment 40%
| Assessment Task | Value | Due Date |
|---|---|---|
| Enterprise systems implementation requirements | 20% | Monday, 3 September 2011 |
| Risk Management Strategy for an Enterprise System implementation | 20% | Monday 8 October 2011 |
| Examination 1 | 60% | To be advised |
Monash is committed to excellence in education and regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through SETU, Student Evaluation of Teacher and Unit. The University's student evaluation policy requires that every unit is evaluated each year. Students are strongly encouraged to complete the surveys. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.
For more information on Monash's educational strategy, and on student evaluations, see:
http://www.monash.edu.au/about/monash-directions/directions.html
http://www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html
Previous students found this unit intellectually stimulating, with sufficient resources and support to complete the learning objectives. Student feedback has informed improvements to this unit by adjusting the pace and structure of this unit sufficiently appropriate to complete the tasks required of them in a timely manner.
If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp
There is no material or equipment required for this exam.
| Week | Activities | Assessment |
|---|---|---|
| 0 | Introduction to FIT3012, Unit objectives, enterprise systems unplugged, the what, why and how of ERP systems | No formal assessment or activities are undertaken in week 0 |
| 1 | Enterprise systems revisited | |
| 2 | Enterprise system implementation issues - 1 | Assignment 1 handed out |
| 3 | Enterprise system implementation issues - 2 | |
| 4 | Enterprise system implementation issues - 3 | |
| 5 | Enterprise system implementation issues - 4 | |
| 6 | Enterprise system implementation issues - 5 | |
| 7 | Enterprise system implementation issues - 6 | Assignment 1 due Monday, 3 September 2011; Assignment 2 handed out |
| 8 | Enterprise system implementation issues - 7 | |
| 9 | Enterprise system implementation issues - 8 | |
| 10 | Enterprise system implementation issues - 9 | |
| 11 | Enterprise system implementation issues - 10 | |
| 12 | Current and future enterprise system trends | Assignment 2 due Monday, 8 October 2011 |
| SWOT VAC | No formal assessment is undertaken SWOT VAC | |
| Examination period | LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/ academic/education/assessment/ assessment-in-coursework-policy.html |
*Unit Schedule details will be maintained and communicated to you via your MUSO (Blackboard or Moodle) learning system.
Faculty Policy - Unit Assessment Hurdles (http://www.infotech.monash.edu.au/resources/staff/edgov/policies/assessment-examinations/unit-assessment-hurdles.html)
Academic Integrity - Please see the Demystifying Citing and Referencing tutorial at http://lib.monash.edu/tutorials/citing/
The assignment task is assessed on students ability to:
1. Identify an appropriate vendor and enterprise resource system for implementation based on business drivers from the real-world case study.
2. Develop an appropriate approach to identify the final enterprise resource system for implementation
3. Identify a proposed implementation methodology
Students will be assessed on their contribution
It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/plagiarism-procedures.html) for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at http://www.infotech.monash.edu.au/resources/student/forms/. Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an online quiz).
Submission must be made by the due date otherwise penalties will be enforced.
You must negotiate any extensions formally with your campus unit leader via the in-semester special consideration process: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html.
Students may not resubmit any part of their assignments.
Monash has educational policies, procedures and guidelines, which are designed to ensure that staff and students are aware of the University's academic standards, and to provide advice on how they might uphold them.
You can find Monash's Education Policies at:
http://policy.monash.edu.au/policy-bank/academic/education/index.html
Key educational policies include:
The University provides many different kinds of support services for you. Contact your tutor if you need advice and see the range of services available at www.monash.edu.au/students. For Sunway see http://www.monash.edu.my/Student-services, and for South Africa see http://www.monash.ac.za/current/
The Monash University Library provides a range of services and resources that enable you to save time and be more effective in your learning and research. Go to http://www.lib.monash.edu.au or the library tab in my.monash portal for more information. At Sunway, visit the Library and Learning Commons at http://www.lib.monash.edu.my/. At South Africa visit http://www.lib.monash.ac.za/.
Academic support services may be available for students who have a disability or medical condition. Registration with the Disability Liaison Unit is required. Further information is available as follows:
Students will be provided with adequate reading requirements in their assignment and at the end of each lecture.
Davenport (1998). Putting the enterprise into the enterprise system. Harvard Business Review. July-August 1998.
Hershey Business case (2000) Located at: http://www.erpwire.com/erp-articles/failure-story-in-erp-process.htm l.
Titulair, H. B., Oktamis, S., and Pinsonneault, A. (2005). Dimensions of ERP implementations and their impact on ERP Project outcomes. Journal of Information Technology Management. Vol XVI, 1. Located at http://jitm.ubalt.edu/XVI-1/article1.pdf lhttp://www.sap.com/australia/solutions/customersuccess/index.epx.
ACC (1984). ERP implementations and their issues. Proceedings of the Australian Computer Conference, Sydney, Australian Computer Society, November Edn.
Berthold W.F. and Hingsen C.S. (1981) The Introduction of New Technology to the Workplace, Berlin: Springer-Verlag.
Bingi, P. Sharma M.K. and Godla J.K. (1999). “Critical Issues Affecting An ERP Implementation”, Information Systems Management, Vol. 16, 3, pp 7-14.
Davenport, T. H. (2000a). Mission critical: Realising the promise of enterprise systems. Boston: Harvard Business School Press.
Davenport, T. H. (2000b). The future of enterprise system-enabled organisations. Information Systems Frontiers (special issue of The future of Enterprise Resource Planning Systems Frontiers), 2(2), 163-180.
Holland, C. and B. Light (1999). "A Critical Success Factors Model For ERP Implementation." Software, IEEE 16(3): 30-36.
Klause, H. & Roseman (2000). What is enterprise resource planning? Information Systems Frontiers (special issue of The Future of Enterprise Resource Planning Systems), 2 (2), pp 141-162.
Lewis, P.J. (1993a). Linking Soft Systems Methodology with Data-focused Information Systems Development, Journal of Information Systems, Vol. 3, pp. 169-186.
Nolan, & Norton Institute. (2000). SAP Benchmarking Report 2000, KPMG Melbourne.
Queensland Health Corporate Publications: Change management Documents: Located at http://www.health.qld.gov.au/publications/change_management/
Ross, J. W. (1999). “The ERP Revolution: Surviving Versus Thriving, Centre for Information System Research, Sloan School of Management, MA, August 1999.
Shang, S. & Seddon, P. B. (2000). “A comprehensive framework for classifying the benefits of ERP systems” in the proceedings of the twenty third Americas Conference on Information Systems. pp 1229-1698.
Sumner, M. (2000). "Risk factors in enterprise-wide/ERP projects." Journal of Information Technology 15(4): 317 - 327.
Yang, S. and Seddon, P. (2004). “Benefits and Key Project Success Factors from Enterprise Systems Implementations: Lessons from Sapphire 2003”. In the proceedings of ACIS 2004, Hobart, UTAS.