Inactive

Brand Name Wellbase Monitoring Licenses and Software VA-23-00066169 Page 14 of 33 PRODUCT DESCRIPTION (PD) TEMPLATE DEPARTMENT OF VETERANS AFFAIRS Office of Information & Technology Health Informatics... Brand Name Wellbase Monitoring Licenses and Software VA-23-00066169 Page 14 of 33 PRODUCT DESCRIPTION (PD) TEMPLATE DEPARTMENT OF VETERANS AFFAIRS Office of Information & Technology Health Informatics Health Middleware Data Management (HMDM) Brand Name Wellbase Monitoring Licenses and Software Date: February 16, 2023 VA-23-00066169 PD Version Number: 1.0 Contents 1.0 PRODUCT REQUIREMENTS 3 2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS (SECTION 508) 5 2.1 SECTION 508 INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) STANDARDS 5 2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY 6 2.3 ACCEPTANCE AND ACCEPTANCE TESTING 6 3.0 INFORMATION TECHNOLOGY USING ENERGY-EFFICIENT PRODUCTS 6 3.1 EPEAT 7 3.2 ENERGY STAR 7 3.3 FEMP 7 4.0 SHIPMENT OF HARDWARE OR EQUIPMENT 7 4.1 SPECIAL SHIPPING INSTRUCTIONS 7 4.2 NATIONAL ACQUISITIONS N/A 8 5.0 GENERAL REQUIREMENTS 8 5.1 VA TECHNICAL REFERENCE MODEL 8 5.2 SOCIAL SECURITY NUMBER (SSN) REDUCTION 8 5.3 INTERNET PROTOCOL VERSION 6 (IPV6) 9 5.4 SOFTWARE AND LICENSING REQUIREMENTS 9 5.5 POSITION/TASK RISK DESIGNATION LEVEL(S) 9 PRODUCT REQUIREMENTS The Department of Veterans Affairs (VA), Office of Information and Technology (OIT) has a requirement for Brand Name Ready Computing Wellbase Monitoring software licenses to support the 130 production servers and 73 non-production servers currently deployed throughout VA. The Wellbase Monitoring software will provide a solution for Veterans Data Integration and Federation (VDIF) Enterprise Platform (EP) that includes using the AppDynamics APM (already in use at VA) and pulling all telemetry from Amazon Web Services (AWS) CloudWatch, Solarwinds networking with Ready Computing Wellbase Monitoring collecting HealthShare telemetry for data, licensing, and application layers to provide a single pane of glass dashboard that could be leveraged by the various areas of the product team from testers, engineers, architects, scrum teams and product managers. The VDIF-EP enables the composition of a comprehensive Veteran Health Record that s interoperable across the VA enterprise as well as with external VA partners such as the Department of Defense, Social Security Administration, and Community Partners. InterSystems HealthShare underpins the VDIF-EP and implements a variety of services and standards-based APIs to collect, normalize, persist, secure, and share the Veteran medical information with authorized users. These monitors shall extract information from the Healthshare servers, Analytics servers, Access Gateway servers, and HSPI servers and populate the Dynatrace Dashboard the VA currently uses to monitor their health care systems. These monitors are available and appropriate to run on any Healthshare server. They will monitor endpoints that are not specific to any specialized functions a Healthshare server might perform. The following lists shall each be separate boxes or windows on the Dynatrace dashboard that the Wellbase monitors shall provide information and formatting for. Healtlhshare Servers- These monitors are intended to run on Healthshares servers. 1. Ensemble Error Check - graphs the number of Ensemble reported errors in the namespace since the last check of the monitor. 2. Ensemble Queue Check- graphs the number of namespace interfaces that have queued messages. This is NOT a graph of the number of messages queued. 3. Ensemble Timeout Check- graphs the number of namespace interfaces that reported an inactivity timeout since the last check of the monitor. 4. Ensemble Activity Monitor - graphs the number of messages processed by interface, the avg time taken to process all messages for that interface, and the number of messages that waited to be processed for a five minute time window. 5. Production Check- graphs Yes (0) or No (1), checking if the production (namespace) passed to the monitor is running. 6. Check Production Services - graphs the number of namespace services that are in Ok, Error, Disabled, or Inactive states. 7. Ensemble Purges and Messages - graphs the number of messages and logs currently stored in the monitored namespace. 8. Database Space - graphs the size of databases passed to the monitor and the amount of free space in the passed databases. 9. Combo Logs Dir Monitor - graphs the amount of journal space used as a percentage of the TOTAL journal space available. 10. HS Process Counters - graphs the HealthShare application processes on the server by process types CSP, Irisusr (or Cacheusr), Root owned, Running, and Total. 11. HS License Expires - graphs the number of days left before the license on the monitored HealthShare instance expires. 12. SSL Certificate Expiration graphs the number days until certificates used in Healthshare SSL/TLS configurations expire Analytics: These monitors are intended to run on servers that host an Analytics instance/namespace. 1. Analytics Batch Summary graph data related to batch performance over time 2. Analytics Patient error list - Get Patient transfer error list. The data in this list is populated when there are errors in Streamlet processing. Access Gateway: This monitor is intended to run on servers that host an Access Gateway/Router instance/namespace. 1. WGW Fetch Performance - Get Fetch Performance information. This information is used by the HealthShare Data Volume Reports concering Fetch Performance. HSPI: These monitors are intended to run on servers that host an HSPI instance/namespace. 1. HSPI Category Check Graph HSPI records by category 2. HSPI Classified Status Check - Graph Classified Status counts. Internally classified records are defined by a Link Status 3. HSPI Classified Warning Check - Graph Classified Warnings counts 4. HSPI Link Summary - This endpoint gets a summary of the number of links for each record, reports only for links greater than a threshold. 5. HSPI Name Change Summary - Graph HSPI patient record name change counts 6. HSPI Link Reason Summary - Get Classified Link Reason counts. The link reason indicates why a record pair was or was not linked together. Base Period (12 months) Description Part no. Quantity Wellbase License Production Server 130 Wellbase License Non-Production Server 73 Option Period 1 (12 months) Description Part no. Quantity Wellbase License Production Server 130 Wellbase License Non-Production Server 73 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS (SECTION 508) On January 18, 2017, the Architectural and Transportation Barriers Compliance Board (Access Board) revised and updated, in a single rulemaking, standards for electronic and information technology developed, procured, maintained, or used by Federal agencies covered by Section 508 of the Rehabilitation Act of 1973, as well as our guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act of 1934. 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. 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: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines. A printed copy of the standards will be supplied upon request. Federal agencies must comply with the updated Section 508 Standards beginning on January 18, 2018. The Final Rule as published in the Federal Register is available from the Access Board: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule. 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 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 usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software. 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. INFORMATION TECHNOLOGY USING ENERGY-EFFICIENT PRODUCTS The Contractor shall comply with Sections 524 and Sections 525 of the Energy Independence and Security Act of 2007; Section 104 of the Energy Policy Act of 2005; Executive Order 13834, Efficient Federal Operations , dated May 17, 2018; Executive Order 13221, Energy-Efficient Standby Power Devices, dated August 2, 2001; and the Federal Acquisition Regulation (FAR) to provide ENERGY STAR®, Federal Energy Management Program (FEMP) designated, low standby power, and Electronic Product Environmental Assessment Tool (EPEAT) registered products in providing information technology products and/or services. EPEAT EPEAT product compliance is not required in this acquisition. ENERGY STAR Energy Star compliance is not required in this acquisition. FEMP FEMP or FEMP low standby power product compliance is not required in this acquisition. SHIPMENT OF HARDWARE OR EQUIPMENT Inspection: Destination Acceptance: Destination Free on Board (FOB): Destination Ship To and Mark For: Primary Alternate Name: Kevin C. Via Name: Portia Vertreese Address: 1601 Brenner Ave. Salisbury, NC 28144 Address: 508 Fulton Street Durham, NC 27705 Voice: 704-953-7608 Voice: 919-917-1606 Email: kevin.via@va.gov Email: portia.vertreese@va.gov SPECIAL SHIPPING INSTRUCTIONS Prior to shipping, Contractor shall notify Site POCs, by phone followed by email, of all incoming deliveries including line-by-line details for review of requirements. The Contractor shall not make any changes to the delivery schedule at the request of Site POC. Contractors shall coordinate deliveries with Site POCs before shipment ofhardware to ensure sites have adequate storage space. All shipments, either single or multiple container deliveries, shall bear the VA IFCAP Purchase Order number on external shipping labels and associated manifests or packing lists. In the case of multiple container deliveries, a statement readable near the VA IFCAP PO number shall indicate total number of containers for the complete shipment (e.g. Package 1 of 2 ), clearly readable on manifests and external shipping labels. Packing Slips/Labels and Lists shall also include the following: IFCAP PO #: ____________ (e.g., 166-E11234 (the IFCAP PO number is located in block #20 of the SF 1449)) Project Description: (e.g. Tier I Lifecycle Refresh) Total number of Containers: Package ___ of ___. (e.g., Package 1 of 3) NATIONAL ACQUISITIONS N/A GENERAL REQUIREMENTS VA TECHNICAL REFERENCE MODEL The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. Moreover, the VA TRM, which includes the Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM. 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. INTERNET PROTOCOL VERSION 6 (IPV6) The Contractor solution shall support Internet Protocol Version 6 (IPv6) 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). IPv6 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 shall support native IPv6 and 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 and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations. 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. POSITION/TASK RISK DESIGNATION LEVEL(S) Service Task/ Item Number Tier1 / Low Risk Tier 2 / Moderate Risk Tier 4 / High Risk 1.1 The Tasks identified above and the resulting Position Sensitivity and Background Investigation requirements identify, in effect, the Background Investigation requirements for Contractor individuals, based upon the tasks the particular Contractor individual will be working. The submitted Contractor Staff Roster must indicate the required Background Investigation Level for each Contractor individual based upon the tasks the Contractor individual will be working, in accordance with their submitted proposal. POINTS OF CONTACT VA Program Manager: Name: Orlando Martinez Address: Voice: 404-606-0344 Email: orlando.martinez2@va.gov Contracting Officer s Representative: Name: Kevin Via Address: Voice: 704-953-7608 Email: kevin.via@va.gov Contracting Officer: Name: Brett Schwerin Address: 23 Christopher Way Eatontown, NJ 07724 Voice: 848-377-5053 Email: brett.schwerin@va.gov Contract Specialist: Name: Michelle Policari Address: 23 Christopher Way Eatontown, NJ 07724 Voice: 848-377-5130 Email: michelle.policari@va.gov INFORMATION SECURITY CONSIDERATIONS: The assessment and authorization (A&A) requirements do not apply and a Security Accreditation Package is not required.