[an error occurred while processing this directive] [an error occurred while processing this directive]
[an error occurred while processing this directive]
[an error occurred while processing this directive]

FIT5101 Enterprise systems - Semester 1, 2013

This unit provides students with an overview of Enterprise Systems and is designed to describe the role of enterprise systems as part of the larger IT infrastructure of large scale organisations. Emphasis will be placed on benefit realisation through the use of specific measurement tools to help manage and deploy these packages. Additionally SAP R/3 will be used to introduce students to the complexity of enterprise wide systems through tutorial workshops where appropriate. This will include the addition of process modelling software tasks in practical sessions using ARIS toolset (SAP R/3 reference model).

Mode of Delivery

  • Caulfield (Day)
  • Sunway (Evening)

Contact Hours

2 hrs lectures/wk, 2 hrs laboratories/wk

Workload requirements

Students are expected to spend 12 hours per week as follows:

  • 2 hour lecture and
  • 2 hour tutorial in a laboratory
  • a minimum of 2-3 hours of personal study per one hour of contact time in order to satisfy the reading and assignment expectations.

Unit Relationships

Prohibitions

IMS5052, BUS5700

Prerequisites

FIT9006

Chief Examiner

Campus Lecturer

Caulfield

Sue Foster

Sunway

Jayantha Rajapakse

Consultation hours: TBA

Tutors

Sunway

Jayantha Rajapakse

Academic Overview

Learning Outcomes

At the completion of this unit students will:
  • identify the role of business wide systems to support the business strategy;
  • identify the main suppliers, products and application domains of enterprise wide packages;
  • understand the scale and complexity of enterprise system packages;
  • understand the integrative role of enterprise systems for information within the organisational context;
  • describe the role of enterprise systems as part of the larger IT infrastructure of large scale organisations;
  • identify the implementation variables, individual variables and contextual variables that interact to influence a successful enterprise system implementation;
  • use a process modelling tool to model processes.

Unit Schedule

Week Activities Assessment
0   No formal assessment or activities are undertaken in week 0
1 Introduction to enterprise systems  
2 Enterprise system requirements - Business case Assignment 1 (Enterprise System) handed out
3 Business process optimisation (1)  
4 Business Process management (2)  
5 Business process modelling Assignment 1 (Enterprise System) due Monday 8 April 2013. Assignment 2 (Risk Management Strategy) handed out
6 Enterprise systems implementation - Risk Management Strategy  
7 Enterprise system implementation - Vendor selection  
8 Enterprise systems implementation - Integration issues Assignment 2 (Risk Management Strategy) due Monday 29 April 2013. Assignment 3 (Implementation Approach Report) handed out
9 Enterprise Systems implementation - Master data management  
10 Organisational change management (1)  
11 Organisational change management strategies (2) Assignment 3 (Implementation Approach Report) due Friday 24 May 2013
12 Future issues and trends  
  SWOT VAC No formal assessment is undertaken in 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 learning system.

Assessment Summary

Examination (2 hours): 30%; In-semester assessment: 70%

Assessment Task Value Due Date
ASSIGNMENT 1 - Enterprise system - Business case development 30% Monday 8 April 2013
ASSIGNMENT 2 - Risk Management Strategy 25% Monday 29 April 2013
ASSIGNMENT 3 - Report on the implementation approach 15% Friday 24 May 2013
Examination 1 30% To be advised

Teaching Approach

  • Lecture and tutorials or problem classes
    This teaching and learning approach provides facilitated learning, practical exploration and peer learning.
  • Problem-based learning
    In this teaching approach you are introduced to information via lectures and then required to practically apply that information. You are encouraged to take responsibility for organising and directing your learning with support from your supervisor (tutor).

    You will be presented with a case study, and relevant information, and guided on how best to find solutions to the problem.

Assessment Requirements

Assessment Policy

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/

Assessment Tasks

Participation

Students will be evaluated on the outcome of the total group assignment. Where individual components are offered , students will be marked according to the marking criteria for that individual component. 

The tutor will monitor individual contributions to the group when allocating marks to members of the group.

Students will be given information on how to conduct meetings and setting agendas; how to complete minutes by including meeting minutes template and sample, contribution form to be completed by each student in each group; and timesheets to be completed by each team member in each group.

  • Assessment task 1
    Title:
    ASSIGNMENT 1 - Enterprise system - Business case development
    Description:
    In project teams, produce an appropriate business case to successfully assist an organisation in implementing an enterprise system for the first time.

    The case study in Assignment 1 and the business case forms the core information you will need for each subsequent assignment you will produce for this unit.  The focus is on implementing an enterprise system based on the information contained within the case study and the business case. To support this implementation you will work in project teams throughout the semester.

    Developing a business case is a valid and appropriate approach to support an enterprise system implementation.
    Weighting:
    30%
    Criteria for assessment:

    Students will be evaluated on the outcome of the total group assignment. Where individual components are offered, students will be marked according to the marking criteria for that individual component. The tutor will monitor individual contributions to the group when allocating marks to members of the group.

    The marking guide will provide a break down of mark allocation for individual and group components where applicable.

    Due date:
    Monday 8 April 2013
  • Assessment task 2
    Title:
    ASSIGNMENT 2 - Risk Management Strategy
    Description:
    In your project teams you will develop a risk management strategy that can be used in the implementation identified in the case study provided with Assignment 1. Your assignment should reflect your readings. You will include risk assessment, risk mitigation and risk monitoring as part of your overall risk management approach.
    Weighting:
    25%
    Criteria for assessment:

    Students will be evaluated on the outcome of the total group assignment. Where individual components are offered, students will be marked according to the marking criteria for that individual component. The tutor will monitor individual contributions to the group when allocating marks to members of the group.

    The marking guide will provide a break down of mark allocation for individual and group components where applicable.

    Due date:
    Monday 29 April 2013
  • Assessment task 3
    Title:
    ASSIGNMENT 3 - Report on the implementation approach
    Description:
    In your project teams, you will be required to produce a report on the practical approach used when implementing ERP ECC6.  The report will be based on the implementation identified in the case study provided with Assignment 1. Your teams will be required not only to provide an implementation report but also provide screen dumps of specific data screens from your input of data.

    PLEASE NOTE: We are using SAP ECC6, the latest version of SAP, and this will be administered through QUT the University Application Hosting Centre. This is a great opportunity for you to have hands on practical experience in the latest version of SAP.
    Weighting:
    15%
    Criteria for assessment:

    Students will be evaluated on the outcome of the total group assignment. Where individual components are offered, students will be marked according to the marking criteria for that individual component. The tutor will monitor individual contributions to the group when allocating marks to members of the group.

    The marking guide will provide a break down of mark allocation for individual and group components where applicable.

    Due date:
    Friday 24 May 2013

Examinations

  • Examination 1
    Weighting:
    30%
    Length:
    2 hours
    Type (open/closed book):
    Closed book
    Electronic devices allowed in the exam:
    None

Learning resources

Reading list

Recommended reading

Goldman, Rawles, Mariga. (2001). Client/Server Information Systems: A Business-Oriented Approach. New York: John Wiley & Sons Inc.

Lau., L. K. (2005). Managing Business with SAP Planning, implementation and evaluation. Melbourne: Idea Group Publishing.

Magal, S. R., & Word, J. (2011). Integrated Business Processes with ERP Systems. Hoboken, NJ:  John Wiley & Sons, Inc.

Magal, S. R. & Word, J. (2009).  Essentials of Business Processes and information Systems.  New York: Wiley & Sons.

Monk, Wagner. (2006). Concepts in Enterprise Resource Planning. Second Edition. Boston: Thompson Learning.

Sandoe, Corbitt, Boykin. (2001). Enterprise Integration. New York: John Wiley & Sons Inc

Monash Library Unit Reading List
http://readinglists.lib.monash.edu/index.html

Feedback to you

Types of feedback you can expect to receive in this unit are:
  • Informal feedback on progress in labs/tutes
  • Graded assignments with comments
  • Other: We will also provide feedback to each group member or group where appropriate.

Extensions and penalties

Returning assignments

Resubmission of assignments

Students are not required to resubmit assignments.

Referencing requirements

Students are required to be aware of the referencing requirements when creating assignments. All assignments in this unit require to be referenced where a contribution to the assignment has come from a source other than the student themselves.

The following link will provide you with an appropriate array of referencing requirements.

http://www.monash.edu/lls/llonline/quickrefs/19-styles.xml

If you are unsure about the appropriate reference style to use, please discuss this with your tutor.

Assignment submission

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).

Online submission

If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.

Required Resources

Please check with your lecturer before purchasing any Required Resources. Limited copies of prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.

On-campus students will have access to the software that they require for this unit, which is installed in the computing labs.

This will include SAP EEC6, the latest version of SAP.

Other Information

Policies

Graduate Attributes Policy

Student services

Monash University Library

Disability Liaison Unit

Students who have a disability or medical condition are welcome to contact the Disability Liaison Unit to discuss academic support services. Disability Liaison Officers (DLOs) visit all Victorian campuses on a regular basis.

Your feedback to Us

Previous Student Evaluations of this Unit

Students have found this unit interesting and informative. Changes that have been made from student feedback have included rearranging the assignments to be more in line with the lecture content and scoping the assignment content.

If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp

Other

Recommended reading – journal and conference articles

ACC (1984). ERP implementations and their issues. Proceedings of the Australian Computer Conference, Sydney, Australian Computer Society, November Edn.

  1. Journal of Computer Information Systems, Spring, 81-90.

Barati, D. Threads of success and failure in business process improvement. Located at  http://www.isixsigma.com/library/content/c070129a.asp

Managing Barriers to business Reengineering success located at:

http://www.isixsigma.com/offsite.asp?A=Fr&Url=http://www.prosci.com/w_0.htm

Roseman, M. (2001). Business process Optimisation:  Making Process Re-engineering Actually work. Coolong Consulting (Australia) Pty Ltd

Bingi, P. Sharma M.K. and Godla J.K. (1999). “Critical Issues Affecting an ERP Implementation”, Information Systems Management, Vol. 16, 3, 7-14.

Boyle., T. A., & Strong, S. E. (2006). "Skill requirements of ERP graduates." Journal of Information Systems Education 17(4): 403-412.

Curran, T. A., & Ladd, A. (2000).  SAP R/3: business Blueprint: Understanding Enterprise Supply Chain Management (2nd Edn). Sydney:  Prentice Hall  Australia Pty, Ltd.

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.

Davenport (1998).  Putting the enterprise into the enterprise system. Harvard Business Review. July-August 1998.

Davenport, T. H., (1990). The New Industrial Engineering: Information Technology and Business Process Redesign, Sloan Management Review, 31(4), Summer, 11.

Francoise, O., Bourgault., M. & Pellerin, R. (2009).  ERP implementation through critical success factors’ management.  Business Process Management Journal, 15(3), 371-394.

Hammer, M. (2000).  Reengineering work:  Don’t’ Automate Obliterate.  Harvard Business Review. July-August.

Holland, C. and Light, B. (1999). "A Critical Success Factors Model for ERP Implementation." Software, IEEE 16(3), 30-36.

  1. Business Process Management Journal, 11(2), 158-170.

Klause, H. & Rosemann, M. (2000). What is enterprise resource planning? Information Systems Frontiers (special issue of The Future of Enterprise Resource Planning Systems), 2 (2), 141-162.

Lewis, P. J. (1993). Linking Soft Systems Methodology with Data-focused Information Systems Development, Journal of Information Systems, Vol. 3, 169-186.

Markus, M.L., Axline, S., Petrie, D., & Tanis, C. (2000) Learning from adopters’ experiences with ERP: problems encountered and success achieved. Journal of Information Technology , 15, 245-265.

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/

Parr., A. & Shanks, G. (2000).  A model of ERP project implementation.  Journal of Information Technology, 15, 289-303.

Ross, J. W. (1999). “The ERP Revolution: Surviving Versus Thriving, Centre for Information System Research, Sloan School of Management, MA, August 1999.

Scott, J. E., & Vessey, I. (2002).  Managing risks in enterprise systems implementations. Communications of the ACM, April, Vol. 45, No 4. Retrieved on 19 March 2010,

Located at: http://delivery.acm.org/10.1145/510000/505249/p74-scott.pdf?key1=505249&key2=8269509621&coll=GUIDE&dl=GUIDE&CFID=80880926&CFTOKEN=57269991

Sedera, D., Gable, G., & Chan., T. (2003).  Measuring Enterprise Systems Success:  A Preliminary Model.  Ninth Americas Conference on Information Systems, 476-485.

Shang, S., & Seddon, P. B. (2002).  Assessing and managing the benefits of enterprise systems:  the business manager’s perspective. Information Systems Journal. 12, pp 271-299.

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. 1229-1698.

Skok, W., & Legge, M. (2001).  Evaluating Enterprise Resource Planning (ERP) Systems using an Interpretive Approach.  ACM.,  SIGCPR, San Diego. 189-197. (Benefit realisation

Sumner, M. (2000). "Risk factors in enterprise-wide/ERP projects." Journal of Information Technology 15(4): 317 - 327.

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. XVI, 1. Located at http://jitm.ubalt.edu/XVI-1/article1.pdf

Umble, E. J. Haft, R. R., and Umble, M. M. (2003).  Enterprise resource planning:  Implementation procedures and critical success factors.  European Journal of Operational Research, 146, 241-257.

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.

[an error occurred while processing this directive]