Attachment H - Commonwealth's Response to Vendors' Written Questions RFP 758 2300000411.xlsx
XLSX spreadsheet 24 KB Posted
- Attached to
- Learning and Employment Records Digital Wallet
- Solicitation number
- RFP-758-2300000411-2
- Issued by
- Franklin County, Kentucky
About this file
This document is the Commonwealth's Response to Vendors' Written Questions for Request for Proposal (RFP) 758 2300000411. The RFP is seeking a solution for a digital wallet that can store and share secure, verified credentials for learners and earners. The project will involve partnering with in-state universities, employers, and other stakeholders for a pilot program. While the Commonwealth has not determined exact user numbers, they estimate the potential user base to be around 200,000 employers and 2.7 million citizens in the 18-65 age range. The pilot is expected to run for a minimum of six months, and the vendor will be responsible for integrating with the Commonwealth's API to enable credential issuance and revocation.
The Commonwealth has not set a specific budget for this project, but they are open to COTS solutions that can meet the open source and other technical requirements outlined in the RFP. The vendor will be responsible for the costs of any security remediations required for their proposed solution. The Commonwealth will procure any necessary third-party software licenses or cloud resources through their existing contracts, and these costs should be excluded from the vendor's cost proposal.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1 Attachment H - Commonwealth's Response to Vendors' Written Questions - RFP 758 2300000411
| Question # | RFP Section / Requirement Number | Document | Document Page Number | Vendor Questions | Commonwealth Response |
| 1 | Section 4.1 page 6 hosting | Attachment A Terms and Conditions | Page 6 | Hosting refers to cloud AWS or Azure for the digital wallet. Is the additional use of distributed ledger/blockchain technology for storing validation pubic encryption keys as DIDs only to enable self-sovereignty and global interoperability of credentials acceptable? | This question is unclear. This is acceptable if the vendor is stating that they intend to meet the hosting requirement for the core solution with the addition of leveraging distributed ledger technology for DID sharing. |
| 2 | Section 3.1-2b | Attachment A-Scope of work | 6 | How much user base is expected in the production environment? | We have not established that, since we are in pre-pilot, but Kentucky has approximately 200,000 employers and approximately 2.7 million citizens between the ages of 18 and 65. |
| 3 | Section 3.1-3b | Attachment A-Scope of work | 6 | Are all credentials supposed to be uploaded directly by universities/ training institutes or by the job seeker? If it's directly by universities, will commonwealth help in building partnership with all the universities? How will it be handled in the case of foreign universities, if they don't agree to share candidate's credentials on the digital wallet? | We currently envision not having the job seeker perform the upload. This project will partner with universities in state for the pilot. Any expansions to this scope will be considered after we evaluate the pilot results, thus we've not yet considered foreign universities. |
| 4 | Section 3 | Attachment A-Scope of work | 6 | What would be the life period of the documents in the digital wallet (repository). Normal access repository / archive repository? Any specific number of years expected after which to remove the data of a user? | We've not defined an end to the retention period. |
| 5 | Section 3 | Attachment A-Scope of work | 6 | After access authentication, is there any provision required for limitation of information which needs to be shared with businesses and educational institutes? | We have not yet set any limitations; although that may change as requirements are defined by our stakeholders. |
| 6 | Section 4.2b | Attachment A-COT Requirements | 7 | Is there any standard frequency/schedule for commonwealth system changes, which might affect the development/implementation of solution for this RFP | Change Management hosts a weekly Change Advisory Meeting and publishes a Schedule of Changes that can be referred to by the awarded vendor and agency. |
| 7 | Section 4.4 | Attachment A-COT Requirements | 7 | Is the cost of engaging a third party certification registrar supposed to be included in the RFP or it can be billed separately when those services are used by vendor? Also, is there a preferred third-party certification registrar for commonwealth? | We want the RFP responder to provide a total solution as a prime contractor,under a single contract, and to subcontract as required to meet our requirements; so that cost should be included in the RFP response. |
| 8 | Section 4.4 | Attachment A-COT Requirements | 7 | Do we need to provide the API to employers and educational institutions to connect with the Digital Wallet or they will provide their APIs for us to connect? | We have not yet made this decision, but anticipate providing the APIs to employers to encourage their participation. |
| 9 | Section 4.5 | Attachment A-COT Requirements | 8 | In case of engaging a third party to address any security findings, will those costs be paid by commonwealth or it is going to be the responsibility of the vendor and should account for in the cost proposal? | Cost of remediation of any security findings would be the responsibility of the entity responsible for the flaw remediation. Security flaws in the products or services delivered by the vendor, directly or through subcontractor arrangement would be the responsibility of the vendor. |
| 10 | Section 4.9 | Attachment A-COT Requirements | 9 | Since any software licenses and cloud resources will be procured via commonwealth's existing contracts, does it mean that vendor does not need to include those costs in the cost proposal and it will be directly paid by Commonwealth? | Section 4.9 states "Any third-party software licenses and cloud resources necessary for the proposed solution may be procured via the Commonwealth’s existing contracts". If the Commonwealth uses existing contracts, the Commonwealth will pay the existing contract holder directly. Please complete the cost proposal as instructed. |
| 11 | Section 3.1.3 | Attachment A | 6 | Is there a minimum or maximum time period that the Commonwealth desires the pilot to run? | We expect the pilot to run for a minimum of six months. |
| 12 | 3.1 Scope of Work/Technical Requirements 1.a | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 5 | How many entities should be considered from business, education, state local agencies, licensing boards and workforce development boards for stakeholder identification? | We have not yet determined this. |
| 13 | 3.1 Scope of Work/Technical Requirements 2. | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 5 | Does the Commonwealth have any requirement for on-premise or cloud hosted solution and any preferred cloud hosting provider (AWS, Microsoft etc.) ? | See Section 4.1 of the RFP. |
| 14 | 3.1 Scope of Work/Technical Requirements 3.b | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 6 | For the Proof-of-Concept, how many credentials should be developed for a trusted source? | We have not yet determined this. Vendors are encouraged to provide this assumption on which to base their price. |
| 15 | 3.1 Scope of Work/Technical Requirements 3.d | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 6 | For the Proof-of-Concept, does the Commonwealth require real or dummy Credentialing institution and/or licensing board? | We plan to engage real credentialing institutions. |
| 16 | 3.1 Scope of Work/Technical Requirements 3.e | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 6 | For the Proof-of-Concept, does the Commonwealth require real or dummy employer? | We plan to partner with a few selected employers. |
| 17 | 3.1 Scope of Work/Technical Requirements 2. | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 5 | Does the state use an enterprise identity system that it intends to use for verifying LER identities? | The Commonwealth does have an identity management system, but only for state employees. |
| 18 | 3.1 Scope of Work/Technical Requirements 2. | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 5 | Does the state intend to adopt a web/cloud based digital wallet, or a user mobile based wallet? | Our intention is to adopt a user mobile based wallet. |
| 19 | 3.1 Scope of Work/Technical Requirements 3a. | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 6 | For the pilot, how many skill credentials will be issued to each learner/earner? | We have not yet determined this. Vendors are encouraged to provide this assumption on which to base their price. |
| 20 | 3.1 Scope of Work/Technical Requirements 3c. | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 6 | Will the credential issuers (termed "credentialling institution/licensing board" in the RFP) be responsible for integrating with Vendor published wallet APIs/services to issue credentials, or is the Vendor responsible for integrating their applications with digital wallet services? If yes, how many applications need to be integrated as part of the pilot? | For the pilot, we assume that the Vendor will integrate with the API, which will involve a small number of applications (we do not yet have a specific number). |
The scope for the production environment will be determined after the evaluation of the pilot.
| 21 | 3.1 Scope of Work/Technical Requirements 3. | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 6 | Does the pilot need to support a skill credential revocation use case? | Yes. |
| 22 | 3.1 Scope of Work/Technical Requirements 2. | Attachment A - Terms and Conditions - RFP 758 2300000411 | Pg. 5 | Does the state intend to limit the Digital Wallet to holding LER related skill credentials? | For the pilot, yes. |
| 23 | 3.1 Scope of Work/Technical Requirements | Can we provide stakeholders a CLR/LER system for them to issue/award credentials in CLRv2 standards in case they don’t comply with any interoperable standard? | To be determined after the pilot. | ||
| 24 | 3.1 Scope of Work/Technical Requirements | Our Digital Wallet is a proprietary software as a service. Would this comply with the proposed Scope of Work? | No. | ||
| 25 | 3.1 Scope of Work/Technical Requirements | Which is the age range for learners/earners? | We have not yet determined this age range | ||
| 26 | 3.1 Scope of Work/Technical Requirements | Is OpenBadges 3.0 suitable to be included as a standard for credentials in conjunction with CLR v2.0? | We encourage open source standards. | ||
| 27 | 3.1 Scope of Work/Technical Requirements | Should we include technical support for stakeholders and learners/earners as part of our proposal? | Yes. | ||
| 28 | 3.1 Scope of Work/Technical Requirements | Could you express what the desired outcome of the pilot should be? It could be expressed in terms of KPIs or any other method. | The concept we are attempting to prove is that we can align our institutions, employers and other stakeholders with the requested technology to provide institutions, employers and learner / earners with accurate, secure, verified and interoperable learning and employment data. | ||
| 29 | 4.1 Hosting | Since our Cloud provider is Microsoft Azure, which complies with FedRAMP, should we include their certification? | It is not a requirement, but yes it can be included in the response. | ||
| 30 | General | RFP | General | Can the Commonwealth share their anticipated budget for this project? | No. |
| 31 | General | RFP | General | Does KYSTATS desire a custom application or a COTS solution? | If a COTS solution can comply with our requirements for open source, we would consider it. |
&P
Sheet2
Sheet3
File details come from the government source that posted it. Updated .