Business Information Systems

Two Examples of Computer-Based Reservation Systems

Two prominent, real-world examples of Computer-Based Reservation Systems (CBRS) are:

1. Amadeus / Sabre Global Distribution System (GDS): Enterprise travel reservation networks that connect airlines, hotels, car rental agencies, and travel agents worldwide for real-time inventory checking, seat booking, and ticketing.
2. IRCTC (Indian Railway Catering and Tourism Corporation) / Airline Web Booking Portals: Consumer-facing computerized passenger reservation systems handling millions of concurrent seat reservations, ticket cancellations, dynamic seat allocations, and payment gateway transactions.

What is an Information System?

An Information System (IS) is a formal, sociotechnical arrangement of interrelated components—including Hardware, Software, Data, People, Procedures, and Telecommunication Networks—that collects (input), transforms (processing), stores, and disseminates (output) timely and accurate information to support decision-making, coordination, control, and strategic competitive advantage in an organization.

Two Importances of Information Systems to Society

1. Democratization of Knowledge and Education: Information systems enable global e-learning platforms, open educational repositories, and remote learning access, allowing students and professionals from remote or underserved regions to access high-quality education and training.
2. Enhanced Healthcare Delivery and Public Health Management: Healthcare information systems (electronic health records, telemedicine, diagnostic AI) enable remote medical consultations, faster epidemiological disease tracking, and improved patient care outcomes.

Two Types of Computer-Based Information Systems (CBIS) and Their Importance

Computer-Based Information Systems (CBIS) utilize computer hardware, software, telecommunications, and databases to process and distribute information across different management levels:

Key Computer-Based Information Systems

---

1. Transaction Processing System (TPS)

• Description: Operates at the operational level of an organization, capturing and processing the routine, daily, high-volume transactions essential to conduct business (e.g., point-of-sale checkouts, ATM banking, inventory receipts).
• Importance:
  • Serves as the primary operational backbone of the business; if TPS fails, business operations halt immediately.
  • Captures and validates clean raw data that feeds into all higher-level executive systems (MIS, DSS, ESS).

---

2. Management Information System (MIS)

• Description: Operates at the middle-management level, summarizing and synthesizing operational TPS data into structured, periodic, scheduled reports and exception reports (e.g., weekly sales comparisons, monthly cost variances).
• Importance:
  • Helps managers track ongoing departmental performance against planned budgets and strategic goals.
  • Highlights operational anomalies (via exception reporting) so managers can take timely corrective action.

Why Organizations Need Different Types of Information Systems

No single, monolithic information system can satisfy all the diverse operational, analytical, and strategic needs of an enterprise. Organizations are structured into hierarchical management levels and specialized functional areas, each requiring distinct information characteristics:

Management Level            Information System Type          Decision Nature & Scope
========================================================================================
Strategic Level     -->     Executive Support System (ESS)    Unstructured, Long-Term
                                       |
Management Level    -->     Decision Support System (DSS)     Semi-Structured, Tactical
                            Management Info System (MIS)
                                       |
Operational Level   -->     Transaction Processing System     Structured, Day-to-Day
                            (TPS) & Functional Systems

---

1. Diverse Decision-Making Characteristics across Levels:

• Operational Level (Structured Decisions):
  • Focus: Routine, daily, repetitive tasks (e.g., processing sales receipts, tracking daily shipments).
  • System Needed: Transaction Processing Systems (TPS). Requires high transaction throughput, high accuracy, and low latency.
• Tactical / Middle Management Level (Semi-Structured Decisions):
  • Focus: Departmental planning, performance monitoring, budgeting, and resource allocation.
  • System Needed: Management Information Systems (MIS) and Decision Support Systems (DSS). Requires summary reports, historical trend tracking, and scenario simulation capabilities.
• Strategic / Executive Level (Unstructured Decisions):
  • Focus: Long-range corporate vision, mergers, entering foreign markets, and competitive responses.
  • System Needed: Executive Support Systems (ESS). Requires high-level visual dashboards integrating internal KPI data with external market, regulatory, and competitor intelligence.

---

2. Functional Specialization Requirements:

• Different functional areas require specialized logic:
  • Marketing requires customer profiling and lead conversion funnels.
  • Finance requires double-entry accounting ledgers and tax compliance tracking.
  • Manufacturing requires material requirements planning (MRP) and machine scheduling.

---

3. Different Time Horizons and Data Granularity:

• Operational frontline staff need real-time, granular, individual record details.
• Senior executives need aggregated, multi-year, summarized visual charts to make strategic corporate bets.

Organizations deploy an interconnected portfolio of systems (TPS, MIS, DSS, ESS, and ERP) to align seamlessly across all decision tiers.

Desirable Characteristics of a Transaction Processing System (TPS)

1. High Processing Speed and Low Latency: A TPS must handle large volumes of transactions simultaneously with rapid response times.
2. Absolute Reliability and Fault Tolerance: Must maintain 24/7/365 uptime with robust backup and failover mechanisms.
3. Strict ACID Compliance: Ensures all transactions strictly follow Atomicity, Consistency, Isolation, and Durability to prevent data corruption or partial commits.