UNIVERSITY OF NORTH CAROLINA AT CHAPEL HILL

Transcription

1 REQUEST FOR PROPOSAL (RFP) ADDENDUM FAILURE TO RETURN THIS RFP ADDENDUM IN ACCORDANCE WITH THE INSTRUCTIONS BELOW MAY SUBJECT YOUR PROPOSAL TO REJECTION. RFP Number: 65-RFP AMW Addendum Number: 01 Addendum Date: January 25, 2019 RFP Opening Date/Time: February 7, 2019 at 2:00 pm ET INSTRUCTIONS: Return one properly executed copy of this addendum prior to the RFP Opening Date/Time specified above. This addendum may be included with your submitted proposal, or it may be ed separately to Alicia Waymack at Please see the following University responses (in red) to all questions received by the deadline to submit written questions of January 21, 2019 at 2:00 PM ET: 1. Whether companies from Outside USA can apply for this? (like, from India or Canada) Yes. 2. Whether we need to come over there for meetings? 3. Can we perform the tasks (related to RFP) outside USA? (like, from India or Canada) Some, not all. 4. Can we submit the proposals via ? Questions 5 21 reference Section What is the estimated cost of the Automated Testing Solution System? We have no target in mind. Less is better. 6. Has the University allocated funding for the Automated Testing Solution yet? If so, through which source (budget, CIP, state/federal grant etc.)? Yes. N/A. 7. Can the University elaborate on any additional drivers behind this acquisition that may not be addressed in the RFP? All drivers are stated in the RFP. 8. Who is the technical contact and/or project manager for the Automated Testing Solution project? N/A. Please reference Attachment A, Instructions to Vendors regarding communications by vendors.

2 9. How is the Department currently meeting this need? Which vendor provides the incumbent Automated Testing Solution system? There is no incumbent vendor solution. 10. Aside from the Automated Testing Solution, what are the three greatest technology challenges the University faces? N/A. 11. The solution allows for testing of multiple types of software, including but not limited to Peoplesoft version 9.2. Please specify the different types of software applications, and types of testing conducted for these types of software. Are these applications desktop or web-based? In addition to PeopleSoft we use other applications we'd like to automate testing on including both homegrown and third-party. We are focused on the testing of application software that exists to serve the needs of the UNC community. These are mostly web-based applications. Some of the home-grown are JAVA based. We regression test existing functionality when changes or new releases come out. We also do extensive positive and negative testing related to rolling out new capability. At times we do test the performance of the system transitions or pages. Lastly, we would like to be able to test how the system performs under load. 12. The solution works equally well (same features and look/feel) regardless of which application is being tested. Any specific look/feel features? Nothing specific. This is mainly about similar ease of use by different types of staff (functional and technical). We want to be sure we can make very quick/good use of whatever solution we buy. Ease of use/look and Feel is an important part of whether the product can be used effectively. 13. Provide list of home-grown applications, 3rd party packages, new applications, # Total regression test cases, # Automation tests. This information is not required to provide a response to the RFP. 14. Pls share the technology stack of the applications, testing tools used, including existing automation tools. This information is not required to provide a response to the RFP. 15. Ability to orchestrate testing scenarios with dependencies - Please elaborate more on dependencies. We want to be able to trigger a 2nd test based on the outcome of the prior test being successful or having seen a specific result of the 1st test. 16. Can you pls share list of specific productivity features? We want the vendors to call attention to any productivity features their products may have. We do not have a specific list we are looking for. 17. Ability to administer granting/maintaining access to users Please elaborate more details on access permisssions at solution level/ component level. We need to be able to easily self-administer who has access to use the tool and at what level of access. For example, we'd expect some small number of people would have admin type access, others the ability to create/edit and run tests, perhaps a group that can only run test cases and perhaps even a group that can just review testing results. We may also want the ability to limit on what applications certain users can test. We'd like to understand what options we have to grant security and how easy it is to do.

3 18. Solid implementation track record Please elaborate with more details. Tell us where you have implemented your solution, how long it took, is the customer very happy with the tool and so on. 19. The solution supports later versions of commonly browsers - Please elaborate more details the browser enablement is at the solution level or component level. We'd like any product to work with the later versions of IE, Chrome and the others. Say anything issued in 2017 or later. We would not expect a vendor to support browser versions from years ago. IE as an example has evolved greatly from its first version to now. We would not expect the software to work with every iteration of that browser. 20. Please share the format/kind of the test data inputs to the application. Manually entered, entered from a file and we'd also like to if any products allow for dynamic input via queries. 21. Does this review pertain to manual or automated test cases? Preferred mode of review comments. We want users of the tool at UNC to be able to view/use the recorded tests cases other UNC users create. 22. Is it possible to get the word version of the Terms & Conditions? It will make it easier for us to recommend the exceptions, we might request for few clauses. Yes. Please Alicia Waymack at awaymack@unc.edu to request a copy. 23. Is there a contact center in the University? Are you using any IVR, if so which organization/brand? Are you also looking to automate the contact center software, IVR? How many agents in the contact center? N/A. 24. (Reference Section 2.3) Please provide approximate counts of anticipated users of the automated solution by application pillar (i.e. PeopleSoft HCM, PeopleSoft FSCM, Other Application #1, Other Application #2, etc.). The user count information is not going to be provided. But I can say we will have 100+ users of this solution and they can assume the # people testing PeopleSoft vs. other software is 50/50. I will further say we use HR/Payroll, Finance, Student and the Enterprise Portal here at UNC and all are within PeopleSoft so they should not focus just on the two areas above. 25. (Reference Section 2.3) Do you anticipate that business end users will perform automated testing with the selected tool, or will the tool be limited to use by the trained testing team? Anyone using it will get trained 1st, but after the initial rollout that will be done by UNC staff. I would expect that after the first six-twelve months non-its staff would leverage this tool. That could include business end users. 26. (Reference Section 2.3, 3.3) Do you anticipate having vendors conduct product demos prior to the trial period? More likely at the start of the trial period to help kickoff the trial. The only way a demo would be requested pre-trial is if the team cannot decide on the 3-4 vendors we are interested in without one.

4 27. (Reference Section 2.3) As with any software, customers need to be well trained and advised on its usage from the vendor. UNC's stated expectations are that within 90 days, the software will be installed, UNC IT users trained and fully self-sufficient. Is this every team supporting every product that UNC will eventually use the product for, or is this specifically for PeopleSoft? The expectation is that people on teams supporting PeopleSoft and other applications will be trained during this period. We estimate this to be approximately 50 people. 28. (Reference Section 3.3) Do you have set expectations or criteria for the trial period? Can you share those with us? We will have specific testing criteria for the trial but do not have these specific as yet. We will ensure the same things are trialed across every vendor. Our expectation is that we will use this trial period to verify the claims about the features and how they work, to verify our understanding of how the software could be used here, get a sense of ease of us and help us pick the best product. 29. (Reference Section 3.3) Please describe the expected vendor support during the 60-day trial period (i.e. training, Q&A, application support, etc.). We would like two main things: a. To have a means ( will work) to ask and get questions answered within 2 business days. The vendor would have the opportunity to suggest a call/webex type session as a way to talk though any complex questions. b. To have access to any how-to information like training guides, job aides or anything that would lessen the learning curve and reduce questions we might have. But no formal training is required. If proposed by a vendor, we would be willing to consider some initial informal and virtual training to jump start the trial. 30. (Reference Section 3.3) Do you anticipate having multiple vendors provide the 60-day trial period or just the expected vendor of choice? We anticipate having 3 4 vendors provide the 60-day trial period. 31. (Reference Section 5.1.A.1.a) Please list the other applications besides PeopleSoft for which you would like to use the automated solution. There are too many to list. Custom applications we have developed on different platforms include Java and some third-party software. 32. Do you have a current comprehensive set of manual scripts? Can you provide an approximate count of scripts by business area (i.e. HR, Payroll, Accounts Payable, Security, etc.)? Yes. We have hundreds with tens (as a minimum) across each area. 33. Can you describe your anticipated major testing events - i.e. for PeopleSoft, are they planned PUM Images, PeopleTools upgrade, business process redesign, infrastructure updates, etc. For other applications, are there also planned upgrades? There are upgrades outside of PeopleSoft. We have all these testing events plus adding new capability and the testing needed just to make other day-to-day changes to software. This applies to all types of applications. 34. Do you have a formal testing methodology? If so, what is it? It varies by project.

5 35. Is there a particular business catalyst driving a timeframe for selection and/or deployment? The desire to reap the benefit of the automation. So, the sooner the better within the parameters of having enough time to make the best decision. 36. (Reference Section 2.3) Is UNC open to having an automated testing capability offered as recurring testing managed service where the vendor is responsible for the creation, maintenance, and execution of the testing framework on behalf of UNC and in partnership with UNC? In this scenario, UNC will be responsible for testing requirements, setup of test environments, software updates, test data, test IDs, security setup, and configuration changes. Questions reference Section How many applications do you need to automate? As many as possible. 38. Application will run on which platform like web, mobile, desktop. Please share the high-level diagram of applications architecture. It needs to run first and foremost on desktops and laptops which are the typical devices we work on every day. They in turn will connect to the test automation application and access various applications in use at UNC. There is no diagram to share. Many of our applications have Single Sign-On, Web, Application and db instances that integrate and some also include load balancing aspects. 39. Do you already have manual test cases which you need to automate? If yes, then; a. Share the count of Manual Test Case that you have. We do today already have hundreds of cases to automate. b. Do you need to add more Test Case in Future? If yes, then please specify the scope. We will want to add more. No projected number. 40. Do we have to manually write test scripts for any application as part of Automation? Possibly. This may be needed in the first 90 days depending on the tool. 41. Do you already have automation scripts? We do not. If yes, then: a. Which tool have you used for automation? b. Which language have you used for automation? c. Do you need to convert scripts in to latest tools or you need to continue with old tool? 42. How many release builds are planned in a month for automation? We implement changes to production on various intervals. 43. What type of testing you need to automate (i.e. Functional Testing, Performance Testing, API Testing)? Any of the above. The testing of new/changes in functionality including integrations is a higher priority than performance testing.

6 44. How many test cases per time frame have you decided for Automation? We have not specified any target number. 45. Will you provide KT session of your application? If yes, please share the time frame. 46. What is plan for maintenance activity for automation scripts? None at this time. The tool and its capability will help determine that. We do not plan to need vendor support for this. 47. Do you need training after completion of scripts? If yes, how many resources will be involved in training? We expect training in how to use the tool before we create scripts and help in the first 90 days to do this more and more efficiently. For approximately 50 people. 48. Will the Product Support be available online? We want you to tell us how you support your product. If yes, then: a. What will be the support hours? b. What will be the Support Response Time? c. What will be the Level of Expertise of Support team? 49. Please share the hardware dependency to run your application, if any. You need to tell us if there are any dependencies. We are interested in any dependencies the software has on what hardware it can run on. UNC has no restrictions. 50. Please share the details of DRM / CAS used for the Application. There are many different applications. If your solution/tool has DRM or CAS needs, you should specify what if anything you require from UNC to make the application work. Our ability to provide that and at any additional work/cost would be factored into our evaluation. 51. Do you need Watermarking as well? 52. Please specify the Authentication Protocol / Mechanism, if any. Could be multiple based on the application and environment. i.e. Shibboleth for integrated PeopleSoft environments but direct authentication for those that aren t integrated (PAY, FUN, for HCM). Authentication by test users to the application being tested depends on which form of authentication the application is using. Authentication to the testing software itself should support SAML authentication, and the InCommon federation if possible. It would be best if the testing software recognized the ismemberof attribute in the SAML assertion for permissions as needed, including administrative permissions. We also use two-factor authentication. 53. (Reference Section 5.2) What is the size of your desired project team from your implementation partner? We have no preset expectation. Smaller the better given this will drive costs.

7 54. (Reference Section 4.2) Is there a target budget number for this project? Can you share any project budget information? We have no target in mind. Less is better. 55. What PeopleTools version is your organization currently on? for most areas, but moving to by end June. 56. Are you currently working with anyone that is responding to this RFP? We will not know until we see the responses. 57. Do you have preferred consulting partners? If you do, can you share who they are? We do not. 58. Who are the decision makers for this RFP? The team of approximately 15 people across ITS that have been engaged on this since last fall. 59. What is your Test Script count? Hundreds and Hundreds of cases. 60. (Reference Section 5.1 A) Please provide complete list of applications including ERPs, Web application, mobile applications, legacy application and thick client (desktop) application and their technology landscape. PeopleSoft HR/Payroll, Finance, Student, Enterprise Portal plus dozens of other applications. 61. Does UNC expect the solution to be integrated with any application level tools eco systems. If yes, please provide the list of below tools for each application: Requirement management tool Build management Test / Defect Management Continuous Integration JIRA for Defect Management. We d like the tool to be able to integrate with Cybermation (automated job scheduling tool). We would also be interested in how the tool integrates with ServiceNow. 62. (Reference Section 5.1 B) Does UNC has any cloud preferences such as AWS, Cloud, Azure etc.? 63. (Reference Section 5.1 B) Please provide a ballpark number on number of licenses required by UNC. Enterprise is preferred; otherwise ballpark is 500 licenses. 64. (Reference Section 2.3) We are assuming the 60 days duration is solution implementation services only, it does not include: Customizations as per UNC needs Integration with UNC tool landscape Training services Please confirm.

8 We d like all work to be complete no later than 90 days after we start the project. This includes customizations, integration and training. 65. Assuming UNC will own environments for multiple / parallel test executions such as multiple Operating systems, mobiles, parallel execution tools for compatibility testing. The vendor responsibility is to integrate our solution to such environment / tools. Please confirm. We expect the solution to be up/running on all needed environments within 90 days and ensuring that is the vendor responsibility. The vendor could do it and/or pass along the knowledge needed to do so to UNC ITS. 66. (Reference Section 2.3) Please provided number users required for 60 days free trial. Please explain if UNC would like to review any specific requirements / features during free trail. 15 users. We will have a list of things to test/validate and use the same across all trials. That list is not yet compiled. 67. (Reference Section 5.1 A) Does UNC have any tools for Test data management? Please provide high level details on current test data practice. Current practices vary. Questions reference Section 5.1 B 68. Please elaborate the below point mentioned in RFP as part of Section B Additional Software Features Desired: Should support real-time integration, or batch mode when sending data to/from other systems Please provide more details on Real time integration and frequency of batch? Does UNC expect to vendor to provide such integration during support duration and should vendor train UNC team to perform such tasks? When we test today, we often send data across modules or applications to see the end to end results of testing a change. Real-time web services and the ability to kick off processing via a job scheduling solution (we use Cybermation) are required. In test, we run batch scheduled nightly as needed and ad hoc. We require no vendor support for actual integration in the trial, but may be validating how this would work and if our needs can be met by asking questions. We would expect a vendor to configure/install to make integration possible once the contract was awarded as part of the first 90 days of work. We would also expect a vendor to train ITS staff on how to support/make changes post 90 days. 69. Assuming UNC will own load generation and environment configurations for conducting performance testing. Please confirm. Vendor will provide required training for UNC team to perform such tasks. We would expect to have to do no additional setup to facilitate performance testing. If UNC would need to do any work here initially or post 90 days, we would need training and related documentation. 70. Please provide list of performance testing types (Load testing, stress testing, endurance testing, benchmark testing etc.) along with expected /indicative user load.

9 For load/stress testing, we d like to simulate up to 2,000 cases. We d be interested in any load testing capability the tool has and any number limitations that go with. Performance testing/benchmark testing the number of users should be very low at one time. 71. Please provide the list of preferred web browsers, operating systems and mobile OS to assess our solution compatibility. Chrome, Safari, Edge, IE and Firefox. MAC/Windows/Linux. Android/IOS. 72. Do you have any preferred SLAs? And Does UNC expect 24 x 7 support model? We want to know what the vendor is offering for other customers but would not expect a 24 x 7 support model. We can probably live more in a 7 7 business day support model. Execute Addendum: Vendor Name: Authorized Signature: Date: Name and Title (Print/Typed): Address: