BISM1201 Chap.4 Enterprise Systems and Integration
Enterprise Systems and Integration
Enterprise systems coordinate shared data and processes across organisational boundaries. ERP capabilities integrate core internal resources and transactions; CRM capabilities organise customer-facing history and interactions; SCM capabilities connect demand, supply, inventory and logistics. Their value comes from common definitions and controlled process consequences, not from the application label.
Integration may reduce duplicate entry and improve visibility while increasing migration, concentration and change risk. A shared database does not automatically create one truth. Data ownership, master-data rules, access control, reconciliation and interface monitoring are what make shared information dependable.
What this chapter covers
- 01
ERP, CRM and SCM coordination roles
- 02
Shared records and cross-functional consequences
- 03
Process standardisation and local variation
- 04
Data migration, cutover and reconciliation
- 05
Interface monitoring, access and data governance
Integrating a multi-store repair service
- +1Standardise product, customer and inventory identifiers needed across stores.
- +1Integrate stock movements and customer history into authoritative shared records.
- +1Keep justified local appointment rules while connecting booking outcomes.
- +1Profile, cleanse, map and reconcile legacy data before cutover.
- +1Measure duplicates, stock accuracy, wait time and interface failures with named owners.
Key terms
- Enterprise system
- A coordinated platform for shared data and processes that span multiple organisational functions or locations.
- ERP capability
- Integrated support for internal resources and transactions such as procurement, operations, inventory and finance.
- CRM capability
- Coordinated customer information and interactions across acquisition, sales, service and retention activities.
- SCM capability
- Information and process support for demand, supply, inventory, partners and logistics across a value network.
- Master data
- Controlled shared definitions for core entities such as products, customers, suppliers and locations.
- Data migration
- The profiled, mapped, cleansed, converted and reconciled movement of data into a new operational environment.
Enterprise Systems and Integration FAQ
What is the main benefit of enterprise integration?
Integration lets one controlled event update the records and processes that depend on it, reducing duplicate capture and improving visibility. The benefit appears only when definitions, ownership and controls are aligned.
Should every local process be standardised?
No. Standardise where shared definitions, control or coordination create value. Preserve justified variation where regulation, customers or operating conditions differ, while connecting the information that other processes genuinely need.
Why is data migration more than copying files?
Legacy values may use different definitions, formats and quality rules. Migration must profile and cleanse data, map meanings, test conversion and reconcile important totals so the new system preserves business meaning.
How can an interface fail even when both systems work?
Messages can be delayed, rejected, duplicated or transformed incorrectly. Monitoring, reconciliation, retry rules and an exception owner are necessary because automatic transfer can otherwise fail without a visible user error.
Exam move
Build a three-column table for ERP, CRM and SCM with coordinated process, shared record and decision enabled. For every integration case, identify the authoritative record, downstream consequences, migration risk and exception control.
Practise arguing both for standardisation and for a justified local variation so your answer is based on fit rather than maximum centralisation.
Use an event walk-through to revise integration. Choose one order, customer update or supplier delivery and list every record and process consequence it should create. Mark which system is authoritative, which interfaces carry the event and who investigates a rejection.
Repeat the exercise with a correction and a duplicate. The normal path shows coordination value; the exception paths show whether the design is governable.
Build a migration checklist around meaning, not file movement. For five legacy fields, record current definition, new definition, transformation rule, data owner, quality issue and reconciliation test. Add a cutover scenario in which old and new totals disagree.
Decide whether to pause, correct or proceed, and state who has authority. This exercise reveals why migration is business analysis and control work.
For each case answer, write one paragraph supporting common process and one supporting local variation. Decide using coordination need, regulation, customer difference and change burden.
If an interface is chosen instead of one suite, add monitoring, retry and reconciliation. End with measures for shared-data quality and process outcome. Do not count the number of connected applications as success; count whether the right information reaches the right decision reliably.
Create a cutover rehearsal with opening balances, transactions in flight and one rejected interface message.
Reconcile record counts and important totals between legacy and target systems, then decide which discrepancies prevent release. Trace a corrected master-data value into every dependent process. Include access approval, fallback, communication and post-cutover monitoring. This rehearsal connects integration architecture to operational continuity and makes the phrase single source of truth testable rather than rhetorical.
