Who would use the EAS?

When would I use the EAS?

Why is there no trial version?  

How is the EAS different from a simple spreadsheet-based solution?

Is the EAS an Interactive Web Application?

I do not want to perform a full-fledged evaluation. Would I need the EAS anyway?

What is the difference between a Public RFP and a Private RFP?

When would I need an EAS Service Provider License (SPL)?

When would I need an EAS Content Authoring License (CAL)?

When would I need an EAS Subject Matter Evaluation License (SMEL)?

I need to author a Request For Proposal (RFP). How can the EAS help?

Can I submit Evaluation Specifications for inclusion in the central repository?  

I am thinking about becoming a Content Provider. What would I need to do?

Do I need an always-on Internet Connection? 

Who would use the EAS?

End user organizations, consulting firms, or just any organization or individual that wants to perform a systematic evaluation of a product, service or methodology. However, for a start, EAS Release 1 supports software product evaluation. 

For example, an organization may wish to perform a product evaluation. In a streamlined scenario, it would download a pre-built Evaluation Specification, adapt it to meet the organization's particular requirements, generate an RFP (Request For Proposal), and process RFP Responses in order to create the comparison sheet.

Normally, RFP Responses would be provided by offerors, such as software vendors. However, the RFP Response Editor allows for the creation of self-authored RFP Responses, which is an option in case an offeror refuses cooperation, or if a product comparison is intended to be performed without vendor participation altogether.

When would I use the EAS?

A typical case would be the product acquisition process for a sophisticated product, which affects business operations at large for a number of years to come.

For example, consider the evaluation of a tool suite that supports Business Process Modeling. Such tool suites vary considerably in terms of functional range and level of sophistication. This is just one example of a complex software product, which warrants thorough evaluation.  

An acquisition process typically contains a subprocess titled "Perform Evaluation" or similar. The EAS supports this subprocess.

In the context of this subprocess, business analysts or business managers would normally prepare a text document or a spreadsheet, which contains evaluation criteria. Further along the subprocess, the document evolves into an evaluation matrix, which forms the basis for decision-making. The EAS supports the subprocess with purpose-specific tools. 

Why is there no trial version?

Because it is not needed. You can download the EAS and play with the demo Evaluation Specification that is in the central Evaluation Specification repository. You may wish to import the demo Evaluation Specification, modify it and perform all the steps that lead to a product comparison.

You can use the full functionality of the EAS and see if it meets your requirements, before you decide to purchase a license for an Evaluation Specification or an application. 

How is the EAS different from a simple spreadsheet-based solution?

The answer is: Preservation of the hierarchical document structure and flexibility.

The EAS supports the hierarchical document structure, which is inherent in documents such as Evaluation Specifications and Request for Proposals (RFPs). In contrast, spreadsheet tools, such as Microsoft Excel or OpenOffice Calc, more or less enforce a "flat" document structure. With such tools it is not easy to manage a hierarchical document structure. As a result, quite often, spreadsheet-based solutions can only support two-dimensional tables, which is a major limitation.

Since the EAS is not restrained by the limitations of a spreadsheet tool, it can implement greater flexibility, which shows in terms of document structure, meaningful reports and much more. EAS represents a purpose-built solution rather than a bolted-on solution.

In addition, the EAS allows for the effective collaboration of RFP issuers (potential buyers) and offerors without media disruption. An RFP issuer can make available an RFP to offerors, who can then create an RFP Response using an EAS application. Once the RFP due date is reached, the RFP issuer would process all received RFP Responses and end up with a ranking of vendor offerings.

Is the EAS an Interactive Web Application?

Interactive web applications are among today's hot topics. They run in the Web browser and do not require extra installation on a computer system.

However, mainly for usability reasons, we have deliberately decided against implementing the EAS as an interactive web application. For example, implementing drag & drop may lead to different behavior in web browsers.   

This is not to say that a web application is ruled out for the future. We are just waiting for a sound technological foundation, which allows for the development of a web application without having to incur usability deficiencies and browser-related incompatibilities.

I do not want to perform a full-fledged evaluation. Would I need the EAS anyway?

Evaluation projects sometimes start small. The only thing deemed necessary in the first instance is a feature list.

You can start small and import a ready-for-use Evaluation Specification from the central repository. You can  adapt the Evaluation Specification, if necessary, using the Evaluation Specification Editor (ESEdit). When you are done, you can generate PDF output. You will then have a comprehensive document with a feature list (including annotated requirements).

In this use case, you make actual use of the Evaluation Specification Editor, which is part of the EAS. If things develop into an evaluation project later on, you are prepared and can reuse your existing work.

What is the difference between a Public RFP and a Private RFP?

A Public RFP is a specific version of a Private RFP. In fact, it can be viewed as a subset of a Private RFP. While the structure is identical, it only contains information that a potential offeror needs to create an RFP Response. In other words, information that prospective offerors do not need in order to create an RFP Response is left out. For example, an offeror does not need to know how you rate the relative importance of a requirement (requirement weight). 

You can generate a Public RFP from a Private RFP. The Public RFP is made available to potential offerors (via E-Mail, for example), while the Private RFP is normally left untouched until you create an Evaluation Spreadsheet. The Evaluation Project Spreadsheet Editor (EPEdit) reconciles Public RFP and Private RFP, thus making all private information available to you.

The distinction between Private RFP and Public RFP is an extremely powerful concept. You can augment Evaluation Specifications with various kinds of private information (e.g. hints about technical concepts that you will find helpful when it comes to product comparison and selection). Offerors will not see private information, yet it will be available to you when you compare products.

When would I need an EAS Service Provider License (SPL)?

You need an EAS Service Provider License (SPL) when you plan to author one or more Evaluation Specifications from scratch AND perform evaluations (e.g. product evaluations).

The SPL includes the Content Authoring License (CAL) and the Subject Matter Evaluation License (SMEL).

When would I need an EAS Content Authoring License (CAL)?

You need an EAS Content Authoring License (CAL) when you wish to create Evaluation Specifications from scratch. When you purchase a ESEdit-CP license, you implicitely acquire a CAL.

Please note that the SPL also includes a CAL.

You need a CAL when you wish to author Evaluation Specifications using the Evaluation Specification Editor - Content Provider Edition (ESEdit-CPE). However, you do NOT need a CAL when you purchase an Evaluation Specification license from the online store. The license grants you the right to edit the downloaded Evaluation Specification in order to edit it with the Evaluation Specification Editor (ESEdit) and adapt it to meet your specific needs.

When would I need an EAS Subject Matter Evaluation License (SMEL)?

You need an EAS Subject Matter Evaluation License (SMEL) when you wish to perform an evaluation that is based on an Evaluation Specification whose authoring required a Content Authoring License (CAL).

Please note that the SPL also includes a SMEL. 

You need a SMEL when you wish to perform evaluations with the Evaluation Project Editor (EPEdit). However, you do NOT need a SMEL when you purchase an Evaluation Specification license from the online store. The license grants you the right to perform an evaluation with the Evaluation Project Editor (EPEdit).

I need to author a Request For Proposal (RFP). How can the EAS help?

You would use the Evaluation Specification Editor (ESEdit) to browse the Evaluation Specification repository for downloadable Evaluation Specifications. Once you have found a suitable Evaluation Specification, you can acquire a license key via the online store and register it through ESEdit. Now that you have a license key, you will be able to import the licensed Evaluation Specification. You can customize the Evaluation Specification to suit your particular needs. As the final step, you would envelope the Evaluation Specification in an RFP.

A sophisticated RFP in one day? It is possible with EAS!

Can I submit Evaluation Specifications for inclusion in the central repository?

Yes, you can! However, please be aware that customers expect you to be a subject matter expert with special knowledge in the particular area that an Evaluation Specification covers. A customer is not prepared to spend money only to find out that it better had been spent otherwise.

In addition, it is understood that you do not violate rights (e.g. copyright) of third parties, and that you are the author of an Evaluation Specification.

Jenz & Partner is committed to providing high-quality Evaluation Specifications for the benefit of all parties involved.

So, you might be a student, a domain expert in an organization, or a self-employed person. If you are a subject matter expert in a particular field, you are welcome to get in touch with us and submit Evaluation Specifications. 

I am thinking about becoming a Content Provider. What would I need to do?

The Evaluation Specification Editor Content Provider Edition (ESEdit-CP) will allow you to author Evaluation Specifications. You can use these Evaluation Specifications in the context of a product acquisition process for an organization, or you can make available your Evaluation Specifications to the public for a fee via the central Jenz & Partner Evaluation Specification repository.

If you plan to pursue the latter option, you will find more information here. 

Do I need an always-on Internet Connection?

Yes. All EAS frontend tools require a connection to the remote BMO (Business Management Ontology) server. The BMO server controls access to the repository, which contains downloadable Evaluation Specifications, code lists, and other information required by frontend tools.