Main Menu
Home
News
Contact Us
Search
Company
Newsletter
Services
Workshops
BMO
Repositories
EAS
Browsers
Web Services
Shop
Best Practices


Using the EAS for an Internal Evaluation PDF Print E-mail

The Evaluator's Application Suite (EAS) has been designed to support the evaluation process, regardless of whether software vendors are involved or not. Thus, you can also use the EAS in the context of an internal evaluation.

Now, the question is: How is an internal evaluation different?

In terms of the evaluation process, there is no conceptual difference. You start out with creating an Evaluation Specification. Next, a Private RFP is generated, and then a Public RFP.

You would distribute the Public RFP among your internal evaluation teams. Ideally, each evaluation team would be tasked with the evaluation of one software product. However, this is not a strict requirement. An evaluation team could also be requested to evaluate more than one software product.

Using the RFP Response Editor, an evaluation team creates an RFP Response for each evaluated software product and assigns requirement fulfillment statements as the product is evaluated.

When all evaluation teams are finished, RFP Responses can be imported into an Evaluation Project, using the Evaluation Project Editor.

So, the only difference lies in the fact that RFP Responses are created by internal evaluation teams and not by software vendors.

Is this adequate? Yes, it is. Technically speaking, the purpose of an RFP Response is to provide requirement fulfillment statements for requirements. There is a 1:1 relationship between requirement and requirement fulfillment statement. The only question then is who provides requirement fulfillment statements.

For the sake of completeness, it should be mentioned that you can import vendor-prepared RFP Responses and self-prepared RFP Responses into an Evaluation Project. Thus, you can cater for a situation when there is no software vendor in the classical sense. For example, there are high-profile open source products, but open source projects do not have marketing and sales staff, at least not comparable to a typical software vendor. As a result, nobody has the time to prepare an RFP Response. You would either need to do an internal evaluation or delegate the task to a consulting firm. 

Whoever prepares an RFP Response, be it a software vendor, a consulting firm or an internal evaluation team: The EAS gives you ultimate flexibility.

 
< Prev   Next >
   Home arrow Best Practices arrow Software Evaluation arrow Using the EAS for an Internal Evaluation