Select a question to reveal the answer.
Q: The RFP includes a lot of Commonwealth language. Are we anticipating any additional Commonwealth requirements?
A: At this time we have not been instructed to include any additional Commonwealth requirements.
Q: Can you clarify ‘alternate implementations’ for SSO?
A: We currently use middleware for Clever, ClassLink, Google and custom SAML implementations between the existing authentication system and SSO platforms, but we are open to alternate SSO implementations. We are also interested in Microsoft-based options.
Q: Does HSLC see any changes or additions with regard to e-resources or current services?
A: Changes or additions are outside of scope of this RFP, and would be handled via change orders. However, we do ask for costing of the possibility for geo-authentication, alternate SSO methods, etc.
Q: If different vendors are selected for each product, how are you handling potential one-time costs? Or rather, even if 1 product was with another vendor, how would we handle the cost of integration?
A: Our goal is to bundle. Cost is a 40% factor, but we can use the BAFO process to make the one-time costs align within the budget.
Q: Section 1.5 Contract, page 7, states “It is expected that if the Issuing Office enters into a contract as a result of this RFP, it will be a Fixed Price contract containing the Contract Terms and Conditions as set forth in this document.” Are there any portions of the contract or T&Cs that are negotiable?
A: We have asked vendors to specify any requirements they feel unable to agree to, per the checklist on Attachment A.
Q: Does your agency require U.S.-based customer support?
A: HSLC has no requirement that customer support be based in the U.S.
Q: We can propose for the parts we have a solution to and not propose for the ones we do not?
A: Correct. Offerers may respond only to the parts as appropriate.