Priority Technology Requirements Vendor Response Comments 10) What database repositories will the application work with? Required List all. Do you provide migration tools if the underlying database has to be changed from one vendor to the other? 11) Does the application allow multiple users to update a single Required document concurrently? If so, how many? b. Scalability 1) Is your application N-Tiered? If so, describe how the different Required shall be deployed to support 24x7 availability with 99.99% uptime and transparent failover protection. Nice to Have/ 2) Does the application have built in load balancing capabilities Answer Required (i.e. two application servers sharing work load)? If so, please explain the architecture needed to support it (both hardware and software). 3) Is there a limit on the number of registered users the package Required can support? If so, how many? 4) Do you have well documented evidence of the number of concurrent users that will be supported by a given physical Required hardware configuration? Will this number scale linearly with the capacity of the hardware configuration? 5) What is the maximum limit to the amount of transactions, Required collaborations, events being managed (workflow) that can be handled per session, per day? How many in each case? Nice to Have/ 6) What is the average response time for initial page load, to Answer Required page re-access and database access? Nice to Have/ 7) Does the application maintain transaction and data integrity Answer Required in failure situations, and if so, how? 8) Does the application maintain transaction logs? Nice to Have/ Answer Required Nice to Have/ 9) Does your application take advantage of any caching Answer Required technique for loading pages, static content, data, etc.? If so, please describe. Nice to Have/ 10) Can all administration activities be performed with the Answer Required application up and running in production?
Priority Technology Requirements Vendor Response Comments Required 10) What database repositories will the application work with? List all. Do you provide migration tools if the underlying database has to be changed from one vendor to the other? Required 11) Does the application allow multiple users to update a single document concurrently? If so, how many? b. Scalability Required 1) Is your application N-Tiered? If so, describe how the different shall be deployed to support 24x7 availability with 99.99% uptime and transparent failover protection. Nice to Have/ Answer Required 2) Does the application have built in load balancing capabilities (i.e. two application servers sharing work load)? If so, please explain the architecture needed to support it (both hardware and software). Required 3) Is there a limit on the number of registered users the package can support? If so, how many? Required 4) Do you have well documented evidence of the number of concurrent users that will be supported by a given physical hardware configuration? Will this number scale linearly with the capacity of the hardware configuration? Required 5) What is the maximum limit to the amount of transactions, collaborations, events being managed (workflow) that can be handled per session, per day? How many in each case? Nice to Have/ Answer Required 6) What is the average response time for initial page load, to page re-access and database access? Nice to Have/ Answer Required 7) Does the application maintain transaction and data integrity in failure situations, and if so, how? Nice to Have/ Answer Required 8) Does the application maintain transaction logs? Nice to Have/ Answer Required 9) Does your application take advantage of any caching technique for loading pages, static content, data, etc.? If so, please describe. Nice to Have/ Answer Required 10) Can all administration activities be performed with the application up and running in production?
PCMS%20Word%20Version%20of%20Required%20Forms.docx