Sources Sought Notice_36C10B26Q0317.docx

Sources Sought Notice

Veteran Decedent Memorial Data/Information Analysis & Visualization

VA-26-00048484

ATTN: Small Business Innovation Research Program (SBIR) Phase II Contract Holders

GENERAL INFORMATION

SET-ASIDE

NAICS CODE*

CONTRACTING OFFICE ADDRESS

POINT OF CONTACT*

541715 Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724 Contract Specialist Shreeia Curry Shreeia.Curry@va.gov

PLACE OF PERFORMANCE

ADDRESS

POSTAL CODE

COUNTRY

ADDITIONAL INFORMATION

AGENCY CONTACT’S EMAIL ADDRESS

EMAIL DESCRIPTION

DESCRIPTION

As permitted by FAR Part 10, this Sources Sought Notice (SSN) is being utilized for informational and planning purposes for Veteran Decedent Memorial Data/Information Analysis & Visualization. Your response will assist the Government in the development of its acquisition strategy for a possible Request for Quote (RFQ), to be issued on a later date.

This SSN shall not be construed as an RFQ or as any commitment or obligation on the part of the Government to issue a solicitation. No reimbursement will be made for any costs associated with providing information in response to this SSN or any follow-up information requests.

Response is strictly voluntary - it is not mandatory to submit a response to this notice to participate in any formal RFQ process that may take place in the future however, it should be noted that information gathered through this notice may significantly influence VA’s acquisition strategy.

Interested Contractors that can provide the services and/or products identified in the Performance Work Statement (PWS) shall submit a Capabilities Statement on company letterhead demonstrating the company’s qualifications to perform the defined work. Responses must be complete and sufficiently detailed to address the specific information. The information submitted shall not exceed three (3) pages. Excessive reliance on promotional brochures is discouraged. The documentation shall include, at a minimum, the following:

1. Company name and address.

1. Two points of contact (names, titles, phone numbers and email addresses).

1. UEI number and CAGE Code, as registered in the System for Award Management (SAM) at http://www.sam.gov/.

1. Small Business designation/status under NAICS 541715 (must correlate with SAM registration):

_____ SB _____ HUBZONE _____ WOSB_____ EDWOSB_____ 8(a) _____ VOSB_____ SDVOSB_____ SDB_____LARGE BUSINESS

1. Existing contract vehicles relevant to this requirement (i.e. General Services Administration, Federal Supply Schedule and/or Government Wide Acquisition Contract number (GWAC).

1. Does the draft PWS provide sufficient detail to describe the technical/functional requirements that encompass the solution products and services to be provided under this effort?

If “No”, please provide recommendations on elements of the draft PWS that may contribute to more accurate responses.

CONTACT INFORMATION AND RESPONSE DUE DATE:

Submit all responses via email to Shreeia.Curry@va.gov no later than April 7, 2026, 2:00 PM CST. Include the following in the subject line of the email: RFI Response 36C10B26Q0317_Business Name.

See embedded document below: PWS_Draft.

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Memorial Affairs – National Cemetery Administration

Veteran Decedent Memorial Data/Information Analysis & Visualization

Date: 25 Mar 26

VA-26-00048484

PWS Version Number: 1.2

Contents

BACKGROUND

The work outlined in this PWS shall be performed by a Small Business Innovation Research Program (SBIR) Phase II Contract holder by further developing, integrating, and applying the SBIR-derived approach to a new mission area and use case(s) supporting U.S. Department of Veterans Affairs (VA)/National Cemetery Administration (NCA).

NCA is one of three Administrations within VA responsible for delivering services and benefits to Veterans. Pursuant to the National Cemeteries Act of 1973 and other statutory authorities and regulations (38 U.S.C. 2306, 38 U.S.C. Chapter 24, 38 CFR Parts 38-39), NCA is responsible for providing cemetery services to Veterans and other eligible persons. NCA’s responsibilities include the operation and maintenance of 153 national cemeteries and the construction of new national cemeteries.

NCA’s mission is to honor Veterans with final resting places in national shrines and with lasting tributes that commemorate their service to our Nation. NCA provides burial space for eligible Veterans and family members; maintains graves and their environs as national shrines in perpetuity; supports state and tribal organizations through the Veterans Cemetery Grants Program; and furnishes headstones, markers, medallions, and Presidential Memorial Certificates in recognition of service to a grateful nation. NCA also administers grants for establishing or expanding state and tribal government Veterans cemeteries.

A key aspect of this project is to support NCA in the operational programming of the Riverside Education and Interpretive Center (REIC). As a natural extension of NCA’s mission, NCA is enhancing and transforming its approach to memorialization beyond foundational elements (headstones/markers/medallions and Presidential Memorial Certificates) to enable more interactive and engaging experiences with the communities in which national cemeteries are located. Beginning in 2016, NCA established the Veterans Legacy Program (VLP) to commemorate Veterans and service members through discovery and sharing of their stories, including education outreach to K-12 schools and students. In 2019, NCA launched the Veterans Legacy Memorial (VLM), an online memorial platform allowing users to interact with the memories of Veterans interred in NCA cemeteries. Establishing an education and interpretive center at Riverside National Cemetery is a logical next step in this transformational effort, and the REIC will be the first of its kind for NCA.

This effort will leverage an iterative, SBIR-informed delivery approach to produce implementation-ready products that optimize REIC stand-up and can be adapted for future NCA education and interpretive centers.

APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. “Federal Information Security Modernization Act of 2014”

2. Federal Information Processing Standards (FIPS) Publication 140-3, “Security Requirements for Cryptographic Modules”, March 22, 2019

3. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

4. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

5. FIPS Pub 201-3, “Personal Identity Verification of Federal Employees and Contractors,” January 2022

6. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended

7. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

8. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and Information Technology Act of 2006, as amended, Title IX, Information Security Matters

9. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”, as amended

10. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm

11. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm

12. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019

13. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” as amended

14. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

15. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”, as amended

16. NIST SP 800-66 Rev. 2, “Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide,” February 2024

17. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended

18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended

19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021 (see VA NOTICE 24-18, dated September 27, 2024, “Update to VA Directive 6500 Cybersecurity Program”, and VA Notice 25-07, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, and VA Notice 25-06, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023

23. VA Handbook 6500.6, “Contract Security,” March 12, 2010 (see VA Notice 24-12, dated April 22, 2024, “Update to VA Handbook 6500.6, Contract Security, Appendix C VA Information and Information System Security/Privacy Language For Inclusion Into Contracts, As Appropriate”)

24. VA Handbook 6500.8, “Information System Contingency Planning,” March 25, 2025

25. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018

26. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017

27. OIT Process Asset Library (PAL), OIT Process Asset Library.

28. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

29. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

30. VA Directive 6510, “VA Identity, Credential and Access Management,” September 3, 2024

31. VA Handbook 6510, “VA Identity, Credential and Access Management,” September 27, 2024

32. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017

33. VA Directive 6300, “Records and Information Management,” September 21, 2018

34. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

35. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

36. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

37. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015

38. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014

39. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005

40. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

41. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008

42. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov))

43. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

44. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

45. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

46. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

47. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

48. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

49. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

50. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

51. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008

52. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L. 110–140), December 19, 2007

53. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005

54. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

55. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022

56. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

57. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

58. “Veteran Focused Integration Process (VIP) Guide 4.0,” March 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

59. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

60. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

61. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

62. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

63. Social Security Number (SSN) Fraud Prevention Act of 2017

64. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018

65. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended

66. Executive Order 14028, “Executive Order on Improving the Nation's Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/

67. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.

68. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations

69. OMB M-22-18, “Enhancing the Security of the Software Supply Chain through Secure Software Development Practices,” September 14, 2022

70. OMB M-23-16, “Update to Memorandum M-22-18,” June 9, 2023

71. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021

72. NIST SP 800-88 Revision 1 “Guidelines for Media Sanitization,” December 2014

73. CISA Binding Operational Directive (BOD) 19-02: “Vulnerability Remediation Requirements of Internet-Accessible Systems,” April 29, 2019, BOD 19-02: Vulnerability Remediation Requirements for Internet-Accessible Systems | CISA

74. CISA BOD 22-01: “Reducing the Significant Risk of Known Exploited Vulnerabilities,” November 3, 2021, BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities | CISA

75. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks.” Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks | CISA

76. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical Devices/Systems, June 03, 2019

77. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

SCOPE OF WORK

The Contractor shall provide data/information-capture, data/information-analysis, data/information-visualization, programmatic planning, and implementation support to optimize the model for the Riverside Education and Interpretive Center (REIC). The Contractor’s scope includes veteran decedent data & information visualization—pertaining to stories of veterans—to inform effective operational programming of the REIC. The effort will include numerous SBIR-derived digital tools as well as a comprehensive Plan of Action & Milestones (POA&M) that identifies tasks, owners, dependencies, durations, and milestones required to optimize REIC implementation.

Work will be completed through structured data/information-capture, data/information-analysis, data/information-visualization, stakeholder engagement, capture of opportunities for REIC optimization, organizational/operational design, and production of actionable deliverables suitable to inform decision-making by NCA. The Contractor will provide project management, documentation, and implementation support as needed to align the digital infrastructure necessary to support the REIC with NCA mission objectives and Veterans Legacy education/interpretive outcomes.

PERFORMANCE DETAILS

PERFORMANCE PERIOD

The PoP shall be 12 months from date of award.

work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

There are 11 Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, five are set by date:

If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

PLACE OF PERFORMANCE

Tasks under this PWS shall predominately be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission.

Under limited circumstances (i.e data/information gathering trips, site visits, or collaboration meetings with the client), work may be performed at a government facility or alternate site with prior concurrence from the Contracting Officer’s Representative.

TRAVEL

The Government anticipates limited travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings throughout the PoP. These costs will not be reimbursed by the Government.

KEY PERSONNEL

The Contractor shall ensure that the aforementioned specific tasks and deliverables are supported with personnel with the skills to meet such tasks and the experience that meets the requirements stated below.

Key Personnel shall include a Program Manager, a Project Manager, a Program Data Analyst (1), a Program Data Analyst (2) and a REIC Programming Consultation:

1. Program Manager:

Provides oversight of the contract and is responsible for direct communication with the VA Technical Representative. The Program Manager shall have a minimum of 15 years of progressively responsible experience managing complex, multidisciplinary technical programs for federal government clients, including responsibility for program governance, cost and schedule control, technical integration, risk management, and stakeholder coordination. A Master’s degree in Geographic Information Science, Geography, Environmental Science, Engineering, or a related technical discipline is required. Specialized experience shall include leadership of data driven planning, asset and infrastructure analysis, geospatial and digital decision support systems, and oversight of professional teams delivering analytical tools, databases, and dashboards used to inform capital planning, operational prioritization, and mission support for large public institutions.

2. Program Data Analyst (1):

Works under guidance of the program manager and performs technical functions related to crowdsourcing, analysis, and visualization of data. The Data Scientist shall have a minimum of 10 years of professional experience, including experience supporting federal agencies, and shall possess a Master’s degree or higher in Statistics, Data Science, Engineering, Computer Science, or a related discipline (preferred). Specialized experience shall include advanced statistical analysis, machine learning, natural language processing, and data automation, as well as development of enterprise scale analytical models, dashboards, and data pipelines. The Data Scientist shall demonstrate experience translating complex datasets into defensible, transparent insights that support infrastructure management, asset prioritization, resource allocation, and executive level decision making.

3. Program Data Analyst (2):

Works under guidance of the above-mentioned program data analyst and performs technical functions related to crowdsourcing, analysis, and visualization of data. The Data Scientist shall have a minimum of 10 years of professional experience, including experience supporting federal agencies, and shall possess a Master’s degree or higher in Statistics, Data Science, Engineering, Computer Science, or a related discipline (preferred). Specialized experience shall include advanced statistical analysis, machine learning, natural language processing, and data automation, as well as development of enterprise scale analytical models, dashboards, and data pipelines. The Data Scientist shall demonstrate experience translating complex datasets into defensible, transparent insights that support infrastructure management, asset prioritization, resource allocation, and executive level decision making.

4. REIC Programming Consultant:

The REIC Programming Consultant will work under direction of the program manager and perform efforts associated with developing recommended visualized products to support client decision making. Additionally, the deliverables associated with Deliverable Item 0008 will be a key focus of the REIC Programming Consultant. The REIC Programming Consultant shall have a minimum of 15 years of progressively responsible experience managing complex, multidisciplinary interpretive and education programs for federal government clients, including responsibility for program governance, cost and schedule control, integration of interpretive technologies with organizational IT initiatives, risk management, and internal stakeholder coordination. A master’s degree in history, Public History, Museum Studies, History Education, Public Communication, or a related technical discipline is required. Specialized experience shall include leadership of history based interpretive planning, exhibit development, interpretive media development, public programs development, curriculum-based educational planning and program implementation for cultural resource sites, planning communication campaigns and management, historical collections management, geospatial data usage and digital technologies in interpretive programing development, and oversight of professional teams delivering design products, databases, and dashboards used to inform program development, planning, operational prioritization, and mission support for government organizations managing cultural resources

The Contractor agrees that it has a contractual obligation to mitigate the consequences of the loss of Key Personnel and shall promptly secure any necessary replacements in accordance with (IAW) this PWS section. Failure to replace Key Personnel pursuant to this clause and without a break in performance of the labor category at issue shall be considered a condition endangering contract performance and may provide grounds for termination for default.

SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform and deliver the following:

All documents and data deliverables described in this document shall be submitted on time and meet the requirements set forth in this PWS.

TASK 1: PROJECT INITIATION & MANAGEMENT

OBJECTIVE

Provide overall management, governance, and coordination for the project to ensure successful completion of the tasks and necessary requirements to capture, analyze and visualize Veteran decedent data/information; communicate observations and recommendations; and provide a roadmap for REIC “operational” implementation.

PROJECT KICKOFF MEETING

In close coordination with the Government, plan and execute a project kickoff meeting to review contract terms and conditions, deliverables, and establish project governance with respect to meetings, communication, and sharing of information.

PROJECT MANAGEMENT PLAN

Develop a Project Management Plan (PMP) focused on scope, schedule, milestones, communication protocols, and project risks. Update plan as required by the Government and maintain the PMP throughout the life of the contract.

Deliverable:

A. Project Management Plan (0001)

MEETING MATERIALS

Develop and share meeting materials electronically at least 24 hours prior to all scheduled meetings. Post meeting materials to a shared repository accessible by all stakeholders involved in the project.

Deliverable:

A. Meeting Materials (0002)

MEETING MINUTES

Develop and share meeting minutes of all planned meetings.

Deliverable:

A. Meeting Minutes (0003)

PROGRESS REPORTS

Submit monthly progress reports detailing monthly activities. The progress reports shall detail any progress made on various tasks and deliverables, as well as Government stakeholders engaged during the period in question.

Deliverable:

A. Progress Reports (0004)

Task 2: Due Diligence

OBJECTIVE

Engage with key stakeholders responsible for various programs throughout the NCA, including but not limited to the Veterans Legacy Program (VLP), Veterans Legacy Grants Program (VLGP), and Veterans Legacy Memorial (VLM) to better understand their programs and collect information.

STAKEHOLDER IDENTIFICATION

Collaborate with the Technical Representative to identify various stakeholders that will be involved with the REIC. Each stakeholder identified will include name, contact information, office, and primary responsibilities as they relate to REIC Veteran Decedent Memorial Data Analysis & Visualization.

STAKEHOLDER INTERVIEWS

Conduct a series of interviews with key stakeholders to gain information into their assigned program(s)/responsibilities. Identify key systems, databases, processes, etc. that will influence potential project outcomes.

REQUEST FOR INFORMATION

Develop an electronic request for information for each stakeholder organization detailing the various documents, websites and other forms that will be used to inform the REIC Veteran Decedent Memorial Data Analysis & Visualization. Review the RFI with the stakeholder(s) prior to finalizing and formally requesting the information.

Deliverable:

A. Requests for Information (0005)

Task 3: Information Capture

OBJECTIVE

Establish streamlined processes to capture information from internal and external stakeholders, systems and documents to support REIC Veteran Decedent Memorial Data Analysis & Visualization.

INFORMATION CAPTURE

Leverage technology developed by the Contractor under SBIR Phase II Contract No. TBD to create a crowd sourcing platform for internal stakeholders, allowing for data collection, analysis and visualization related to REIC Veteran Decedent Memorial Data Analysis & Visualization.

Deliverable:

A. SBIR-based internal information capture tool (0006)

EXTERNAL INFORMATION CAPTURE

Leverage technology developed by the Contractor under SBIR Phase II Contract No. TBD to create a crowd sourcing platform for external stakeholders. The platform will allow for data collection, analysis and visualization related to REIC Veteran Decedent Memorial Data Analysis & Visualization.

Deliverable:

A. SBIR-based external information capture tool (0007)

Task 4: POA&M Development

Objective

The Contractor shall work with stakeholders identified by the Government to develop a Plan of Action & Milestones (POA&M) that incorporates an integrated roadmap, schedule, resourcing, and risk plan for implementation of the REIC.

Integrated Schedule & Milestones

The Contractor shall develop a comprehensive plan of action for various focus areas (e.g. People, Process, Technology, etc.). Each plan of action shall include the steps necessary to successfully implement the task, along with a built-out schedule, including dependencies, and key milestones.

Deliverable:

A. POA&M (0008)

RESOURCE & BUDGET PLAN

The Contractor shall produce a resource and budget plan to accompany each plan of action. The resource and budgeting plan shall include a mix of contract and FTE labor, along with all other anticipated resource costs (e.g. equipment, facilities, etc.)

Deliverable:

A. Resourcing Workbook (0009)

RISK, ISSUES & MITIGATION PLAN

The Contractor shall produce a risk register aligned with the POA&M that highlights potential risks associated with each focus area and the proposed mitigation strategies to address those risks.

Deliverable:

A. Risk Register (0010)

GENERAL REQUIREMENTS

ENTERPRISE AND IT FRAMEWORK

VA TECHNICAL REFERENCE MODEL

The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM). Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.

ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM)

The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Architecture (EA), and VA Identity and Access Management (IAM) approved Enterprise Technology Guidelines (ETG). The Contractor shall ensure all Contractor delivered applications and systems comply with the VA Identity, Credential, and Access Management policies and guidelines set forth in Executive Order 14028, VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, CISA Binding Operational Directive 23-01, and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.

The Contractor shall ensure all Contractor delivered applications and systems provide user authentication services compliant with the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-63-3, VA Handbook 6500, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the ETGs. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.

The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of Management and Budget (OMB) Memoranda M-05-24, M-19-17, M-22-09, and NIST Federal Information Processing Standard (FIPS) 201-3. Contractor delivered applications and systems shall be on the FIPS 201 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.

The Contractor shall ensure all Contractor delivered applications and systems support:

1. Automated provisioning and are able to use enterprise provisioning service.

2. Interfacing with VA’s Master Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.

3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number [ICN]).

4. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.

5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.

6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.

7. Two-factor authentication (2FA) through an applicable Technology Guideline as outlined in VA ETG.

8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion-based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP 800-63-3 guidelines.

9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.

10. Role Based Access Control.

11. Auditing and reporting capabilities.

12. Compliance with VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.

The required Assurance Levels for this specific effort are Identity Assurance Level 3, Authenticator Assurance Level 3, and Federation Assurance Level 3.

INTERNET PROTOCOL VERSION 6 (IPv6)

The Contractor solution shall support IPv6-Only based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments. IPv6-Only technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices, applications, and systems shall support all applicable functionality on native IPv6-Only as well as dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g., web, email, DNS, ISP services, etc.) shall support native IPv6-Only and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall support using native IPv6-Only and dual stack (IPv6 / IPv4) for all functionality and operations.

TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents).

STANDARD COMPUTER CONFIGURATION

The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, Windows 11, Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to Windows 11 workstations shall be delivered as a signed .msi package with switches for silent and unattended installation and updates shall be delivered in signed .msp file formats for easy deployment using Microsoft Endpoint Configuration Manager (CM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by VA using a code signing authority such as Verizon/Cybertrust or Symantec/VeriSign. The Contractor shall also ensure and certify that their solution functions as expected when used from a standard VA computer, with non-admin, standard user rights that have been configured using the Defense Information Systems Agency (DISA) Secure Technical Implementation Guide (STIG) specific to the particular client operating system being used.

VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM)

The Contractor shall support VA efforts IAW the Veteran-Focused Integration Process (VIP) Guide and Product Line Management (PLM) Playbook. The major focus of VIP is on Enterprise Oversight, Governance, reporting, and establishing practices that focus on outcomes and continuously delivering sustainable IT capabilities to benefit the Veteran. PLM is a framework that focuses on delivering functional products that provide the highest priority work to customers while delivering simplified, reliable, and practical solutions to the business, medical staff, and our Veterans. The VIP Guide is a companion guide to the PLM Transformation Playbook and can be found at: https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 and the PLM Transformation Playbook can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946. VIP and PLM are the authoritative processes that IT projects must follow to ensure development and delivery of IT products.

The VIP Guide provides guidance for transitioning from project-centric to product-centric delivery. The VIP guide applies to all OIT Office of Management and Budget (OMB) reportable products that are required to collect and report costs, schedules, risks, and other valuable information in VA PARS (whether products are procured or developed by VA) and any VA Information Technology project effort in Software Product Management (SPM) and Infrastructure Operations (IO), or their successors, that touch the VA network regardless of IT organizational alignment (whether it spends government funding from VA's Congressional IT Appropriation or any other appropriation).

The PLM Transformation Playbook details how OIT leadership expects Product Lines (PLs) to implement PLM, DevOps, and Lean-Agile principles, methods, practices, and techniques through levels of maturity. The PLM Transformation Playbook applies to all Information Technology (IT) products aligned to PLs in the Software Product Management, Infrastructure Operations and Product Engineering organizations within the OIT organization.

Others outside the referenced groups or organizations may use the VIP Guide and PLM Transformation Playbook for situational awareness as needed.

PROCESS ASSET LIBRARY (PAL)

The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL includes a spectrum of OIT functions and activities, such as project management, operations, service delivery, communications, acquisition, and resource management. PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards and guides to assist the OIT workforce, Government and Contractor personnel. OIT utilizes PAL processes to ensure compliance with policies and regulations and to meet VA quality standards. The PAL includes the contractor onboarding process consistent with Section 6.2.2 and can be found at process_CONB_ext.docx (live.com). The main PAL can be accessed at www.va.gov/process.

AUTHORITATIVE DATA SOURCES

The VA Enterprise Architecture Repository (VEAR) is one component within the overall EA that establishes the common framework for data taxonomy for describing the data architecture used to develop, operate, and maintain enterprise applications. The Contractor shall comply with the department’s Authoritative Data Source (ADS) requirement that VA systems, services, and processes throughout the enterprise shall access VA data solely through official VA ADSs where applicable, see below. The Information Classes which compose each ADS are located in the VEAR, in the Data & Information domain. The Contractor shall ensure that all delivered applications and system solutions support:

1. Interfacing with VA’s Master Person Index (MPI) (formerly the Master Veteran Index (MVI)) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.

2. Interfacing with Capital Asset Inventory (CAI) to conduct real property record management actions, if the solution relies on real property records data. CAI is the authoritative source for VA real property record management data.

3. Interfacing with electronic Contract Management System (eCMS) for access to contract, contract line item, purchase requisition, offering vendor, and solicitation information above the micro-purchase threshold, if the solution relies on procurement data. ECMS is the authoritative source for VA procurement actions data.

4. Interfacing with HRSmart Human Resources Information System to conduct personnel action processing, on-boarding, benefits management, and compensation management, if the solution relies on personnel data. HRSmart is the authoritative source for VA personnel information data.

5. Interfacing with VA Profile to access personal contact information, if the solution relies on VA Veteran personal contact information data. VA Profile is the authoritative source for VA Veteran Personal Contact Data.

6. Interfacing with VA/Department of Defense (DoD) Identity Repository (VADIR) for determining eligibility for VA benefits under Title 38, if the solution relies on qualifying active duty military service data. VADIR is the authoritative source for qualifying active duty military service in VA.

7. Interfacing with VA Systems Inventory (VASI) to access VA systems information, if the solution relies on VA system information. VASI is the authoritative source for VA Information Technology systems.

8. Interfacing with Enterprise Mission Assurance Support Service (eMASS) to access the historical Authority to Operate (ATO) status of all VA Information Systems prior to migrating to ServiceNow Continuous Authorization and Monitoring (SNowCAM) until it is determined the migration is completed and eMASS is sunset. eMASS contains the historical Authority to Operate (ATO) status of all VA Information Systems prior to September 30, 2025, with all status provided through SNowCAM once migration is completed.

SOCIAL SECURITY NUMBER (SSN) REDUCTION

The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the ICN in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA MPI for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.

SOFTWARE AND LICENSING REQUIREMENTS

No software solutions or products are required.

GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS

If Artificial Intelligence (AI) is part of the Contractor system/solution, the Contractor shall be in compliance with E.O. 13960 and 14319, OMB Memorandums M-25-21, M-25-22, and M-26-04, and VA Directive and Handbook 6500 to support VA in trustworthy, secure, responsible, accountable, Truth Seeking, and Ideologically Neutral AI innovation.

No web-based, publicly available generative AI service has been approved for use with VA-sensitive data including, but not limited to OpenAI’s ChatGPT, Microsoft’s Copilot, Google’s Gemini, and Anthropic’s Claude. No PII, protected health information (PHI), or VA-sensitive data should be entered into these unapproved services. The entire definition of VA Sensitive Data can be found at 38 U.S.C. § 5727 (23). The Contractor shall protect VA Sensitive data from unauthorized disclosure or use, and from being used to train or improve the functionality of the vendor's commercial offerings without express permission from VA.

The Contractor shall deliver the services, technical data, configurations, models, weights, documentation or other information, including source code, developed during contract performance.