Employee Recognition Service_Draft PD.pdf

PRODUCT DESCRIPTION (PD)

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration (VHA) Orlando Veterans Affairs Healthcare System (OVAHCS)

Employee Recognition Service

Date: March 30, 2026

VA-26-00052104

PD Version Number: 0.1

TAC Number: VA-26-00052104

Contents

1.0 PRODUCT REQUIREMENTS

1.1 SALIENT CHARACTERISTICS

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY

(ICT) STANDARDS

2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

2.3 ACCEPTANCE AND ACCEPTANCE TESTING

3.0 GENERAL REQUIREMENTS

3.1 VA TECHNICAL REFERENCE MODEL

3.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

3.3 SOCIAL SECURITY NUMBER (SSN) REDUCTION

3.4 INTERNET PROTOCOL VERSION 6 (IPV6)

3.5 SOFTWARE AND LICENSING REQUIREMENTS

3.6 TRUSTED INTERNET CONNECTION (TIC)

3.7 GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS

5.7.1 AI SYSTEM/LLM DEVELOPMENT AND OPERATION DOCUMENTATION

REQUIREMENTS

5.7.2 MONITORING, REPORTING, AND CORRECTIVE ACTION

5.7.3 AI MODEL UPDATES AND CHANGE DISCLOSURES

4.0 PROJECT MANAGEMENT REQUIREMENTS

9.0 INFORMATION SECURITY CONSIDERATIONS

1.0 PRODUCT REQUIREMENTS

The Contractor shall provide a Healthcare driven digital, cloud-based employee recognition platform that enables employees, patients, caregivers, and family members to recognize Orlando VA Health Care System (OVAHCS) clinical and non-clinical staff for exemplary customer care and support.

The platform shall utilize a push/pull technology approach to healthcare employee recognition by facilitating real-time feedback from patients, peers, caregivers, and family members (pull), and by delivering personalized recognition and actionable data to staff (push).

The platform shall include, at a minimum, the capability to:

• Generate detailed reports measuring patient satisfaction, patient safety, and staff recognition data.

• Capture real-time, in-the-moment patient feedback.

• Provide prioritized, real-time results and insights.

• Offer marketing and communication tools that support efforts to improve patient experience and employee engagement.

The platform shall be accessible on any Android or Apple device. The system shall support unlimited data pulls by the organization and must accommodate up to 6,648 OVAHCS employees. The Contractor shall provide technical support services sufficient to ensure full and continuous functionality of the platform for all covered users.

1.1 SALIENT CHARACTERISTICS

1. Allow Veterans and family members to digitally recognize staff members who positively impact their care journey.

2. Provide an easy-to-use, real-time interface that allows Veterans and families to submit recognition directly from mobile devices or digital access points during their visit.

3. Enable Veterans to recognize individuals who impacted their experience across clinical and non-clinical roles.

4. Support multiple languages to ensure accessibility for diverse populations.

5. Deliver positive Veteran feedback directly to staff members through a platform accessible to their peers and leadership. While screening and redacting any protected health information (PHI) in compliance with HIPAA requirements.

6. Enable real-time service recovery opportunities by privately routing any constructive feedback to relevant leaders.

7. Integrate existing recognition programs (e.g., Diseases Attacking the Immune System (DAISY) Award nominations) into a unified workflow, enabling Veterans and family members to submit nominations directly through the interface.

8. Ask configurable questions related to a Veteran’s experience with specific staff members and provide individualized Veteran experience insights to employees and leadership.

9. Enable real-time notifications to staff and leaders when recognition is received.

10. Provide resources to support awareness and adoption of the healthcare patient driven recognition program.

11. Ensure healthcare workers receive meaningful and frequent recognition by incorporating the voice of leaders, peers, Veterans, and their families.

12. Reinforce Integrity, Commitment, Advocacy, Respect, and Excellence (ICARE) values by incentivizing and promoting mission-aligned behaviors across staff.

13. Provide Veteran-to-staff, peer-to-peer, leader-to-staff, and leader-to-team recognition capabilities.

14. Enhance employee engagement by highlighting the impact of staff contributions through Healthcare patient driven recognition.

15. Support employee celebrations including service anniversaries, new hires, milestones, and other culture-building events.

16. Provide an internal social engagement environment that allows patient-driven stories, positive experiences, and communication to be shared between individuals, teams, groups, departments, and across the organization.

17. Enable leadership to communicate organizational priorities through digital communication tools within the platform.

18. Provide opportunities to highlight positive care experiences across departments and service lines.

19. Provide interactive challenges that promote teamwork, patient experience, quality, safety, and positive workplace behaviors.

20. Provide platform user interface design with branding customization and data insights to drive organization improvements

21. Provide real-time reporting and analytics to identify trends related to Veteran experience, staff engagement, and recognition activity.

22. Deliver platform insights directly to leaders to surface areas of strength and share opportunities on how to make the biggest impact on your team

23. Support data access and reporting capabilities to inform leadership decision making.

24. Provide Software-as-a-Service based interactive software hosted in a secure cloud environment.

25. Support access across Android and iOS devices.

26. Include a companion mobile application.

27. Provide Single Sign-On integration with existing authentication and HR systems.

28. Support at least 6,648 users and provide technical support.

29. Provide ongoing technical support and system administration assistance.

30. The Contractor shall implement an Information Security Management

System (ISMS), that adheres to ISO27001 and HIPAA.

31. The Contractor shall be SOC 2 Type II certified.

32. Maintain an information security policy that complies with applicable regulatory and business requirements. This policy must protect all sensitive and confidential data stored, accessed, or transmitted by the software platform, including applications, components, infrastructure, and underlying code.

33. The Contractor shall have a risk assessment program to assess the organization’s enterprise-level risk at least annually, or upon significant changes to the environment.

34. Require employees with access to sensitive information to sign confidentiality agreements prohibiting unauthorized disclosure of system data

35. The Contractor shall have a comprehensive security awareness training program that is fully implemented. A core set of security training, including HIPAA, for all employees onboarding. The training program also includes monthly updates of latest security threats;

annual review of core security training; and team-specific training, as defined by security team.

36. Strict control access to restrict private information to privileged users.

These users are required to abide by their assigned responsibilities related to their elevated access.

37. Data handling, retention, and disposal program to manage information in accordance with applicable laws, regulations, policies, and standards. This program establishes a formal data retention schedule and implements a data classification standard to ensure the confidential data is secured.

38. Retains sensitive and confidential data only for as long as necessary to fulfill its purposes unless otherwise required by law or to meet legal and client contractual obligations.

39. Network segmentation to prevent direct or unauthorized connections between an external network and its information systems, in particular confidential data in cloud environments.

40. A vulnerability management program to ensure the confidentiality, integrity, and availability (CIA) of the organization’s information systems landscape, which includes all critical system resources. The program includes internal and external scans, penetration testing, and issue remediation for the purposes of identifying, detecting, classifying, prioritizing, remediating, validating, and continuously monitoring vulnerabilities.

41. Independent third-party penetration tests at least annually on any systems with Confidential data or with a critical risk rating to identify security vulnerabilities.

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

On January 18, 2017, the Access Board issued a final rule that updated accessibility requirements covered by Section 508 and refreshed guidelines for telecommunications equipment subject to Section 255 of the Communications Act. The final rule went into effect on January 18, 2018. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

2.1 SECTION 508 – INFORMATION AND COMMUNICATION

TECHNOLOGY (ICT) STANDARDS

The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT. These standards are found in their entirety at: Revised 508 Standards and 255 Guidelines (access-board.gov). A single PDF file version of the Revised Section 508 Standards and 255 Guidelines will be supplied upon request, or can be obtained from the Access Board website. Federal agencies must comply with the Rehabilitation Act of 1973, as amended.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

☒ E205 Electronic Content – (Accessibility Standard -WCAG 2.0 Level A and AA Guidelines)

☒ E204 Functional Performance Criteria ☒ E206 Hardware Requirements ☒ E207 Software Requirements ☒ E208 Support Documentation and Services Requirements

2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and https://www.access-board.gov/ict/ https://www.access-board.gov/ict/ usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

2.3 ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery. The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

If the government determines that Section 508 conformance claims provided by the offeror represent an inaccurate level of conformance than what is actually delivered to the agency, the government shall, at its option, require the offeror to remediate the delivered item to align with the required Section 508 conformance claims prior to acceptance.

3.0 GENERAL REQUIREMENTS

3.1 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.

3.2 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 https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

VA Critical Controls after implementation will result in VA discontinuing the use of the system.

3.3 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 Integrated Control Number (ICN) in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA Master Person Index (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.

3.4 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.

https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119

3.5 SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

3.6 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.)

3.7 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. Only VA-hosted instances of generative AI services may be approved for use with VA-sensitive data.

The Contractor shall deliver the services, technical data, configurations, models, weights, documentation or other information, including source code, developed during contract performance. The Contractor, in collaboration with VA, must evaluate the output of any AI tool for accuracy prior to using the output in VA efforts. All data, including models, weights, algorithms, and outputs generated using either Government-furnished data or data first developed under this https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf https://www.cisa.gov/publication/tic-30-core-guidance-documents contract shall be the property of the Government with unlimited rights as defined by FAR 52.227-14. The Contractor shall also deliver any custom-developed code developed with AI methodologies in accordance with the SHARE IT Act, if applicable. VA shall also retain unlimited rights to any improvements to that data, including the continued design, development, testing, and operation of AI systems and/or systems utilizing AI.

The Contractor shall ensure that all AI Systems, including Large Language Models (LLM), whether standalone LLMs or integrated into broader software platforms, procured under this effort and/or used in performance of this contract complies with the Unbiased AI Principles as defined in Executive Order 14319 and OMB Memorandum M-26-04, e.g. Truth Seeking and Ideologically Neutral, as applicable to the intended use of the system.

The Contractor shall ensure that AI System/LLM generated outputs are truthful in responding to user prompts seeking factual information or analysis, prioritize historical accuracy, scientific inquiry, and objectivity, as well as acknowledge uncertainty where reliable information is incomplete or contradictory and do not fabricate, hallucinate, or present unverifiable information as fact.

The Contractor shall ensure that LLMs and AI outputs are neutral, nonpartisan tools that do not manipulate responses in favor of ideological dogmas such as Diversity, Equity, and Inclusion (DEI). The Contractor shall ensure that the LLMs, including the AI System, are not intentionally encoded with partisan or ideological judgments within an AI System’s/LLM’s outputs unless those judgments are prompted by or otherwise readily accessible to the end user.

Compliance with the AI requirements of this contract, including adherence to the Unbiased AI Principles, Truth-Seeking and Ideological Neutrality requirements, disclosure obligations, monitoring and reporting requirements, and corrective action responsibilities, is a material condition of eligibility for payment and continued performance. In accordance with OMB Memorandum M-26-04, failure to comply with these requirements, or refusal to take timely and appropriate corrective action to remedy identified noncompliance, may constitute a material breach of contract and may result in remedies consistent with the terms of the contract and applicable law including but not limited to withholding of payment, termination for cause/default, or other appropriate contractual remedies, as determined by the Contracting Officer.

All AI for delivery and/or use in performance of the contract shall adhere to the VA Trustworthy AI Framework, available at https://department.va.gov/ai/trustworthy/. Once the Contractor has obtained CO authorization to use specific AI in contract performance, the Contractor shall provide the COR a signed Statement of Attestation prior to AI implementation as identified in the Artificial Intelligence in VA Contracts clause, to include its associated list of AI being used in contract performance.

https://department.va.gov/ai/trustworthy/

Deliverable:

A. Statement of Attestation

5.7.1 AI SYSTEM/LLM DEVELOPMENT AND OPERATION

DOCUMENTATION REQUIREMENTS

To enable Government continued assessment of compliance with Trustworthy AI requirements and both Unbiased AI Principles, Truth-seeking and Ideological Neutrality, in accordance with OMB M-26-04, the Contractor shall provide AI System/LLM Development and Operation Documentation Package to include, at a minimum:

1. Acceptable Use Policy The Contractor shall provide an Acceptable Use Policy document governing its AI operation that characterizes and differentiates appropriate and inappropriate use of their product offering.

2. Model Cards, System Cards and/or Data Cards The Contractor shall provide documentation describing essential information about the model, system, and or data as it relates to the AI/LLM product offering. The documentation shall address summaries of training process, identified risks and mitigations, and model evaluation scores on LLM benchmarks at a minimum, where appropriate.

3. End User Resources The Contractor shall provide documentation to include product tutorials, developer guides, and/or other tools to assist VA in ensuring proper use of the AI/LLM to maximize utility.

4. Mechanism for End User Feedback The Contractor shall provide documentation describing the mechanism employed to provide feedback to the Offeror on outputs identified that violate the Unbiased AI Principles. This may be satisfied by a general inbox, specific Point of Contact, or similar feedback mechanism.

5. Pre-Training and Post-Training Activities of the AI System/LLM

The Contractor shall provide documentation of Pre-Training and Post Training Activity that provides details on:

a. Actions taken that impact the factuality and grounding of AI System/LLM outputs

b. System-level prompts that provide natural language instructions to the model specifying guidelines on responding to user-generated queries, to include how a model responds when reliable information is incomplete, contradictory, or subject to individual interpretation

c. The type of outputs restricted via content moderation and safety filters

d. The use of red teaming as a means of continuously assessing the model to protect against incidents of bias in generated output.

e. Training or development, if any, that occurred outside the United States, to include the type of activity and the country in which it occurred.

f. Any modifications or configurations undertaken to comply with any regulation from a government other than the U.S. Federal Government.

6. Model Evaluation Results and Methodologies The Contractor shall provide documentation describing the Evaluation Results of bias evaluations conducted by the Vendor to include the methodology for performing such tests (e.g., testing prompt pairs for politically oriented topics).

The documentation shall also include Benchmark scoring results measuring the model’s bias, helpfulness, honesty, or accuracy when provided with ambiguous versus straightforward questions. (Including any benchmarks comparing performance across multiple languages, where applicable).

7. Description of Enterprise-Level Controls The Contractor shall provide documentation describing the Enterprise Governance tools and controls, such as:

a. Customizable system instructions that are additive to a base model’s system prompts or content generation filters.

b. Product features that require a model to cite sources of its outputs or otherwise provide visibility into the provenance of the model’s outputs.

c. AI System/LLM model evaluation tools that enable comparisons either between a model’s outputs, or across various models.

8. Third Party Modification Disclosure The Contractor shall disclose of any additional controls to modify an AI Model’s/LLM’s output applied by the Contractor if the Contractor is not a direct developer of the LLM (e.g., classifiers, system prompts, fine-tuning, content moderation and filters, etc.)

Deliverable:

A. AI System/LLM Development and Operation Documentation Package

5.7.2 MONITORING, REPORTING, AND CORRECTIVE ACTION

The Contractor shall develop and implement a Compliance Monitoring and Reporting Plan supporting ongoing monitoring processes to evaluate AI outputs for compliance with Trustworthy AI and Unbiased AI principles. This plan shall include the mechanism for authorized users to provide end user feedback to report suspected violations of Truth-Seeking or Ideological Neutrality requirements.

The Contractor shall notify the COR within 10 business days of identifying any material deviation from these principles and shall submit a written Corrective Action Plan describing mitigation steps, responsible parties, and timelines.

Any material deviation, corrective action taken, and results shall be detailed in the Monthly Progress Reports.

Deliverable:

A. Compliance Monitoring and Reporting Plan B. Corrective Action Plan

5.7.3 AI MODEL UPDATES AND CHANGE DISCLOSURES

The Contractor, in an AI Model/LLM Change Disclosure, shall notify the Government throughout the PoP in advance of any material changes to AI models, including new AI enhancements, features and/or components, controls, retraining, classifiers, system prompts, fine-tuning, content moderation, filters, version replacement, or architectural changes, that could reasonably affect compliance with Trustworthy AI or Unbiased AI principles.

Updated documentation shall be provided to VA for VA approval prior to implementation of such changes.

Deliverable:

A. AI Model/LLM Change Disclosure

4.0 PROJECT MANAGEMENT REQUIREMENTS

1) A project Kick-off call shall be conducted within 14 calendar days of the contract award, as scheduled by OVAHCS and Contractor representatives.

2) Installation shall be performed Monday – Friday 08:00 a.m. – 4:00 p.m. Eastern Standard Time (EST).

3) Commissioning and training shall be done Monday – Friday 08:00 a.m. – 4:00 p.m. EST

4) Weekend Hours: To be determined (TBD) as needed (8:00 AM to 4:30 PM). Must Notify VA Point of Contact (POC) two (2) weeks prior.

5) The government-recognized US holidays are listed below. If a holiday falls on Sunday, it is observed on Monday.

Holiday Date Month New Year’s Day 1st January

Martin Luther King Jr.’s

3rd Monday January President’s Day 3rd Monday February

Memorial Day Last Monday May

Juneteenth 19th June Independence Day 4th July

Labor Day 1st Monday September Columbus Day 2nd Monday October Veterans Day 11th November

Thanksgiving Day 4th Thursday November Christmas Day 25th December

5.0 POINTS OF CONTACT

VA Program Manager:

Name: Greg Merrill Voice: 407-844-8823 Email: Gregory.Merrill@va.gov

Contracting Officer’s Representative:

Name: John Vohs Voice: 321-689-7011 Email: John.Vohs@va.gov

Contracting Officer:

Name: Mina Awad Email: mina.awad@va.gov

Contract Specialist:

Name: Allison Fulton Email: Allison.Fulton@va.gov

6.0 INFORMATION SECURITY CONSIDERATIONS

All VA sensitive information shall be protected at all times in accordance with local security field office System Security Plans and Authority to Operate for all systems/LAN’s accessed while performing the tasks detailed in this Product Description.

mailto:Gregory.Merrill@va.gov mailto:John.Vohs@va.gov mailto:mina.awad@va.gov