Enterprise Applications

Chapter 9 · Strategic Information Systems

Lecture draft

From the content sections and aligned assignments.

Chapter learning objectives

  1. Distinguish ERP, CRM, and SCM responsibilities in a cross-functional process.
  2. Trace a business event through shared records and application integrations.
  3. Evaluate configuration, customization, migration, and implementation choices.
  4. Connect customer and supplier information to appropriate work, trust, and organizational value.

ERP

Chapter 9 · Enterprise Applications

Read: ERP

Goals for this part

  • Explain Shared Data and Processes.
  • Explain Configuration and Integration.
  • Explain Implementation and Change.

Shared Data and Processes

Enterprise resource planning (ERP) supports connected core activities such as procurement, inventory, sales, accounting, production, and human resources. The scope varies by organization and product. Its central management purpose is to coordinate related work so that a business event can have consistent consequences across functions.

Shared Data and Processes

When the distributor receives goods, the event can update stock, create evidence for invoice matching, and change what sales can promise. Shared master data, such as product and supplier records, provide identifiers and definitions reused across transactions. Poor master data can spread errors more efficiently through an integrated system.

Shared Data and Processes: comparison

Event Operational consequence Related information need
Purchase order approved Supplier is authorized to supply items. Procurement and budget ownership.
Goods received Stock and receipt evidence change. Warehouse and accounting reconciliation.
Customer order fulfilled Goods leave available stock. Delivery, invoicing, and service records.

Shared Data and Processes

Read the table as coordinated consequences of events. A shared database is valuable when the organization also agrees on what each event means and who may record it.

Shared Data and Processes

An enterprise application supports important organizational activities across roles or functions. A module groups related capabilities within a broader system. A common database can provide shared records, while business process integration coordinates how related work proceeds. These arrangements can support operational excellence, but only when the records and process are dependable.

Shared Data and Processes

Master data management establishes consistent practices for important shared entities rather than allowing each module to invent incompatible customer or product definitions.

Configuration and Integration

Configuration selects supported settings and process options. Customization changes or extends the software beyond its standard behavior. Integration connects ERP with other applications or external partners. These choices affect fit, maintenance, upgrades, and the effort needed to diagnose a problem.

Configuration and Integration

The distributor might configure approval thresholds, integrate its carrier service, and customize a specialized equipment-pricing rule. The differences matter because each choice creates a different operating responsibility. A customization that depends on one consultant can become a support risk even when it works well initially.

Configuration and Integration

Integration also requires ownership of records. If both ERP and a sales application can independently change the product code, conflicting updates may occur. A design should specify the authoritative source for each data element, when updates are exchanged, and how failures are reconciled.

Configuration and Integration

Successful message delivery is useful evidence, but managers also need to know that the receiving process used the update correctly.

Configuration and Integration

Application integration connects the behavior and information of separate applications, often using an API or an exchange service. SaaS delivers the application as a provider-operated service. Both can create vendor lock-in when specialized configuration, records, or connections are difficult to move.

Configuration and Integration

Managers should evaluate these choices alongside process fit, rather than assuming that a shared database or subscription removes every integration responsibility.

Implementation and Change

ERP implementation is organizational change as well as software deployment. It includes agreeing on process definitions, preparing records, assigning roles, testing related activities, and supporting employees as work changes. A standard process can simplify coordination while also conflicting with a useful local practice.

Implementation and Change

For the distributor, testing should follow a transaction across departments: order, reservation, shipment, invoice, payment, and exception. A demonstration showing that each screen opens does not establish that the complete process is dependable. User acceptance should include realistic records and unusual but important cases.

Implementation and Change

Subscription delivery and embedded AI do not remove these responsibilities. A provider may operate the application while the organization remains responsible for roles, data, process choices, and consequential uses of generated recommendations. Benefits should be evaluated after the change through outcomes such as fewer reconciliation errors or more reliable order completion.

Implementation and Change

Installation is a milestone, not the definition of enterprise value.

Implementation and Change

A package may include a recommended best practice, meaning a proposed way to organize work based on the supplier's experience or design assumptions. It still needs evaluation for the organization. Change management prepares people and responsibilities for the new arrangement. Data conversion transforms records into the form required by the new system.

Implementation and Change

A converted date can be syntactically valid while representing the wrong event, so business interpretation belongs in migration checks.

Quick check

Name the concept that completes this statement.

________ supports connected core activities such as procurement, inventory, sales, accounting, production, and human resources.

Quick check

Name the concept that completes this statement.

________, such as product and supplier records, provide identifiers and definitions reused across transactions.

Your turn

Use the chapter case: Three systems, one customer order.

Assign ERP, CRM, and SCM responsibilities and identify shared records, owners, and distinct business events.

Prepare a brief explanation with a stated assumption and an outcome measure.

Recap

ERP coordinates events and records across functions. Its value depends on shared definitions, manageable extensions, realistic process testing, and sustained ownership.

CRM

Chapter 9 · Enterprise Applications

Read: CRM

Goals for this part

  • Explain Customer Data and Touchpoints.
  • Explain Sales, Service, and Marketing.
  • Explain Data Quality and Trust.

Customer Data and Touchpoints

Customer relationship management (CRM) is an approach to managing customer interactions and the information needed to support them. CRM systems can connect sales, service, marketing, and other touchpoints. A touchpoint is an interaction through which a customer experiences the organization, including a call, store visit, website interaction, or service request.

Customer Data and Touchpoints

A shared customer record can help employees see relevant history, but building that record requires decisions about identity, duplicates, access, and purpose. Two accounts may represent one person, while several people may legitimately share a business account. Treating every matching email address as one individual can create a misleading history.

Customer Data and Touchpoints

For the distributor, a useful record connects the customer organization, authorized contacts, orders, and unresolved service issues. Employees should receive the information needed for their task rather than unrestricted access to every customer detail. More collected data do not automatically produce a more trustworthy relationship.

Sales, Service, and Marketing

Sales uses CRM to organize potential opportunities and customer commitments. Service uses it to record issues, route work, and track resolution. Marketing uses customer information to plan and evaluate communications or offers. These purposes overlap, but they need clear connections and limits.

Sales, Service, and Marketing

A salesperson's promise creates work for operations and service. If the promise is recorded only in a private note, another team may unknowingly contradict it. Conversely, a marketing campaign that ignores an unresolved complaint can damage the relationship even when the campaign is delivered correctly.

Sales, Service, and Marketing: comparison

Function Information it contributes Coordination need
Sales Requirements and commitments Confirm what the business can deliver.
Service Problems and resolution history Make unresolved issues visible to authorized staff.
Marketing Offers and communication responses Respect preferences and relevant service context.

Sales, Service, and Marketing

Operational CRM supports these interactions and workflows. Analytical CRM examines customer-related patterns. An analysis showing that customers with more service calls leave more often does not by itself establish that reducing calls will improve retention; the underlying service problems may explain both.

Sales, Service, and Marketing

Customer lifetime value estimates the economic contribution of a customer relationship over a defined horizon, using assumptions about revenue, cost, retention, and sometimes the timing of money. It is an estimate, not a person's intrinsic worth. A ranking based on it can be misleading when service costs are missing or when assumptions change.

Sales, Service, and Marketing

Managers should also consider service commitments and fairness rather than treating the estimate as the sole basis for attention.

Data Quality and Trust

Customer trust depends partly on what the organization does with information and whether its promises are dependable. An inaccurate record can lead to a repeated complaint, an inappropriate offer, or disclosure to the wrong person. Trust cannot be installed as a software feature.

Data Quality and Trust

The distributor needs a way to correct records, reconcile duplicate accounts, preserve meaningful histories, and record relevant communication preferences. Staff should know which record is authoritative and which information is only an uncertain note. Quality controls should be designed around actual uses rather than assuming that every field must be available to everyone.

Data Quality and Trust

AI-assisted summaries or recommendations add another need for review. A fluent summary may omit a disputed fact or convert a tentative note into an apparent commitment. Employees need access to the underlying evidence and authority to correct the record.

Data Quality and Trust

CRM contributes to a relationship when the resulting work is more coherent, useful, and respectful, rather than simply more personalized.

Quick check

Name the concept that completes this statement.

________ is an approach to managing customer interactions and the information needed to support them.

Quick check

Name the concept that completes this statement.

A ________ is an interaction through which a customer experiences the organization, including a call, store visit, website interaction, or service request.

Your turn

Use the chapter case: Three systems, one customer order.

Assign ERP, CRM, and SCM responsibilities and identify shared records, owners, and distinct business events.

Prepare a brief explanation with a stated assumption and an outcome measure.

Recap

Connect interactions to the work of maintaining the customer relationship. Shared records need identity rules, appropriate access, accurate interpretation, and dependable follow-through.

SCM

Chapter 9 · Enterprise Applications

Read: SCM

Goals for this part

  • Explain Suppliers and Logistics.
  • Explain Planning and Visibility.
  • Explain Risk and Resilience.

Suppliers and Logistics

Supply chain management (SCM) coordinates the flows and activities linking suppliers, the focal organization, intermediaries, and customers. An SCM application can support information exchange about purchases, production, stock, transportation, and fulfillment. Its role is broader than tracking the location of a vehicle.

Suppliers and Logistics

The distributor must distinguish what it ordered, what the supplier confirmed, what actually shipped, and what arrived. These events have different consequences. A shipment notice supports preparation for receipt, but it is not proof that usable stock is available.

Suppliers and Logistics

A shared supplier record, product identifier, and order reference help connect the events. Access and exchange agreements also matter because partners may have different systems and commercial interests. Managers should identify which information must be shared, why it is needed, and who is responsible when a quantity or date changes.

Planning and Visibility

Supply chain planning uses information about demand, inventory, capacity, and constraints to prepare future actions. Execution concerns carrying out activities such as releasing orders, receiving goods, and dispatching shipments. Applications can connect planning and execution, but a plan remains conditional on the information and assumptions behind it.

Planning and Visibility

Visibility is the ability to obtain relevant information about the state of work or resources. It is useful when the information is timely, meaningful, and connected to someone able to respond. A dashboard of late shipments cannot resolve the shortage unless a responsible person can adjust the plan.

Planning and Visibility: comparison

Application information Business meaning Possible action
Forecast demand Expected demand, with uncertainty Plan capacity or purchasing.
Confirmed supplier order A partner's stated commitment Prepare receipt and monitor changes.
Actual receipt Recorded goods that arrived Inspect, reconcile, and update usable stock.

Planning and Visibility

Separating the states prevents a planning estimate from being mistaken for a completed event. Integration should preserve that distinction.

Risk and Resilience

SCM applications can expose dependencies and exceptions, but they do not eliminate supplier failure, disruption, or uncertainty. A forecast based on a single supplier's promised capacity can look precise while leaving a major dependency unexamined. Managers need to know which assumptions make the plan feasible.

Risk and Resilience

The distributor might configure alerts for a changed shipment date and link the alert to customer orders affected by the delay. The workflow should identify who evaluates alternatives, who approves changes, and who communicates revised promises. Without those responsibilities, the alert adds information without improving resilience.

Risk and Resilience

Implementation choices also create risk. Poor record mapping can make stock appear twice, and a failed interface can leave teams using stale data. Application evaluation should therefore include reconciliation, exception handling, and continuity of essential work. {doc}Supply Chain <../11_supply_chain/1100_supply_chain> examines the operational choices behind sourcing, buffers, logistics, and recovery.

Quick check

Name the concept that completes this statement.

________ coordinates the flows and activities linking suppliers, the focal organization, intermediaries, and customers.

Quick check

Name the concept that completes this statement.

________ uses information about demand, inventory, capacity, and constraints to prepare future actions.

Your turn

Use the chapter case: Three systems, one customer order.

Assign ERP, CRM, and SCM responsibilities and identify shared records, owners, and distinct business events.

Prepare a brief explanation with a stated assumption and an outcome measure.

Recap

SCM applications connect planning and execution records across organizational boundaries. Evaluate the meaning of each state, the quality of exchanged information, and the actions that follow exceptions.

Reading and assignments