Como elegir al proveedor de ERP - Webinar

Evaluating and Selecting Enterprise Software

Importance of a Structured Evaluation Process

• A structured and planned process is essential for evaluating and selecting enterprise software, ensuring efficiency and cost-effectiveness.

• The evaluation of software vendors is crucial; their reputation, experience, and references provide guarantees for project execution.

Initial Steps in Software Evaluation

• One of the first steps is to identify the type of software needed for the company by answering key questions about its requirements.

• The evaluation process typically spans 3 to 6 months, followed by implementation and team training.

Potential Risks with Software Vendors

• Scenario one: If a software vendor goes bankrupt, the project halts with no updates or additional modules delivered.

• Scenario two: If a vendor is acquired, support may cease after a set period, necessitating a new selection process.

Recommendations for Vendor Evaluation

• To mitigate risks, take time to assess each vendor's financial stability and strategic alignment as part of the evaluation process.

• Tools like product evaluators can assist in assessing functionality alongside financial viability.

Financial Viability Assessment

• Evaluate vendors based on their financial health—considering income stability, profitability margins (ideally above 10%), and working capital adequacy.

• Classify vendors as viable or at risk based on their financial capacity but avoid solely relying on this metric.

Strategic Viability Assessment

• Assess three key factors: continuous investment in product development, industry focus of the vendor’s offerings, and potential consolidation scenarios within the market.

• Understanding a vendor's roadmap helps gauge future product direction and commitment to ongoing development.

Resources for Software Evaluation

• Utilize objective tools like software evaluators that compare needs against standardized offerings from various vendors.

• Approximately 350 products are included in these evaluations to ensure comprehensive comparisons based on functional responses.

Evaluation and Selection of Software Solutions

Understanding Product Behavior and Project Needs

• The evaluation process begins with understanding product behavior in various situations, aligning it with project needs submitted through a pre-established form. This is facilitated by a search engine that identifies products meeting those needs.

Resources for Evaluation

• A library of non-commercial articles is available, free from advertising influences, providing unbiased insights into industry practices. Additionally, white papers and downloadable PDFs are accessible to aid the evaluation process.

• Special reports and implementation case studies can be found in the library section on the website, offering practical examples for better decision-making. Users can also access a directory of registered suppliers whose products have been validated by Evaluando RP.

Importance of Supplier Evaluation

• Selecting an enterprise software provider is crucial; it requires thorough evaluation to minimize subjective biases and ensure objectivity in supplier assessment. Key factors include representativeness, implementation history, financial stability, maintenance policies, service level agreements (SLAs), execution capacity, industry knowledge, and human resource expertise assigned to projects.

Four Axes of Evaluation

• The overall evaluation process consists of four main axes: functional evaluation (closing gaps between current and desired states), technological validation (ensuring future-proof technology), supplier assessment (ensuring project execution capability), and economic evaluation (securing necessary financial resources). Each axis involves specific stakeholders such as business areas for functional evaluations and finance management for economic assessments.

Functional Evaluation

• Functional evaluations aim to bridge gaps between current capabilities and desired outcomes using templates that guide the assessment process involving multiple business areas beyond just technology departments.

Technological Validation

• The technological evaluation focuses on validating whether the chosen technology aligns with future trends or has adequate support within the industry; this typically involves technical experts utilizing structured templates for assessment.

Supplier Assessment

• Evaluating suppliers ensures they can execute projects effectively; this often includes input from company leadership who make critical decisions regarding project direction while employing multi-level templates to reduce subjectivity in assessments.

Economic Evaluation

• Economic evaluations confirm that sufficient financial resources are available for project implementation; this involves collaboration between management teams responsible for budget oversight using comparison templates or projected cash flow analyses to assess viability before proceeding with implementations.

Evaluation Methodology in Project Assessment

Overview of Evaluation Criteria

• The evaluation of a project typically involves four main axes: functional, technical, provider/implementer, and economic.

• Each axis is assigned a score that collectively sums to 100 points or 100%. The importance of each axis must be defined based on the project's needs.

• For example, in Project A, the functional evaluation is prioritized at 40 points, while in Project B, the economic aspect takes precedence with 45 points.

Importance of Functional vs Economic Evaluation

• In Project A, the focus is on having a strong functional product to support business processes and strategic decisions over cost considerations.

• Conversely, Project B emphasizes budget constraints and may compromise on functionality for economic feasibility. This highlights differing priorities between projects.

Evaluating Providers

Key Aspects to Consider

• When evaluating providers, several factors are crucial:

• Sales figures within the country can indicate experience with ERP software implementation.

• Global sales provide insight into product significance and market presence.

• Other important aspects include:

• Client base size ensures ongoing market support for products.

• Adequate personnel availability for implementation and support services.

Training and Support Services

• Assessing training plans is vital for ensuring staff excellence; this includes checking if comprehensive user training programs exist.

• Availability of help desks during non-business hours is essential for addressing urgent issues during critical project phases like production or migration.

Structuring Evaluation Grids

Importance Assignment in Grids

• Utilizing grids or matrices helps objectify evaluations across four axes: functional, technical, provider implementer, and economic.

• In an example grid:

• Functional evaluation holds significant weight (40 points), followed by economic (35), technical (15), and provider (10).

Detailed Breakdown of Provider Evaluation

• The provider's evaluation can be further divided into subcategories such as market presence and local structure which are deemed more critical than experience or credentials.

• This structured approach allows for nuanced assessments that reflect specific project requirements effectively.

Market Presence Evaluation Framework

Breakdown of Market Presence Criteria

• The market presence is evaluated based on three key components: years in the local market (2 points), size of clients (0.5 points), and number of employees (0.5 points) .

• The evaluation grid prioritizes criteria from highest to lowest, transitioning from Level 1 to Level 2 (orange grid) and then to Level 3 (green grid) .

• Scoring tables will indicate how suppliers are rated, with scores ranging from 0.5 to higher values depending on their performance across various metrics .

Supplier Evaluation Example

• An example evaluation shows Supplier 1 scoring 8.51 points while Supplier 2 scored 6.45 points, indicating a clear preference for Supplier 1 based on their scores in different categories such as market presence and experience .

• Specific scores for each supplier include:

• Market presence: Supplier 1 - 2.65, Supplier 2 - 2.70

• Experience: Supplier 1 - 1.80, Supplier 2 - 1.60

• Local structure: Supplier 1 - 2.56, Supplier 2 - 1.15

• Credentials: Supplier 1 - 150, Supplier 2 -100 .

Detailed Insights into Market Presence Components

• The market presence component is further divided into years in the local market, client size, and employee count; these factors contribute significantly to the overall score for each supplier's evaluation .

• For experience assessment:

• Successful implementations in the local market are crucial; more implementations generally yield better scores.

• A balance is sought where too few or too many implementations may negatively impact perceived reliability and service quality .

Structure Local Assessment

• The local structure assessment includes metrics like personnel turnover rates and availability of onsite support; lower turnover rates are favored as they suggest better service quality .

• Employee counts are compared against a baseline company with maximum staff; this percentage-based approach helps evaluate other companies' staffing levels effectively .

Credential Evaluation Metrics

• Credential assessments focus on certifications and industry references; more credentials lead to higher scores for suppliers .

• Each supplier's market presence can be quantified by years active in the industry, with a maximum score of two points available based on this metric .

This structured overview provides insights into evaluating suppliers based on their market presence and related criteria while highlighting specific scoring mechanisms used within the framework discussed in the transcript.

Evaluation Methodologies for Software Selection

Criteria for Product Evaluation

• The evaluation of a product's market presence is quantified: if marketed to SMEs, it scores one point; otherwise, zero. Similarly, international market presence follows the same scoring system.

• Additional criteria include the supplier's years in business and customer base size. For instance, over 500 customers earns one point, while R&D investment responses are scored as one for affirmative and zero for non-responses.

Advantages of Grid-Based Methodology

• A grid-based methodology is nearly objective as it relies on measurable data that can yield a single quantifiable value regardless of subjective perceptions.

• This method simplifies the evaluation process through basic arithmetic operations (addition, subtraction, multiplication), making it accessible with tools like Excel.

• It establishes priorities by assigning varying points to different criteria, indicating their relative importance in the evaluation process.

Disadvantages of Grid-Based Methodology

• Competition between companies may be uneven; larger firms have more resources to showcase their offerings compared to smaller firms.

• The methodology does not emphasize quality or compliance in implementation but focuses solely on the supplier’s metrics.

• Subjectivity can creep into evaluations if measures are poorly defined or inconsistently applied.

Importance of Planning in Evaluation Process

• Effective evaluation requires thorough planning and organization before initiating software searches; constructing grids and criteria beforehand is essential.

• Objectivity should be prioritized to minimize biases stemming from personal preferences or perceptions during evaluations.

Key Considerations for Successful Implementation

• Evaluators must determine which factors hold greater significance by weighing them appropriately without imposing excessive demands on suppliers based on company size.

• Proper preparation is crucial for streamlining processes later on; inadequate preparation risks project abandonment due to complexity.

For further information or materials related to this topic, please visit academiaevaluandosoftware.com.