SOURCES SOUGHT
R -- Controlled Unclassified Information Implementation Program Support
- Notice Date
- 2/27/2019
- Notice Type
- Synopsis
- NAICS
- 541611
— Administrative Management and General Management Consulting Services
- Contracting Office
- Department of Veterans Affairs;Technology Acquisition Center;23 Christopher Way;Eatontown NJ 07724
- ZIP Code
- 07724
- Solicitation Number
- 36C10B19Q0207
- Response Due
- 3/8/2019
- Archive Date
- 5/7/2019
- Point of Contact
- david.sette@va.gov
- Small Business Set-Aside
- N/A
- Description
- Sources Sought This is a request for information (RFI) only. This is a Sources Sought to conduct market research and to determine the availability of vendors capable of providing a Controlled Unclassified Information (CUI) program that standardizes and simplifies the way the Executive Branch handles unclassified information that requires safeguarding or dissemination controls, pursuant to and consistent with applicable law, Federal regulations, and Government-wide policies. Do not submit a proposal. It is requested that all contractors interested in participating in this effort please note their interest and provide indication of their respective capabilities to perform the effort described in the attached draft Performance Work Statement (PWS). BACKGROUND: On November 4, 2010, President Obama signed EO 13556, establishing the CUI Program and designating the National Archives and Records Administration (NARA) as the CUI Executive Agent (EA) to oversee agency actions and ensure compliance. The Archivist of the United States delegated these responsibilities to the Information Security Oversight Office (ISOO). The CUI Program is an information security reform designed to standardize the way the executive branch handles information that requires safeguarding or dissemination controls. This excludes information that is classified under EO 13526, Classified National Security Information, 75 FR 707 (January 5, 2010), or any predecessor or successor order; or the Atomic Energy Act of 1954 (42 U.S.C. § 2011, et seq.), as amended. On November 14, 2016, 32 CFR 2002 was effective as policy for agencies on designating, safeguarding, disseminating, marking, decontrolling, and disposing of CUI, self-inspection and oversight requirements, and other requirements of the Program. 32 CFR 2002 affects federal executive branch agencies that handle CUI and all entities that handle, possess, use, share, or receive CUI as well as other entities which operate, use, or have access to federal information and information systems on behalf of an agency. The VA CUI Program will be implemented in phases. In other words, legacy practices (policies and practices used to protect Sensitive but Unclassified [SBU], Personally Identifiable Information [PII], VA Sensitive Information/Data, Protected Health Information [PHI], and other sensitive information types) and CUI practices will coexist until full migration is achieved. VA legacy practices will eventually be replaced by CUI standardized approaches to information protection and handling. This RFI is for planning purposes only and shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI. Your response to this RFI will be treated only as information for the Government to consider. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. The information provided may be used by VA in developing its acquisition strategy and PWS. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government does not intend to pay for the information submitted in response to this RFI. Be advised that set-aside decisions may be made based on the information provided in response to this RFI. Responses should be as complete and informative as possible. The North American Industry Classification System (NAICS) for this requirement is 541611 with a size standard of $15.0 million. A company that is a Service-Disabled Veteran-Owned Small Business (SDVOSB) or a Veteran-Owned Small Business (VOSB) must be VIP registered and verified (http://www.va.gov/OSDBU/index.asp). An SDVOSB or VOSB company that is not a VIP registered and verified SDVOSB or VOSB should not respond to this notice. Generic capability statements will not be accepted or reviewed. Your response must address capabilities specific to the services required in the attached **draft** PWS and must include the following: Name of Company: Cage code and DUNS Number: Address: Point of Contact: Phone Number: Fax Numbers: Email Address: Any applicable contract vehicles (Transformation Twenty-One Total Technology Next Generation (T4NG), General Services Administration (GSA), Mission Oriented Business Integrated Services (MOBIS), Veterans Technology Services (VETS) Government wide Acquisition Contract (GWAC), etc.) Provide a summary of your technical capability to meet the requirements as defined in the draft PWS. As part of your RFI response, please address your expertise and qualifications in the following areas: Controlled Unclassified Information (CUI) Training and Web-based Training Development Development and execution of training on CUI Program (including PII and PHI). Development and execution of web-based training programs Knowledge of VA CUI legacy practices and protocols necessary to develop and execute phased training until the VA fully migrates to the new NARA-defined CUI standards. Policy and planning Federal policy development and implementation for CUI programs and NARA guidelines. CUI reporting requirements VA CUI legacy practices necessary to develop policy and planning documents until the VA fully migrates to new NARA-defined CUI standards. Baseline CUI assessments of IT systems Assessing CUI impact on systems Knowledge of IT systems impact on VA CUI legacy practices. Knowledge of VA legacy CUI practices VA CUI legacy practices (VA practices used to protect Sensitive but Unclassified [SBU], Personally Identifiable Information [PII], VA Sensitive Information/Data, Protected Health Information [PHI], and other sensitive information types) and new CUI practices will coexist after expiration of the current VA CUI contract. Until VA s legacy practices are replaced by the new NARA-defined CUI practices, a prospective bidder must possess expertise in existing VA CUI legacy practices. Knowledge of VA legacy practices will be critical for training, reporting and ongoing assessment of VA IT systems. Small businesses should also include information as to: The intent and ability to meet set-aside requirements for performance of this effort, if set-aside, as set forth in Veterans Affairs Acquisition Regulation (VAAR) 852.219-10 (JUL 2016) (DEVIATION) and VAAR 852.219-11 (JUL 2016) (DEVIATION) VA Notice of Total SDVOSB Set-Aside and VA Notice of Total VOSB Set-Aside, respectively, and 13 CFR §125.6, the contractor will not pay more than 50% of the amount paid by the Government to it to firms that are not SDVOSBs or VOSBs as defined by VAAR 852.219-10 (JUL 2016) (DEVIATION) and VAAR 852.219-11 (JUL 2016) (DEVIATION). Please note that in accordance with 13 CFR §125.6 limitations on subcontracting requirements, demonstrate how you will not pay more than 50% of the amount paid by the Government to it to firms that are not similarly situated. Information as to available personnel and financial resources; full names of proposed team members and the PWS requirements planned to be subcontracted to them, which must include the prime planned percentage or the names of the potential team members that may be used to fulfill the set aside requirement. Has the draft PWS provided sufficient detail to describe the technical requirements to be performed under this effort. ______ YES _______ NO (if No, answer question c) If NO, please provide your technical comments/recommendations on elements of the draft PWS that may contribute to a more accurate proposal submission and efficient, cost effective effort. Specific Response Instructions: Please submit your response to this RFI in accordance with the following: Provide the Vendor Capabilities Response which encompasses items 1 through 5 and any sub-items in less than 10 pages (excluding transmittal page). Vendors shall be aware that the file size for email submissions is 5MB. Submit your response via email to the Contracting Officer, David Sette, at David.Sette@va.gov and the Contract Specialist, Jamie.McPherson at Jamie.McPherson@va.gov. Submit your response no later than 12:00PM ET on Friday, March 8, 2019. If there are any vendor questions regarding the requirement, the contracting office will coordinate a comprehensive response and post to Federal Business Opportunities Page (FedBizOps). Mark your response as Proprietary Information if the information included is considered to be business sensitive and/or includes trade secrets. NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (27-FEB-2019); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT 877-472-3779 or fbo.support@gsa.gov REGARDING THIS ISSUE.
- Web Link
-
Link To Document
(https://www.fbo.gov/notices/ad5a131e7811a881f2b5ffd6927e266d)
- Record
- SN05234607-F 20190301/190227230024 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |