0% found this document useful (0 votes)
12 views4 pages

INTM 446/546 Midterm Exam Guide

The midterm exam for INTM 446/546 will be administered online through Blackboard using Respondus Lockdown Browser in computer lab SB 112E from 6:25pm to 9:05pm. Students should focus their studying on chapters 1 through 8 of the Modern ERP textbook and lesson 1 of Infor Cloudsuite Industrial, with a particular emphasis on terminology and concepts discussed in each chapter. The exam will contain 40-45 total questions, including 3-7 short answer questions and 35-40 multiple choice or true/false questions. Students are permitted to bring two sheets of notes (4 sides total) to refer to during the exam.

Uploaded by

Sidharth
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views4 pages

INTM 446/546 Midterm Exam Guide

The midterm exam for INTM 446/546 will be administered online through Blackboard using Respondus Lockdown Browser in computer lab SB 112E from 6:25pm to 9:05pm. Students should focus their studying on chapters 1 through 8 of the Modern ERP textbook and lesson 1 of Infor Cloudsuite Industrial, with a particular emphasis on terminology and concepts discussed in each chapter. The exam will contain 40-45 total questions, including 3-7 short answer questions and 35-40 multiple choice or true/false questions. Students are permitted to bring two sheets of notes (4 sides total) to refer to during the exam.

Uploaded by

Sidharth
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

INTM 446 / 546 – Midterm Exam Study Guide

 Exam will be administered online through Blackboard using Respondus Lockdown Browser
o We will utilize a computer lab in Stuart Building (SB) 112E
o Make sure you have your Login ID and Password available to log into Blackboard from the lab
o You must use the computer in the computer lab. You can not use your laptop in the lab
o No book, no phones, no laptop, no tablet
o Questions will be given in random order
o You will be able to come back and change answers to prior questions you already answered
o Full class time will be available for the exam. We will start at 6:25pm and end at 9:05pm
 Any topic which was discussed in class is fair game for questions.
 Test content:
o 40 to 45 questions in total
o 3 to 7 short answer
o 35 to 40 multiple choice and true/false
 Reminder, you are allowed 2 sheets of 8.5 x 11 double sided paper to bring in to the exam as notes (4 sides of
notes in total). Can be typed or handwritten
 Focus will be on content from Modern ERP textbook, chapters 1 through 8 and Infor, lesson 1

Modern ERP Textbook:


Chapter 1 – Introduction to Enterprise Resource Planning Systems:

1. Terminology:
a. ERP system
i. Pros and Cons
b. Business process
c. Legacy systems
i. Pros and Cons
d. Cloud ERP (or SaaS)
e. Instances
f. Tiers
g. Modules
h. Clients
i. Configuration
j. Ownership
k. Segregation
l. Integration
m. Functionally-oriented systems
n. Cross functional systems
o. Process-centered systems
p. Integrated systems
q. Best practice
r. Application control
s. Core competency
2. Names of the Tier 1 ERP vendors (per the textbook)
3. Suite of modules considered part of Core ERP
4. Suite of modules NOT considered part of Core ERP
5. Movements of configurations and customizations go from DEV to QA to PRD
Chapter 2 - ERP Technology:

1. Terminology:
a. Mainframe architecture
b. Client-server computing
c. Distributed computing
d. Types of data
i. Configuration
ii. Transactional
iii. Master
e. Examples of types of data from each part in (d) above
f. Entity integrity rule
g. Referential integrity rule
2. On-premise vs. Cloud ERP systems
a. Pros and Cons of each type
3. Aspects of a well-structured database
4. Reasons why a company would want to use Cloud for their ERP systems
5. ERP server landscape and ERP instances (differences and when each are used and why)
a. DEV, QA, and PRD
6. Who has access to DEV, QA, and PRD

Chapter 3 - ERP and Business Process Redesign

1. Terminology
a. Business Process
b. Business Process Reengineering (BPR)
c. Business Process Improvement (BPI)
d. Shared service
e. Internal control
f. Process hierarchy
g. Handoffs
h. Intermediaries
i. Rework
j. Bottleneck
k. Segregation of Duties (SOD)
2. Reengineering (BPR) principles
3. Optimal Business Process Criteria
4. Differences in BPI versus BPR

Chapter 4 – ERP and Process Map

1. Terminology
a. As-is Process Map
b. To-be Process Map
c. Swim Lane
2. How and why process maps are used
Chapter 5 – ERP Life Cycle: Planning and Package Selection

1. Terminology
a. ERP life cycle
b. Steering Committee
c. Project Team
d. Project Manager
e. Program Manager
f. Super User
g. Project Scope
h. Project charter
i. Project timing
j. Center of Excellence
k. Change management
2. Business case rationales for ERP system (4 of them)
3. Benefits of process mapping
4. Methods of process mapping
a. Self-generate method
b. Group interview method
c. One-on-one interview method
5. Steering committee responsibilities
6. Areas that impact ERP implementation costs
7. Lower cost versus higher cost areas of ERP implementation
8. Organizational readiness for implementing ERP
a. Change management
b. Culture

Chapter 6 – ERP Life Cycle: Implementation and Operation and Maintenance

1. Terminology
a. ERP customization
i. User exit
ii. Enhancement
iii. Retro fit
iv. Modification
b. Scope creep
c. Consultants
d. Best-of-Breed ERP
e. Vanilla ERP
f. Integration testing
g. Performance load testing
h. Unit testing
i. Customer acceptance testing
j. Data extraction
k. Data collection
l. Data cleansing
m. Data harmonization
2. ERP customization: Advantages and disadvantages
3. Organizational readiness for implementing ERP
a. Change management
b. Culture
4. ERP Implementation approaches
a. Phased Implementation Strategy
b. Big Bang Implementation Strategy
c. Hybrid Implementation Strategy
d. Parallel Implementation Strategy

Chapter 7 – ERP Financial Management

1. Terminology
a. Direct costs
b. Indirect costs
c. Profitability analysis
d. Activity Based Costing
e. Product costing
f. Cash Management
2. Examples of direct costs and indirect costs

Chapter 8 – ERP Sales, Customer Relationship Management, and Knowledge Management

1. Terminology
a. Customer Relationship Management (CRM)
2. Metrics used to measure CRM

Infor Cloudsuite Industrial (CSI)


Lesson 1: Introduction to CloudSuite Industrial Fundamentals - 101
1. Foundation 101 Overview

Common questions

Powered by AI

Process mapping is essential during the ERP lifecycle as it helps in understanding existing processes ('as-is') and designing future processes ('to-be') that align with organizational goals. It aids in identifying inefficiencies, redundancies, and areas for improvement . During the planning and package selection phases, process mapping informs the selection of a suitable ERP package that best fits the needs of the organization, ensuring that the chosen system supports optimized processes .

The Phased Implementation Strategy involves segments of the ERP system being implemented over time, allowing for gradual adaptation . Big Bang Implementation entails launching the entire ERP system at once, which can be riskier but ensures faster adoption . The Hybrid Strategy combines aspects of both phased and big bang approaches to balance risk and speed. Parallel Implementation runs the new ERP system alongside the old one temporarily, reducing risk but increasing cost and complexity .

On-premise ERP systems offer greater control over data and system customization but require substantial upfront investment for hardware and infrastructure, along with ongoing maintenance costs . Cloud-based ERP systems (SaaS) offer scalability, faster deployment, and lower initial costs, but can be limited by less control over customization and potential data security concerns . Pros of cloud deployment also include ease of updates and reduced need for in-house IT expertise.

BPR involves fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in critical measures such as cost, quality, service, and speed . It is often more radical and involves significant changes to how business processes are structured. Conversely, BPI is more incremental and focuses on enhancing existing processes through continuous improvements rather than complete overhauls . BPI is less disruptive than BPR and tends to focus on smaller-scale changes aimed at enhancing efficiency and effectiveness.

In ERP configurations, "best practice" refers to pre-defined processes or configurations considered most efficient or effective, often based on industry standards . Implementing these can lead to streamlined processes, improved efficiency, and reduced customization needs. However, adherence to best practices might limit an organization's flexibility and uniqueness if not aligned with their specific business strategies and objectives .

Organizational readiness for ERP implementation is heavily influenced by change management and culture. Change management involves preparing, supporting, and helping individuals and teams in making organizational change, which is critical to overcoming resistance and ensuring smooth adoption of new systems . Cultural aspects, such as openness to change, leadership alignment, and willingness to embrace new technologies, play significant roles in determining how well an organization adapts to ERP implementation .

Entity integrity ensures that each table in a database has a primary key that uniquely identifies records, preventing duplication and maintaining accurate data . Referential integrity ensures that relationships between tables remain consistent, whereby foreign keys correctly point to primary keys in related tables, avoiding orphan records and maintaining data consistency across the database . Both rules are fundamental to the reliability and coherence of data in ERP systems.

ERP customization can significantly increase project costs due to additional development time, required expertise, and long-term maintenance of custom features . Customization can also lead to complexities in system upgrades and integration challenges down the line. While it can tailor an ERP system better to fit organizational needs, extensive customization often leads to scope creep and may negatively impact project timelines and budgets if not managed carefully .

Change management is crucial in ERP implementation as it deals with the human aspects of changing business processes. It helps in mitigating resistance, enhancing acceptance, and ensuring smooth transitions . Strategies to address resistance include effective communication, involving employees early in the project, training programs, and demonstrating the benefits of the new system. Emphasizing a culture of ongoing learning and adaptation also helps in minimizing pushbacks .

Segregation of Duties (SOD) is a crucial internal control principle used to ensure that no single individual has control over all aspects of any critical business process. This prevents fraud and errors by dividing responsibilities among multiple people . In ERP systems, SOD is vital to maintaining data integrity and protecting against unauthorized data manipulation by delineating access controls and avoiding conflicts of interest in roles .

You might also like