Unit 6.3: Functional Area Information Systems (FAIS) and Information Silos

--:-- --
↓ Scroll for more

Unit 6.3

Functional Area Information Systems (FAIS) and Information Silos

IT 233: Business Information Systems

Learning Objectives

By the end of this session, you will be able to:

  • ✅ Define Functional Area Information Systems (FAIS).
  • ✅ Explain the problem of information silos and why they are detrimental.
  • ✅ Provide examples of common FAIS for key business departments.

What is an FAIS?

Functional Area Information Systems (FAIS) are systems designed to support the specific needs of a single department or functional area within an organization.

Think of them as specialized tools for a specific team. 🎯

  • Each department (Accounting, Marketing, HR) has its own processes and data.
  • FAIS are tailored to meet those unique needs.
  • They evolved from early days when departments bought or built their own software independently.

Interactive: Sort the Systems!

Click a system card, then click the correct department to match it.

Score: 0 / 5
FAIS Department Dashboards
Silo Bridges

The Core Problem: Information Silos ⚡

While FAIS are great for individual departments, they create a massive organizational problem.

Information Silo: A situation where data is isolated in separate, often incompatible, information systems, preventing easy communication and sharing across the organization.

Essentially, each department has its own island of data, with no bridges connecting them.

Visualizing the Silo

Imagine trying to get a complete view of one customer...

📊 Marketing

Has a database of potential customers and campaign responses.

System: CRM

🛒 Sales

Has a database of actual customers and their purchase history.

System: Sales Tracker

💰 Accounting

Has a database of customer payment information and credit history.

System: Billing System

Without integration, how can you know if a marketing lead made a purchase and paid on time? It's incredibly difficult.

Interactive: The Silo Effect Simulator

Select a Customer ID and query each department's isolated system to see how fragmented the data is.

Marketing CRM

Not queried yet.

Sales Tracker

Not queried yet.

Billing System

Not queried yet.

🎬 Watch: What Data Silos Are

Fragmented View of Silos

Consequences of Information Silos

  • No Single Source of Truth: Different departments have conflicting or outdated data about the same thing (e.g., a customer's address).
  • Inefficiency and Waste: Employees waste time manually re-entering data from one system into another.
  • Poor Decision Making: Leaders cannot get a holistic, real-time view of the business to make strategic decisions.
  • Poor Customer Experience: A support agent can't see a customer's sales history or billing status, leading to frustration.

This fundamental problem was the primary motivation for developing integrated Enterprise Resource Planning (ERP) systems.

Interactive: Identify the Silo Consequence

Read the scenario and click the consequence it best demonstrates.

🏛️ Real Case: When Silos Have a Human Cost

The US 9/11 Commission Report (July 2004) examined why warning signs before the 2001 attacks were missed.

  • Different agencies each held pieces of the picture in their own systems.
  • Rules and culture said share only on a "need to know" basis, so the pieces were rarely joined up.
  • The Commission recommended moving to "need to share": information flowing across organisational walls.
Lesson: a silo isn't just a technology problem. Structure, incentives and culture keep data apart too.

The 9/11 Commission Report

Cover of The 9/11 Commission Report.

🎬 Watch: 9/11 and Shared Intelligence

🌉 Breaking Silos: Four Solutions

1. Shared database / ERP
Replace separate systems with one integrated system (Unit 6.4).
2. Integration middleware / APIs
Keep each FAIS, but let them exchange data automatically.
3. Data warehouse
Copy data from every FAIS into one place for reporting and analysis.
4. Process ownership
Give one manager responsibility for a cross-department process, e.g. order to delivery.

Options 1–3 are technical; option 4 is organisational. Most firms need a mix.

🎬 Watch: Middleware Explained

🧪 Quick Activity: Which Silo Solution?

Pick the best of the four solutions for each situation.

  1. A bank wants to keep its loan system and its card system, but needs them to update each other automatically. → Middleware / APIs
  2. A hotel chain's CEO wants a monthly report combining bookings, staffing and costs from every branch. → Data warehouse
  3. A manufacturer's ten old departmental systems are all out of support next year. → Shared database / ERP
  4. Orders are delayed because Sales and Delivery each blame the other. → Process ownership

Examples of FAIS by Department

Let's look at some common systems you'd find in a typical organization.

Accounting & Finance FAIS

  • Financial Planning Systems: For forecasting revenue, expenses, and creating budgets.
  • Accounts Payable/Receivable: Manages payments to suppliers and money owed by customers.
  • General Ledger (GL): The central repository for all accounting data. The "book of record" for the company.
Routine vs Ad-hoc Reports
Accounting

Marketing & Operations FAIS

🎯 Marketing

  • CRM Systems: Manage customer relationships from lead to support. (Note: Modern CRMs are often cross-functional).
  • Campaign Management: Plan, execute, and measure marketing campaigns.
FAIS Wheel

🏭 Operations

  • Inventory Management: Track raw materials, work-in-progress, and finished goods.
  • Quality Control Systems: Monitor and identify product defects.

Human Resources FAIS

Human Resources Information System (HRIS)

An HRIS is the core FAIS for the HR department, often managing the entire employee lifecycle. It can include modules for:

  • Recruiting & Applicant Tracking (ATS): Manages job postings and candidate applications.
  • Payroll & Benefits Administration: Processes salaries, taxes, and employee benefits.
  • Performance Management: Tracks employee goals and annual reviews.

💸 Real Case: An HR System Go-Live Gone Wrong

In March 2010, Queensland Health (Australia) switched on a new payroll system for its staff.

  • Thousands of nurses and doctors were underpaid, overpaid or not paid in the following pay cycles.
  • The system had to handle very complex award rules and rosters that were not fully tested before launch.
  • A 2013 Commission of Inquiry called it one of the worst public-sector IT failures in Australia.
An HRIS touches every employee's pay. Its data and rules must match how the organisation really works.

Interactive: FAIS Department Explorer

Click a department to reveal its key FAIS tools and what they do.

Select a department above to explore its FAIS.

🔍 Practical Application: A Nepali Context

Scenario: "Himalayan Goods," a large retail chain in Nepal

The marketing team runs a massive Dashain festival campaign using their Campaign Management System.

  • The Sales System in each store records a huge spike in sales, but can't link it directly to the marketing campaign. Which ads worked best?
  • The Inventory System shows the Pokhara branch is out of stock on a popular item, but the marketing team is still running local ads for it.
  • The Accounting System can't easily calculate the campaign's Return on Investment (ROI) because sales and marketing cost data are separate.

The Result: Wasted ad spend, lost sales, and poor data for future planning, all due to information silos.

Interactive: Silo Cost Calculator

Estimate the annual cost of manual data re-entry caused by information silos in your organisation. (Savings % shown is an approx. industry estimate.)

Total annual hours wasted: —
Estimated annual cost: —

🧮 Worked Example: One Customer Complaint

Illustrative: A customer calls a Nepali electronics retailer: "I paid for a TV, but it hasn't arrived."

❌ In silos
  1. Service agent sees the order, but not the payment.
  2. Calls Accounts: "Payment received yesterday."
  3. Calls Warehouse: "No dispatch request yet."
  4. Customer is put on hold three times and promised a call back.
✅ Integrated
  1. Agent sees order, payment and stock on one screen.
  2. Spots that dispatch was never triggered.
  3. Triggers it and gives a delivery date during the call.

Decision-making suffers the same way: managers can't see which step is the bottleneck.

💬 Discuss: Silos at Your College

  • Name two offices at your college (e.g. admissions, exams, accounts, library) that keep separate records about you.
  • What goes wrong for students because they don't share data?
  • Which of the four solutions would you try first, and why?

Key Takeaways

  • FAIS are powerful tools designed for a single business department.
  • Their independent nature creates information silos, isolating data and preventing communication between departments.
  • Silos lead to inefficiency, poor decision-making, and a fragmented view of the business.
  • The limitations of FAIS and the problems of silos drove the development of integrated ERP systems.

Exam Practice 📝

Short answer

  1. What is a functional area information system (FAIS)?
  2. What are information silos?
  3. Give one example of an information system for each of accounting, marketing, and HR.

Exam Practice 📝 (continued)

Long answer

  1. Explain functional area information systems with examples, and discuss the problem of information silos.
  2. How do information silos affect customer service and decision making? Suggest solutions.

Revise the answers in the full note.

Image & Video Credits

Images

  • The 9/11 Commission Report cover: National Commission on Terrorist Attacks Upon the United States, public domain (US Government work), via Wikimedia Commons
  • Point-to-point vs hub diagram: course author (original), CC BY 4.0

Videos (YouTube)

  • Contentsquare, "What are data silos? And how to eliminate them for good" (26–101 s)
  • Voice of America, "9/11 Forced Change in US Intelligence" (2011; 53–112 s)
  • Connected Cookie, "Middleware Explained in 2 minutes" (16–94 s)

Thank You & Questions


Next Topic:

Unit 6.4: Enterprise Resource Planning (ERP) Systems

📖 Read the full note