Skip to the content | Change text size
PDF unit guide

FIT3012 Enterprise systems - Semester 2, 2009

Chief Examiner:

Ms Susan Foster
Lecturer
Phone: +61 3 990 32404

Lecturer(s) / Leader(s):

Clayton

Ms Susan Foster
Lecturer
Phone: +61 3 990 32404

Additional communication information:

Sue Foster

Contact details:

H7.58 H Block, Caulfield School of IT

Telephone:  99032404

Email:  Sue.Foster@infotech.monash.edu.au

Introduction

Welcome to FIT3012 Enterprise Systems for semester 2, 2008. This 6 point unit is a core unit of the eBusiness ERP stream in BBIS at the third year level. This unit has been designed to provide you with both theoretical and practical overview of Enterprise Systems. Enterprise Systems are configurable information systems packages that integrate information and information-based processes within and across functional areas in an organization. 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.

Unit synopsis

This unit provides both a theoretical and practical overview of Enterprise Systems. Enterprise Systems are configurable information systems packages that integrate information and information-based processes within and across functional areas in an organization. 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.

Learning outcomes

Upon successful completion of this unit students should be able to:
  1. Describe the characteristics of an Enterprise System that distinguishes it from other software systems. This focus is particularly on the concept of an integrated enterprise solution;
  2. Explain the benefits of enterprise systems in terms of integration, world-wide flexibility, interactive processing, client-server platform, open systems, and the capacity to be configured for all business types;
  3. Explain the application modules and system architecture of an enterprise system;
  4. Describe an enterprise system's features and functionality that support business processes;
  5. Explain the stages of an enterprise systems implementation lifecycle;
  6. Describe the technical architecture and integration of enterprise systems;
  7. Explain the planning and implementation approaches for enterprise systems;
  8. Discuss the communication, people handling and team management skills required of an enterprise system's implementation manager;
  9. Explain implementation project team responsibilities using examples from actual business cases;
  10. Discuss the major factors behind the success and failure of enterprise systems implementation projects using both theoretical knowledge and actual business cases;
  11. Demonstrate a capacity to describe and perform navigation functions of an enterprise systems system;
  12. Describe system-wide concepts such as workflow, archiving, reporting, and the exchange of information between business partners and employees;
  13. Explain system-wide features including the customization of organizational elements, master data, configuration and security;
  14. Identify and critically discuss the impact on implementation of external influences, organisational structure, and stakeholders;
  15. Describe four main business processes and how they integrate with each other to represent an entire enterprise;
  16. Explain the processes and issues involved in configuration of an enterprise system.

Contact hours

4 x contact hrs/week

Workload

12 hours per week, nominally including 2 hours of lectures and 2 hours of laboratory work.

Unit relationships

Prerequisites

Completion of 12 points from FIT

Relationships

FIT3012 is a core unit in the Bachelor of Business Information Systems.

Before attempting this unit you must have satisfactorily completed 12 points of FIT units, or equivalent.

Teaching and learning method

Timetable information

For information on timetabling for on-campus classes please refer to MUTTS, http://mutts.monash.edu.au/MUTTS/

Tutorial allocation

On-campus students should register for tutorials/laboratories using the Allocate+ system: http://allocate.cc.monash.edu.au/

Unit Schedule

Week Topic Key dates
1 Introduction to Enterprise systems 20 July 2009
2 Enterprise system Issues 27 July 2009
3 Enterprise System - Vendor products 3 August 2009
4 Enterprise systems - implementation issues 10 August 2009
5 Enterprise systems - implementation issues 17 August 2009
6 Enterprise systems - implementation issues 24 August 2009
7 Enterprise systems - implementation issues 31 August 2009
8 Enterprise systems - implementation issues 7 September 2009
9 Enterprise systems - Change management 14 September 2009
10 Enterprise systems - change management 21 September 2009
Mid semester break
11 Enterprise systems - Benefit realisation 5 October 2009
12 Enterprise systems - future issues 12 October 2009
13 Revise and review 19 October 2009

Unit Resources

Prescribed text(s) and readings

There are no prescribed texts, therefore please turn your attention to the recommended readings as described below.

Recommended text(s) and readings

Brady J.A., Monk E.F. and Wagner B.J., Concepts in Enterprise Resource Planning, Course Technology (2001)

Bancroft N. H., Seip H. and Sprengal A., Implementing SAP R/3, 2nd Edition, Manning (1996)

Curran T., Keller G, and Ladd A., SAP R/3 Business Blueprint, Prentice Hall (1998)

Shanks G., Seddon P.B. and Willcocks L.P., Second-Wave Enterprise Resource Planning Systems Implementing for Effectiveness, Cambridge University Press (2003)

O'Leary D. E., Enterprise Resource Planning Systems Systems, Life Cycle, Electronic Commerce, and Risk., Cambridge University Press (2000)

Required software and/or hardware

SAP ECC6

Equipment and consumables required or provided

Students studying off-campus are required to have the minimum system configuration specified by the Faculty as a condition of accepting admission, and regular Internet access. On-campus students, and those studying at supported study locations may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook. You will need to allocate up to n hours per week for use of a computer, including time for newsgroups/discussion groups.

Study resources

Study resources we will provide for your study are:

  • Weekly detailed lecture notes outlining the learning objectives, discussion of the content, required readings and  exercises;
  • Weekly tutorial or laboratory tasks and exercises with sample solutions provided one to two weeks later;
  • Assignment specifications ;
  • A sample examination and suggested solution
  • This Unit Guide outlining the administrative information for the unit;
  • The unit web site on MUSO, where resources outlined above will be made available.

Assessment

Overview

Examination: 60%; Assignments: 40%. Students must pass the examination in order to pass the unit.

Faculty assessment policy

To pass a unit which includes an examination as part of the assessment a student must obtain:

  • 40% or more in the unit's examination, and
  • 40% or more in the unit's total non-examination assessment, and
  • an overall unit mark of 50% or more.

If a student does not achieve 40% or more in the unit examination or the unit non-examination total assessment, and the total mark for the unit is greater than 44% then a mark of no greater than 44-N will be recorded for the unit.

To pass this unit, a student must obtain :
  • 40% or more in the unit's examination and
  • 40% or more in the unit's non-examination assessment
     and
  • an overall unit mark of 50% or more
If a student does not achieve 40% or more in the unit examination or the unit non-examination assessment then a mark of no greater than 44-N will be recorded for the unit.

Assignment tasks

Assignment coversheets

Assignment coversheets are available via "Student Forms" on the Faculty website: http://www.infotech.monash.edu.au/resources/student/forms/
You MUST submit a completed coversheet with all assignments, ensuring that the plagiarism declaration section is signed.

Assignment submission and return procedures, and assessment criteria will be specified with each assignment.

  • Assignment task 1
    Title:
    Implementation issues in Enterprise systems - Part 1
    Description:
    This assignment will be based on a case study approach where you will be required to research an implementation issue.
    Weighting:
    20%
    Due date:
    Monday 26 August 2009
  • Assignment task 2
    Title:
    enterprise systems Implementation outcomes - Part 2
    Description:
    This assignment follows the case study provided in Part 1.  You will be required to build on the outcomes of the implementation to research areas related to benefit realisation for example.
    Weighting:
    20%
    Due date:
    5 October 2009

Examination

  • Weighting: 60%
    Length: 2 hours
    Type (open/closed book): Closed book
    Remarks:

    the exam will cover all content referred to in the twelve topics identified in this unit.

See Appendix for End of semester special consideration / deferred exams process.

Due dates and extensions

Please make every effort to submit work by the due dates. It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are not regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.

Students requesting an extension for any assessment during semester (eg. Assignments, tests or presentations) are required to submit a Special Consideration application form (in-semester exam/assessment task), along with original copies of supporting documentation, directly to their lecturer within two working days before the assessment submission deadline. Lecturers will provide specific outcomes directly to students via email within 2 working days. The lecturer reserves the right to refuse late applications.

A copy of the email or other written communication of an extension must be attached to the assignment submission.

Refer to the Faculty Special consideration webpage or further details and to access application forms: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html

Late assignment

Assignments received after the due date will be subject to a penalty of [describe penalty for late submission, describe the deadline for late assignment acceptance or any conditions that are placed on late assignments, e g, "Assignments received later than one week after the due date will not normally be accepted."]

Return dates

Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.

Appendix

Please visit the following URL: http://www.infotech.monash.edu.au/units/appendix.html for further information about:

  • Continuous improvement
  • Unit evaluations
  • Communication, participation and feedback
  • Library access
  • Monash University Studies Online (MUSO)
  • Plagiarism, cheating and collusion
  • Register of counselling about plagiarism
  • Non-discriminatory language
  • Students with disability
  • End of semester special consideration / deferred exams