IT231 IT And Applications

IT And ApplicationsUnit 1012 min read

TPS & MIS: Systems, Data Flow, and Business Intelligence

Unit 10 of IT And Applications explores Transaction Processing Systems (TPS) and Management Information Systems (MIS), covering their definitions, architectures, real-world applications, and how they transform raw data into actionable business insights. Learn how TPS handles routine transactions (e.g., bank deposits) a


Core Concepts: Definitions and Scope

Transaction Processing Systems (TPS)

A Transaction Processing System (TPS) is a computerized system that records, processes, and stores routine business transactions in real-time. These transactions are repetitive, high-volume, and critical for day-to-day operations.

Key Characteristics of TPS

Records routine transactions (e.g., sales, payments, inventoTransaction-OrientedHandles thousands of transactions per second (e.g., Ncell biHigh VolumeUpdates data immediately (e.g., eSewa payment confirmation)Real-Time ProcessingBatch: Processes transactions in groups (e.g., monthly salarOnline: Processes transactions instantly (e.g., Daraz order Batch vs. Online ProcessingEnsures accuracy, consistency, and security (e.g., bank ATM Data IntegrityMinimizes human intervention (e.g., NTC’s automated fare colAutomatedTPS Characteristics
Hierarchical breakdown of TPS characteristics with Nepali examples

Management Information Systems (MIS)

An MIS is a system that collects, processes, stores, and disseminates information to support managerial decision-making. Unlike TPS, MIS focuses on aggregating and analyzing data to provide insights rather than handling transactions.

Key Characteristics of MIS

Helps managers make informed decisions (e.g., NEPSE stock anDecision SupportCombines data from multiple sources (e.g., sales reports froData AggregationGenerates periodic reports (e.g., monthly profit/loss statemReportingPredicts outcomes (e.g., Pathao’s demand forecasting)Modeling and SimulationDashboards for executives (e.g., Khalti’s transaction analytUser-Friendly InterfacesLinks with TPS, ERP, and other systems (e.g., bank loan apprIntegrationMIS Characteristics
Hierarchical breakdown of MIS characteristics with Nepali business examples

In the Real World

TPS and MIS are everywhere in Nepal’s digital economy. Here’s how they power daily life:

Company/App System Type How It Uses the Concept Example Transaction/Data Flow
eSewa TPS Processes real-time payments (e.g., bill payments, remittances) with data integrity. User → eSewa Server → Bank → Confirmation (all in <5 seconds).
Ncell TPS + MIS TPS: Handles call logs, top-ups, and billing. MIS: Analyzes usage patterns for promotions. Customer tops up → TPS updates balance → MIS generates "high-usage customers" report for offers.
Daraz TPS TPS: Manages orders, inventory, and shipments in real-time. Order placed → Inventory deducted → Shipping label generated → TPS updates seller dashboard.
NTC (Nepal Telecom) TPS TPS: Processes bus/train tickets and fares automatically. Passenger scans QR → TPS validates ticket → Gate opens (no manual checks).
NEPSE (Stock Exchange) MIS MIS: Aggregates stock data to generate trading signals and market trends. Broker inputs trade → MIS analyzes volume → Alerts trader: "Buy NABIL at ₹450 (5% gain predicted)."

Worked Example: Ncell’s Billing System (TPS)

  1. Transaction Input: A customer uses 2GB data in a month.
  2. TPS Processing:
    • System checks plan (e.g., ₹999 for 10GB).
    • Deducts 2GB from allowance.
    • Updates database in real-time.
  3. Output: Customer receives an SMS: "Your data balance: 8GB. Next bill: ₹999 on 15th June."
  4. MIS Integration: At month-end, MIS generates a report:
    • "Top 10 data-heavy users in Kathmandu: [List]" → Used for targeted promotions.

Architecture and Data Flow

TPS Architecture

TPS follows a layered architecture to ensure efficiency and accuracy:

flowchart TD
  A["User Input\n(e.g., eSewa payment)"] --> B["Input Module\n(Validation & Authentication)"]
  B --> C["Processing Module\n(Transaction Logic)"]
  C --> D["Database\n(Updates records)"]
  D --> E["Output Module\n(Receipts, SMS, Reports)"]
  E --> F["Audit Trail\n(Logs for security)"]

Key Components

  1. Input Module: Validates transactions (e.g., checks if a Daraz order has stock).
  2. Processing Module: Executes the transaction (e.g., deducts inventory).
  3. Database: Stores transaction records (e.g., Ncell’s customer usage logs).
  4. Output Module: Generates confirmations (e.g., eSewa payment receipt).
  5. Audit Trail: Logs all transactions for security (e.g., bank ATM logs).

MIS Architecture

MIS builds on TPS data but focuses on analysis and reporting:

flowchart TD
    A["Raw Data
(From TPS/ERP)"] --> B["Data Warehouse
(Centralized storage)"]
    B --> C["ETL Process
(Extract, Transform, Load)"]
    C --> D["Data Mining
(Pattern detection)"]
    D --> E["Reporting Tools
(Dashboards, BI tools)"]
    E --> F["Decision Support
(Executive reports)"]
    F --> G["Feedback Loop
(Refines data collection)"]

Key Components

  1. Data Warehouse: Stores historical data (e.g., Khalti’s 5-year transaction history).
  2. ETL (Extract, Transform, Load): Cleans and structures data (e.g., converting raw sales data into charts).
  3. Data Mining: Finds patterns (e.g., "Customers who buy X also buy Y" for Daraz).
  4. Reporting Tools: Dashboards for executives (e.g., NEPSE’s stock performance trends).

TPS vs. MIS: A Comparison

Feature Transaction Processing System (TPS) Management Information System (MIS)
Primary Function Processes routine transactions (e.g., sales, payments). Supports decision-making (e.g., forecasts, reports).
Data Focus Operational data (real-time, detailed). Aggregated data (summarized, historical).
Users Clerks, operators (e.g., bank tellers, Daraz delivery agents). Managers, executives (e.g., Ncell’s marketing team).
Processing Speed High-speed, real-time (e.g., NTC ticket validation). Batch or periodic (e.g., monthly sales reports).
Output Receipts, confirmations, logs (e.g., eSewa payment proof). Reports, dashboards, alerts (e.g., "Low inventory alert").
Example in Nepal eSewa, Ncell billing, Daraz order processing. Khalti’s fraud detection, NEPSE’s stock analysis.
Dependency Independent but feeds data to MIS. Relies on TPS data for insights.
023.7547.571.2595Transaction Volume95Processing Speed80Data Scope40User Focus60Output Type75
[object Object]

Advantages and Disadvantages

TPS Advantages

✅ Efficiency: Automates repetitive tasks (e.g., NTC’s fare collection). ✅ Accuracy: Reduces human errors (e.g., bank ATM transactions). ✅ Speed: Processes transactions in milliseconds (e.g., Pathao ride booking). ✅ Scalability: Handles high volumes (e.g., Daraz’s Black Friday sales). ✅ Audit Trail: Maintains records for compliance (e.g., tax filings).

TPS Disadvantages

❌ High Initial Cost: Expensive to implement (e.g., ERP systems for banks). ❌ Rigid Structure: Difficult to modify for new transaction types. ❌ Data Overload: Can slow down if not optimized (e.g., Ncell’s network during peak hours).

MIS Advantages

✅ Decision Support: Helps managers make data-driven choices (e.g., NEPSE’s stock tips). ✅ Strategic Insights: Identifies trends (e.g., "Demand for smartphones rises in winter"). ✅ Integration: Works with TPS, ERP, and other systems. ✅ Customizable Reports: Tailored for different stakeholders (e.g., CEO vs. sales team).

MIS Disadvantages

❌ Complexity: Requires skilled analysts to interpret data. ❌ Data Quality Depends on TPS: Garbage in → garbage out (e.g., wrong sales data → bad forecasts). ❌ Costly Tools: Advanced BI software (e.g., Tableau) can be expensive.


Worked Example: Kathmandu Traffic Management (TPS + MIS)

Scenario: The Kathmandu Metropolitan City (KMC) wants to reduce traffic congestion using IT.

Step 1: TPS for Real-Time Traffic Monitoring

  • Input: Sensors on roads detect vehicle count/speed (e.g., at Thapathali junction).
  • Processing:
    • TPS records data every 5 minutes (e.g., "120 cars/minute at 8 AM").
    • Triggers alerts if congestion exceeds a threshold (e.g., >150 cars/minute).
  • Output:
    • Displays real-time traffic on KMC’s website/app.
    • Sends SMS to commuters: "Heavy traffic on Ring Road. Take alternative route."

Step 2: MIS for Long-Term Planning

  • Data Aggregation: MIS collects 6 months of traffic data.
  • Analysis:
    • Identifies peak congestion times (e.g., "7–9 AM on weekdays").
    • Predicts future trends (e.g., "Traffic will increase by 20% during Dashain").
  • Output:
    • Report for city planners: "Add a flyover at Thapathali to reduce delays by 30%."
    • Public dashboard showing historical trends (e.g., "Traffic reduced by 15% after new signals").

Exam Tip

2078 BSTPS introduced inNcell billing system2080 BSMIS adopted byNEPSE for stock analys2081 BSIntegration ofTPS/MIS in Kathmandu t
Timeline of TPS/MIS adoption in major Nepali systems

How to Score Full Marks in TU/PU Exams

  1. Define Clearly:

    • Start with precise definitions (e.g., "TPS is a system that records and processes routine transactions in real-time").
    • Avoid: Vague answers like "TPS is used for transactions."
  2. Use Diagrams:

    • Draw data flow diagrams for TPS/MIS (even if not perfect, partial credit is given).
    • Label all components (e.g., "Input Module → Processing → Database").
  3. Compare TPS vs. MIS:

    • Exams often ask for differences. Use a table (as above) to highlight 3–4 key points.
    • Example Answer:

      "Unlike TPS, which processes individual transactions like eSewa payments, MIS aggregates data to generate reports like Khalti’s monthly transaction summaries."

  4. Real-World Examples:

    • Nepal-specific examples score higher. Mention:
      • TPS: eSewa, Ncell, Daraz, NTC.
      • MIS: NEPSE, bank loan approvals, Pathao’s demand forecasting.
    • Avoid: Generic examples like "Amazon" without explaining how they use TPS/MIS.
  5. Advantages/Disadvantages:

    • List 3 pros and 2 cons for each system. Use bullet points for clarity.
    • Example:

      "An advantage of TPS is its speed (e.g., NTC ticket validation), but a disadvantage is the high cost of implementation."

  6. Common Pitfalls:

    • ❌ Confusing TPS with ERP: TPS is for transactions; ERP integrates multiple systems (e.g., SAP).
    • ❌ Ignoring Audit Trails: Always mention that TPS maintains logs for security.
    • ❌ Overcomplicating MIS: Focus on reports and dashboards, not coding.
  7. Short-Answer Tips:

    • For "List one difference between TPS and MIS":

      "TPS processes real-time transactions (e.g., eSewa payments), while MIS analyzes aggregated data for decision-making (e.g., NEPSE stock trends)."


Final Reminder: Always link theory to Nepal’s context. Examiners love answers that show how TPS/MIS are used in eSewa, Ncell, or Daraz—not just generic examples!

Based on the TU BBA syllabus for IT And Applications (IT231), unit 10.

Discussion

Loading…