Gathering and analyzing customer requirements is a critical step in designing the right IT solution. It helps ensure that the proposed infrastructure aligns with both business objectives and technical needs.
Understanding the business side of the project is crucial because IT solutions must ultimately serve the customer’s business goals.
Workflows:
Study the daily operations and processes. What applications or systems do employees use? Which parts of the operation are bottlenecks or areas for improvement?
Example: A retail company might need smoother communication between its online store and warehouse systems.
Key Performance Indicators (KPIs):
KPIs are metrics that track the business's success. Examples include response times, sales growth, or customer satisfaction.
Example: A KPI for a retailer might be "order fulfillment within 24 hours."
Growth Expectations:
Understand the company’s future goals. Are they expecting rapid expansion, or will their needs remain stable for a few years?
Example: A startup might plan to expand its customer base by 200% in the next year, meaning they need scalable infrastructure.
After identifying business needs, the next step is to understand the technical environment. This involves analyzing the existing system’s performance and finding areas for improvement.
Example:
If the company’s website loads slowly due to high traffic, they may need higher IOPS or more bandwidth to improve performance.
HPE offers tools that simplify infrastructure evaluation by providing insights into system performance and potential bottlenecks.
HPE InfoSight:
HPE OneView:
Let’s say a company complains about slow database performance during peak hours. Before recommending an upgrade, you could:
Based on the findings:
Mastering this step ensures that the solution you design is aligned with the customer’s short-term needs and long-term growth goals. It also makes your recommendations data-driven and reliable, increasing the chance of project success. With practice, you’ll become more confident in collecting and analyzing these requirements.
A successful HPE solution design depends on a comprehensive understanding of the customer's business and technical needs. This section expands on four critical areas: advanced business requirements gathering methods, deeper technical analysis, logical HPE solution recommendations, and data-driven decision-making.
While business goals, KPIs, and growth plans are essential, additional techniques can improve accuracy when gathering customer needs.
Engaging with key personnel through one-on-one interviews helps in understanding strategic IT challenges and business pain points.
Example Question:
"What are the top three IT-related challenges slowing down your company’s digital transformation?"
Online questionnaires can gather insights from end-users and IT staff about current infrastructure problems and desired improvements.
Example Use Case:
"If multiple employees report that file sharing is slow, it might indicate a network bandwidth issue or an inefficient storage solution."
Sometimes, directly observing a company’s IT operations can uncover hidden inefficiencies.
Example:
"By monitoring the network traffic of a global retailer, we found that their e-commerce platform slowed down every Friday night, indicating a need for load balancing and cloud bursting capabilities."
Comparing the customer’s IT environment to industry best practices can help identify areas for improvement.
Example:
"A manufacturing company wants to improve its supply chain efficiency. By benchmarking against competitors using HPE Aruba SD-WAN, we can propose a similar cloud-based networking strategy."
Beyond IOPS, latency, and bandwidth, more detailed technical assessments help identify the right solution.
Example:
"A financial firm experiencing slow data processing may need to upgrade to HPE ProLiant Gen10+ servers with higher RAM capacity and accelerated storage caching."
Example:
"A video production company with 50TB of new footage generated per month needs an HPE Alletra solution with intelligent storage tiering to optimize performance and cost."
Example:
*"A law firm dealing with confidential client data may require Aruba ClearPass Policy Manager to enforce role-based access control (RBAC)."*
Example:
"An e-commerce site preparing for Black Friday may need a hybrid cloud solution that temporarily scales to the public cloud while keeping sensitive customer data on-premises with HPE Nimble Storage."
Once customer pain points are clear, HPE solutions should be matched to business needs.
| Customer Need | Recommended HPE Solution |
|---|---|
| High storage performance | HPE Nimble Storage (intelligent caching) |
| Predictive analytics & automation | HPE InfoSight |
| Simplified IT operations | HPE OneView |
| High-performance computing (HPC, AI/ML) | HPE Apollo |
| Hybrid cloud deployment | HPE GreenLake |
| Cost-effective IT for SMBs | HPE SimpliVity (HCI) |
Example:
"If an organization is struggling with IT complexity, we can recommend HPE OneView to centralize management and automate updates, reducing IT overhead."
HPE InfoSight enables AI-driven infrastructure monitoring, which can guide proactive decision-making.
By analyzing historical performance trends, businesses can make data-backed IT investment decisions.
HPE InfoSight can predict failures before they happen, reducing downtime.
Example:
"If InfoSight predicts a RAID controller failure within 30 days, the IT team can schedule a proactive replacement, avoiding unexpected downtime."
By incorporating advanced business requirement gathering, deeper technical analysis, a structured solution recommendation approach, and AI-driven insights, HPE solutions can be tailored to customer needs with greater precision.
What is the most important first step when gathering requirements for an HPE SMB solution?
Understanding the customer’s business objectives and workloads.
Before selecting hardware or designing architecture, engineers must determine what the customer is trying to achieve. This includes identifying key applications, expected user workloads, data growth patterns, and performance expectations. Understanding the business context ensures that the solution aligns with operational goals rather than focusing only on technical specifications. For example, a company prioritizing uptime may require high-availability design, while another focused on cost efficiency may prioritize consolidation. Gathering this information early prevents oversizing or undersizing the infrastructure and improves the overall effectiveness of the solution design.
Demand Score: 85
Exam Relevance Score: 91
Why should engineers analyze existing infrastructure before proposing a new HPE solution?
To determine compatibility, upgrade paths, and integration requirements.
Many organizations already have servers, storage, or networking equipment deployed in their environment. Analyzing the current infrastructure helps architects determine whether the new solution should integrate with existing systems or replace them. It also helps identify potential compatibility issues, such as unsupported operating systems or outdated hardware. Evaluating existing infrastructure ensures smoother migration and reduces deployment risks. This assessment typically includes reviewing server specifications, network topology, storage capacity, and virtualization platforms.
Demand Score: 82
Exam Relevance Score: 88
Why is capacity planning important during requirement analysis?
Because it ensures the solution can handle current workloads and future growth.
Capacity planning involves estimating how much compute, storage, and network resources are required for both current operations and projected expansion. Without proper capacity planning, infrastructure may quickly become insufficient as workloads increase. Engineers typically analyze factors such as data growth rate, number of users, transaction volume, and expected workload spikes. Designing a system with adequate capacity helps prevent performance bottlenecks and reduces the need for frequent hardware upgrades.
Demand Score: 79
Exam Relevance Score: 87
What type of requirement determines the need for redundancy and high availability in a solution?
Business continuity and service availability requirements.
Organizations that rely on critical applications often require infrastructure capable of operating even during hardware failures. During requirement analysis, engineers should determine acceptable downtime limits and recovery objectives. These requirements influence architecture decisions such as redundant power supplies, RAID storage, clustered servers, and backup systems. Identifying business continuity requirements early ensures that the solution provides the necessary level of reliability and minimizes operational risk.
Demand Score: 77
Exam Relevance Score: 90