Professional Documents
Culture Documents
Building Organizational Partnerships Using Enterprise Information Systems
Building Organizational Partnerships Using Enterprise Information Systems
Chapter
1
Learning Objectives
2
Learning Objectives
3
Enterprise Systems
• Problem:
o Information systems growing over time
o Lack of integration
• Different computing platforms
• Difficult to integrate
• Data must be reentered from one system to
another
• Same pieces of data stored in several versions
4
Legacy System Approach
5
Enterprise System Approach
6
Supporting Business Activities
• Internally focused systems
o Support functional areas, business processes and decision-
making within an organization
o New information (value) is added at every step
• Interorganizational
systems
o Streamline the flow
of information
between companies
8
Internally Focused Systems: Value Chain
• Flow of information through a set of business activities
o Core activities – functional areas that process inputs and
produce outputs
o Support activities – enable core activities to take place
10
Core Activities (II)
• Marketing and Sales activities
• Presale marketing activities (e.g., creating
marketing brochures)
• Amtrak – use of IS to update prices and
schedules
11
Support Activities
• Administrative activities
• Support of day-to-day operations (for all functional
areas)
• Infrastructure activities
• Implement hardware and software needed
• Human resource activities
• Employee management
12
Support Activities
• Technology development activities
• Design and development of applications to support
the primary activities
• Procurement activities
• Purchasing of goods and services (inputs into the
primary activities)
13
Externally Focused Applications – Value
System
• Coordination of multiple value chains
14
Externally Focused Applications – Value
System
• Information Flows in a Value System
o Upstream information flow – information received from another
company
o Downstream information flow – information produced by a company
and sent to another organization
15
The Rise of Enterprise Systems
• Packaged applications
o Written by third-party vendors
o Used by many different organizations
o Useful for standardized, repetitive tasks
o Cost effective
o E.g., Microsoft Money and Quicken
16
The Rise of Enterprise Systems
• Custom applications
o Developed exclusively for a specific
organization
o Designed for particular business needs
o Higher development costs
17
Evolution of Enterprise Systems
• Enterprise
systems
o Organizations
start with stand-
alone
applications
o Legacy systems
18
Legacy Systems
• Each department has its own system
o Infrastructure specific
o Inefficient processes
o Potential for inaccuracies
20
Vanilla Versus Customized Software
• Vanilla version
o Modules the version comes with out of the
box
o Certain processes might not be supported
• Customization
o Additional software or changes to vanilla
version
o Always needs to be updated with new
versions of vanilla
21
Best Practices-Based Software
• Most ERP vendors build best practices into
their ERP systems
o Identify business processes in need of change
o Future updates are smoother if businesses change
their business processes to fit with ERP systems
• Is following the best practices always the best
strategy?
o If companies have competitive advantage from
unique business processes
22
Learning Objectives
23
Business Process Management
• Systematic and structured improvement approach
o All or part of organization is involved
o Rethinking and redesign of business processes
• Became popular in 1990s
• IS seen as key enabler for radical change
• Process intended to be cross-functional
24
BPM Steps
1. Develop a vision for the organization (specify
business objectives)
2. Identify critical processes that are to be
redesigned
3. Understand and measure existing processes
as a baseline
4. Identify ways IS can be used for improvement
5. Design and implement a prototype of the new
processes
25
Conditions Leading to a Successful BPM
• Data warehouse
o Large,
centralized data
repository
o Single place for
data storage and
access
27
Choosing an ERP System
• Control
o Centralized control vs. control within specific
business units
o Level of detail provided to management
o Consistency of policies and procedures
• Business requirements
o Selection of modules
• Core and extended components
28
Core and Extended ERP Components
• Core components – support primary internal activities
• Extended components – support primary external
activities
29
ERP Limitations
• ERP falls short in communicating across
organizational boundaries
• Not well suited for managing value
system activities
o Other systems can work with ERP to provide
these capabilities
30
Learning Objectives
31
Customer Relationship Management
32
Customer Relationship Management
• Web has changed the business
o Customers have the power
o Transactions vs. relationships
o Keeping customers satisfied is key
• CRM
o Corporate-level strategy
o Concentrates on the downstream information flow
• To attract potential customers
• Creation of customer loyalty
o Managers need to be able to monitor and analyze
factors driving customer satisfaction
33
Key Benefits of CRM
1. Enables 24/7/365 operations
2. Individualized service
3. Improved information
4. Speeds up problem identification/resolution
5. Speeds up processes
6. Improved integration
7. Improved product development
8. Improved planning
34
Developing a CRM Strategy
• More than just
software
purchase and
installation
• Enterprise-wide
changes
35
Policy and Business Process Changes
• Policies and
procedures need
to reflect
customer-
focused culture
36
Customer Service Changes
• Customer-focused
measures of
quality
• Process changes
to enhance
customer
experience
37
Employee Training Changes
• Employees from
all business
areas must
value customer
service and
satisfaction
38
Data Collection, Analysis and Sharing
Changes
• All aspects of
customer
experience must
be tracked,
analyzed and
shared
• Consider ethical
concerns
39
Architecture of a CRM
40
Operational CRM
• Systems for customer
interaction and
service
o Personalized and
efficient customer
service
o Access to complete
information about
customer
41
Sales Force Automation
• Component of operational CRM
• Primary goals
o Identification of potential customers
o Streamlining of selling processes
o Improvement of managerial information
42
Sales Force Automation
• Supports day-to-day sales activities
o Order processing and tracking
o Contact development, assignment and
management
o Customer history preferences
o Sales forecasting and performance analysis
o Sales administration
43
Advantages of Sales Force Management Systems
for Sales Personnel
1. Product flow
o Flow of product from supplier to consumer
o Automation of product returns
2. Information flow
o Complete removal of paper documents
o Access to current information at all times
3. Financial flow
o Automatic flow of payments
Information Systems Today: Managing in the Digital World 8-61
Developing an SCM Strategy
• SCM efficiency and effectiveness need to be
balanced
o Efficiency – cost minimization
o Effectiveness – customer service maximization