Welcome to the World of Systems Selection!
Hello future CPAs! Welcome to one of the most practical chapters in the Information Management curriculum. Think about the last time you bought a new smartphone. Did you just walk into a store and pick the first one you saw? Probably not! You likely checked your budget, looked at the features, read reviews, and maybe even tested a demo model.
In a business setting, picking a new information system is exactly the same, but on a much bigger (and more expensive) scale. This chapter is part of the Analyse Systems Development Process section. We are going to learn how companies move from "We need a new system" to "This is the specific software we are going to buy." It’s a critical step because picking the wrong system can cost a company millions of dollars and years of wasted time. Don't worry if this seems technical—we will break it down step-by-step!
1. The Systems Selection Process: Step-by-Step
Selecting a system isn't a single event; it's a journey. Following a formal process ensures the company remains objective and doesn't just buy what the most charismatic salesperson is offering. Here is the typical flow:
Step A: Establish Requirements
Before looking at what’s available, you must know what you need. This is often called Requirements Analysis.
• Functional Requirements: What should the system do? (e.g., "The system must generate monthly tax reports.")
• Non-functional Requirements: How should the system be? (e.g., "The system must be secure and easy to use.")
Analogy: If you're buying a car, a functional requirement is "it must seat 5 people." A non-functional requirement is "it must be fuel-efficient."
Step B: Information Gathering (RFI and RFP)
Once you know your needs, you reach out to the market using two important documents:
1. Request for Information (RFI): A polite way of saying "Tell us about your company and what your software generally does." This helps narrow down the list of potential vendors.
2. Request for Proposal (RFP): A much more serious document. You tell the vendor exactly what you need, and they send back a detailed plan of how their system meets those needs, including the price.
Step C: Evaluation and Shortlisting
Now you compare the proposals. Since you can't interview 50 vendors, you create a Shortlist of the top 3 or 5 candidates who best match your requirements and budget.
Step D: Demonstrations and Site Visits
This is the "test drive" phase. You invite vendors to show the software in action. Pro Tip: Don't let them show you a "canned" demo. Give them some of your company's real (but anonymized) data to see how the system handles your specific business problems.
Step E: Final Selection and Contract Negotiation
After the demos, you pick the winner and start the legal process of signing contracts.
Key Takeaway: The process must be structured and documented. This prevents bias and ensures the chosen system actually solves the business problem.
2. Key Issues to Consider During Selection
Choosing a system isn't just about the software features. There are several "hidden" issues that can make or break the project. Let's look at the most important ones using the mnemonic "V.A.S.T.":
V - Vendor Viability: Is the company selling the software stable? If the vendor goes bankrupt in two years, who will fix your bugs or provide updates? You should check their financial statements and reputation.
A - Adaptability (and Scalability): Can the system grow with you? If your company doubles in size, can the system handle twice as many users? Can it be customized to fit your unique business processes?
S - Support and Maintenance: What happens when things go wrong at 2:00 AM? You need to check the Service Level Agreement (SLA) to see what kind of technical support the vendor promises.
T - Total Cost of Ownership (TCO): This is a huge one for accountants! The price tag on the software is just the beginning. TCO includes:
• Initial purchase price/License fees.
• Implementation and setup costs.
• Training costs for staff.
• Ongoing maintenance and upgrade fees.
Quick Review: Which is more important—the purchase price or the TCO? Answer: The TCO! A "cheap" system that requires expensive monthly maintenance is actually very costly in the long run.
3. Evaluation Techniques: Scoring Systems
How do we decide between Vendor A and Vendor B objectively? We use Weighted Scoring. This is a mathematical way to compare different options.
1. List your criteria (e.g., Price, Ease of Use, Security).
2. Assign a Weight to each (e.g., Price might be 40%, Security might be 60%).
3. Score each vendor on a scale of 1-10 for each category.
4. Multiply the Score by the Weight and add them up!
The Formula: \( Total Score = \sum (Score \times Weight) \)
Example: If Vendor A scores 8 on Security (Weight 0.6) and 5 on Price (Weight 0.4), their total score is: \( (8 \times 0.6) + (5 \times 0.4) = 4.8 + 2.0 = 6.8 \).
4. Common Pitfalls (And How to Avoid Them)
Even smart managers make mistakes during selection. Here are a few to watch out for:
1. "The Shiny Object" Trap: Being impressed by fancy graphics or "cool" features that the company doesn't actually need. Solution: Stick to your original requirements list!
2. Ignoring the Users: Only the IT department or Top Management picks the system. If the people actually using it every day hate it, the system will fail. Solution: Include "End-Users" in the selection committee.
3. Underestimating Change Management: Choosing the software is only 20% of the work. Changing the way people work to fit the software is 80%. Solution: Plan for extensive training and communication.
5. Summary and Key Takeaways
Did you know? Research shows that a huge percentage of IT projects fail not because the technology was bad, but because the selection process was rushed or ignored the business needs!
Summary Points:
• Systems selection is a formal process involving requirements, RFPs, and demos.
• Look beyond the features—consider Vendor Viability and Support.
• Always calculate the Total Cost of Ownership (TCO), not just the sticker price.
• Use Weighted Scoring to remain objective and reduce bias.
• Keep end-users involved to ensure the system is actually usable in the real world.
Don't worry if this feels like a lot of steps. Just remember: Selection is about finding the best fit for the business, not necessarily the most expensive or advanced technology available!