Questions and Answers
CHANGE 27 WEB SERVICE URLs FROM INSECURE TO SECURE
Document #: BWC210413
Question: CONTEXT: On page 1, under Specifications you mention an attachment: Complete list of the URLs that need to be updated is attached. As of February/15/2021 - 9:00 am there are no attachments on the Procurement portal. This is required to complete an accurate proposal. QUESTION: When will the list be uploaded to the Procurement portal?
Answer: See Addendum #2: BWC210413-2 Web Service URLs to be updated
Question: CONTEXT: A single web service can be called in multiple locations. 27 web services mean at least 27 locations, but we understand some might be called multiple times. QUESTION: Does BWC have documented how many times and where each web service call will need to be updated? If the answer is yes, could you provide the number of instances in scope for this RFQ?
Answer: Each custom Handler needs to be reviewed an if a web service is called, it needs to be converted to use the updated https URLs. There are at least 60 handlers that need to be reviewed, however not all of them will require updates or modifications. ePowerCenter must also be updated to accept using https URLs (ePowerCenter is software provided by Astute Solutions and to the best of my knowledge only Astute can modify their code).
Question: Hello! Our team has 4 questions: 1. When the RPF mentions “gathering WSDL information”, does this mean that information is not available and must be discovered? 2. Are there actual code changes involved or is it modifying configurations? Several instances refer to “Updating code” of “Updating Call Handlers”. 3. Approximately how many scenarios are there for each of the 27 urls to be tested? 4. Under project assumptions, it states that the vendor will work remotely, but in all other areas it states it is on premise. Will this work be done remotely? Thank you!
Answer: 1) No, the WSDLs are all created and the data that is returned by each has been determined. They are currently in use by the IVR & ePC system. 2) Our IVR coding is written using a combination of Genesys Pure cloud Interaction Attendant and Handlers in their Interaction Designer. These custom Handlers need tool steps updated and modifications made to use secure HTTPS. 3) Each custom Handler needs to be reviewed an if a web service is called, it needs to be converted to use the updated https URLs. There are at least 60 handlers that need to be reviewed, however not all of them will require updates or modifications. ePowerCenter must also be updated to accept using https URLs (ePowerCenter is software provided by Astute Solutions and to the best of my knowledge only Astute can modify their code). 4) This can be done 100% remotely through Teams meeting sessions with myself to access the servers and do the work.
Question: CONTEXT: The work being requested to quote can vary depending on the specific system and current integrations. In the RFQ there is no information provided about the IVR system that is currently in place. QUESTION: Could you provide the minimum necessary information required to assess effort regarding the IVR system and the current integration? (Which IVR system is currently being used?) any additional information to provide a more accurate quote will be appreciated.
Answer: The current IVR is using the Genesys PureConnect (Interactive Intelligence) Customer Interaction Center, with Custom Handlers. Our current version is CIC 2019 R4. The URLs are for web services that call some internal BWC services and our CoreSuite system.
Question: CONTEXT: Under Project Tasks you state "On Premise Dev Testing Scenarios for Each Web Service". Later, under Project Assumptions and Constraints you state: "Vendor will perform work remotely via remote access." QUESTION: Is A) 100% of the work for this quote to done remotely or B) are there specific tasks, like Testing, to be done on premise? If the answer is B) could you specify which tasks?
Answer: Yes this can be done 100% remotely through Teams meeting sessions with myself to access the servers and do the work.
- Ohio|Buys Suppliers Login
- Current Contract Search
- Bid Opportunities Search
- Ohio|Buys Catalog Search
- IT Release and Permit
- Telecommunication Contracts &
Cloud Services Agreements
- IT Enterprise Services Portal
- MBE & EDGE Opportunities
- State Contract Opportunities
- State Printing and Mail Services
- Agency Request to Purchase
- Procurement Related Web Links
- State Procurement Manual
- State Procurement Supplier Handbook
- Agency State Term Schedule Purchases
- FY 2018 (07/1/17-09/30/17)
- FY 2018 (10/1/17-12/31/17)
- FY 2018 (01/1/18-03/31/18)
- FY 2018 (04/1/18-06/30/18)
- FY 2019 (07/1/18-09/30/18)
- FY 2019 (10/1/18-12/31/18)
- FY 2019 (01/1/19-03/31/19)
- FY 2019 (04/1/19-06/30/19)
- FY 2020 (07/1/19-09/30/19)
- FY 2020 (10/1/19-12/31/19)
- FY 2020 (01/1/20-03/31/20)
- FY 2020 (04/1/20-06/30/20)
- FY 2021 (07/1/20-09/30/20)
- FY 2021 (10/1/20-12/31/20)
- FY 2021 (01/1/21-03/31/21)