Attachment B - Atlanta VAMC MFD Specifications.xlsx
XLSX spreadsheet 26 KB Posted
- Attached to
- W074--Multifunction Device Lease and Support Services Atlanta VA Medical Center (VA-26 00053801)
- Solicitation number
- 36C10B26Q0331
About this file
This is a technical specifications document for multifunction device (MFD) equipment required by the Atlanta Veterans Affairs Medical Center (VAMC). The solicitation covers ten MFDs across three categories: small monochrome (Devices #5-6), medium monochrome and color (Devices #1-4), and production-level monochrome and color (Devices #7-10). All devices must support Microsoft Windows 8, 10, and current operating systems with OEM driver support within six months of OS release, feature gigabit ethernet and 802.11a/b/g/n wireless connectivity, and comply with EPEAT Bronze or higher and Energy Star certifications with Section 508 accessibility standards.
The specifications emphasize comprehensive security requirements including secure boot/BIOS integrity checks, whitelisting capabilities, runtime malware detection with automatic isolation, FIPS 140-2 compliance, configurable SNMP community strings, strong password requirements (minimum 10 alphanumeric characters), HTTPS capabilities with redirect functionality, and PIV/CAC card reader integration (FIPS 201 compliant with SHA 256). All devices must provide secure PIV-authenticated printing for VistA, Cerner Millennium MHR, and Windows applications with audit trail tracking of username, job name, and timestamp. The contract requires a Secure Network Fax/Communications Service (SNFCS) solution deployed on-premise behind the VA firewall with primary and disaster recovery virtual servers (48 channels each), supporting encrypted scanning via HTTPS/SFTP with AES, RC4, or SHA-256 encryption, LDAP authentication, Active Directory synchronization, secure fax address book functionality with role-based filtering, and alert notification capabilities via phone, fax, email, and text messaging with voice conversion and survey functionality. OEM must provide all remote centralized management licenses, on-site installation and training, 24/7 technical support, and maintain hardware/software supportability for a minimum of five years post-delivery, including consumables, spare parts, and firmware updates. The device specifications vary by class with speed ranges from 45 to 125 pages per minute, paper capacity from 1,200 to 5,950 sheets, and scanning speeds up to 200 images per minute for production models.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10B26Q0331_2.docx | DOCX document | |
| Attachment A - Multifunctional Devices.docx | DOCX document | |
| S02_36C10B26Q0331_4.28.26_Final_v2.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
MFD Printers
| MINIMUM REQUIREMENT | MFD-Small Monochrome (Device #5) | Device/Part# | MFD - Small Monochrome (Device #6) | Device/Part# | MFD - Medium Monochrome (Device #1) | Device/Part# | MFD - Medium Color (Device #2) | Device/Part# | MFD - Medium Monochrome (Device #3) | Device/Part# | MFD - Medium Monochrome (Device #4) | Device/Part# | MFD - PRODUCTION Monochrome | ||||
| (Device #8) | Device/Part# | MFD - PRODUCTION Monochrome | |||||||||||||||
| (Device #9) | Device/Part# | MFD - PRODUCTION Color (Device #7) | Device/Part# | MFD - PRODUCTION Color | |||||||||||||
| (Device # 10) | Device/Part# | ||||||||||||||||
| Power Source | 120V/60Hz/12A; National Electrical Manufacturers Association (NEMA) 5-15 P. | 120V/60Hz/12A; NEMA 5-15 P. | 120V/60Hz/12A; NEMA 5-15 P. | 120V/60Hz/12A; NEMA 5-15 P. | 208-240V/60Hz/15A; NEMA 6-15R. | 208-240V/60Hz/15A; NEMA 6-15R. | 110V/60Hz/20A; NEMA 5-20 P. | 208-240V/60Hz/20A; NEMA 6-20R. | |||||||||
| Paper Capability | 1,200 sheet capacity. | 1,200 sheet capacity. | 3,140 sheet capacity. | 3,140 sheet capacity. | 3,140 sheet capacity. | 3,140 sheet capacity. | 5 Drawers/trays: 2 x 550; 1 x 1100; 1 x 1600 and 1 x 250 sheets. | 5 Drawers/trays: 2 x 550; 1 x 1100; 1 x 1600 and 1 x 250 sheets. 2,000 sheet oversized capacity feeder up to 13x19.2 sized media, up to 100 cover stock. | 5 Drawers/trays: minimum 2 x 500; 1 x 870; 1 x 1140 and 1 x 2000 sheets. 2,000 sheet oversized capacity feeder up to 13x19.2 sized media. | 4 Drawers/trays: 3 x 550; 1 x 1140 and 1 x 2000 sheets. 2,000 sheet oversized capacity feeder up to 13x19.2 sized media. | |||||||
| Paper Size | Up to 8.5"x14". | Up to 8.5”x14”. | Up to 11" x 17". | Up to 11" x 17". | Up to 11" x 17". | Up to 11" x 17". | Up to 13" x 19.2". | Up to 13" x 19.2" | Up to 13" x 19". | Up to 13" x 26". | |||||||
| Paper Tray(s) | 2 x 500 sheet paper trays not including the multipurpose tray. | 2 x 500 sheet paper trays not including the multipurpose tray. | 3 Drawers/trays (not including multi-purpose tray). | 3 Drawers/trays (not including multi-purpose tray), 500 sheet trays. | 3 Drawers/trays, 500 sheet trays (not including multi-purpose tray). | 3 Drawers/trays, (not including multi-purpose tray). | 5 Drawers/trays | 5 Drawers/trays. | 5 Drawers/trays. | 4 Drawers/trays. | |||||||
| Paper Weight (paper trays) | Must be capable of handling the entire range of 60-120 gsm for paper tray feeding. | Must be capable of handling the entire range of 60-120 gsm for paper tray feeding. | Must be capable of handling the entire range of 60-120 gsm for paper tray feeding. | Must be capable of handling the entire range of 60-120 gsm for paper tray feeding. | Must be capable of handling the entire range of 60-120 gsm for paper tray feeding. | Must be capable of handling the entire range of 60-120 gsm for paper tray feeding. | Must be capable of handling the entire range of 60-200 gsm for paper tray feeding. Manual feed must be able of handling heavy duty card stock, up to 110 lbs without damage to card stock. | Must be capable of handling the entire range of 60-200 gsm for paper tray feeding. Manual feed must be able of handling heavy duty card stock, up to 110 lbs without damage to card stock. | Must be capable of handling the entire range of 60-300 gsm for paper tray feeding. | Must be capable of handling the entire range of 60-300 gsm for paper tray feeding. Manual feed must be able of handling heavy duty card stock, 110 lbs/350 gsm without damage to card stock. | |||||||
| Operating Systems Supported | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | Microsoft Windows 8, 10, and current versions of operating systems for Microsoft and Apple. MFD manufacturer (OEM) will supply a driver for the Operating system within 6 months of realease from either Microsoft or Apple. MFD shall be capable of interfacing with upgraded Microsoft or Apple software to include print drivers during the life of maintenance support | |||||||
| Memory | 1 Gb minimum, All Memory Preinstalled prior to shipment by Factory | 1 Gb minimum, All Memory Preinstalled prior to shipment by Factory | 1 Gb minimum, All Memory Preinstalled prior to shipment by Factory | 1 Gb minimum, upgradeable up to 2.0 Gb - All Memory Preinstalled prior to shipment by Factory | 1 Gb minimum, All Memory Preinstalled prior to shipment by Factory | 1 Gb minimum, upgradeable up to 2.0 Gb - All Memory Preinstalled prior to shipment by Factory | 2 Gb minimum - All Memory Preinstalled prior to shipment by Factory | 2 Gb minimum - All Memory Preinstalled prior to shipment by Factory | 2 Gb minimum - All Memory Preinstalled prior to shipment by Factory | 2 Gb minimum - All Memory Preinstalled prior to shipment by Factory | |||||||
| Data Storage (HDD or SSD) | Minimum 250 GB | Minimum 250 GB | Minimum 250 GB | Minimum 250 GB | Minimum 250 GB | Minimum 80 GB | Minimum 80 GB | ||||||||||
| Network Connectivity | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | Gigabit Ethernet. 802.11a/b/g/n | |||||||
| Network Protocols | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | TCP/IP, IPv4, IPv6, Web Services Printing, IPP 2.0, SNMPv3, TLS 1.2 or greater version, (support must be provided within 6 months of release), HTTPS | |||||||
| Product Criteria | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | EPEAT Bronze or higher, Energy Star,(certification/reference link required), Section 508 | |||||||
| Device Security | Device must have secure boot or secure BIOS technologies that perform integrity checks immediately upon power on and prior to normal operation. If anomalies or unexpected changes in the chain of trust are detected, a reboot and restore to a "last known good" condition should occur.; Whitelisting capabilities, at a minimum check for and validate digital signature prior to upgrade/installation of firmware and/or embedded solution(s). If anomalies or unexpected changes in chain of trust on firmware and/or embedded solution(s) during upgrade/install or during normal boot process are detected, the device should be designed to audit/report the event, and reboot to a "last known good" condition.; Devices will have continuous runtime validation/integrity technology designed to prevent/detect malware intrusion or the execution of arbitrary code. In the event that malware or an attempt to run untrusted code is detected, the device shall be designed to prevent compromise of the network or other network assets by immediately shutting down all inbound/outbound connections and isolating itself, audit the event, and reboot to a "last known good" condition.; The device should have the capability to blacklist or block external network connections which disable the network connection, report/audit event, and automatically trigger a reboot to a "last known good" condition. | Device must have secure boot or secure BIOS technologies that perform integrity checks immediately upon power on and prior to normal operation. If anomalies or unexpected changes in the chain of trust are detected, a reboot and restore to a "last known good" condition should occur.; Whitelisting capabilities, at a minimum check for and validate digital signature prior to upgrade/installation of firmware and/or embedded solution(s). If anomalies or unexpected changes in chain of trust on firmware and/or embedded solution(s) during upgrade/install or during normal boot process are detected, the device should be designed to audit/report the event, and reboot to a "last known good" condition.; Devices will have continuous runtime validation/integrity technology designed to prevent/detect malware intrusion or the execution of arbitrary code. In the event that malware or an attempt to run untrusted code is detected, the device shall be designed to prevent compromise of the network or other network assets by immediately shutting down all inbound/outbound connections and isolating itself, audit the event, and reboot to a "last known good" condition.; The device should have the capability to blacklist or block external network connections which disable the network connection, report/audit event, and automatically trigger a reboot to a "last known good" condition. | Device must have secure boot or secure BIOS technologies that perform integrity checks immediately upon power on and prior to normal operation. If anomalies or unexpected changes in the chain of trust are detected, a reboot and restore to a "last known good" condition should occur.; Whitelisting capabilities, at a minimum check for and validate digital signature prior to upgrade/installation of firmware and/or embedded solution(s). If anomalies or unexpected changes in chain of trust on firmware and/or embedded solution(s) during upgrade/install or during normal boot process are detected, the device should be designed to audit/report the event, and reboot to a "last known good" condition.; Devices will have continuous runtime validation/integrity technology designed to prevent/detect malware intrusion or the execution of arbitrary code. In the event that malware or an attempt to run untrusted code is detected, the device shall be designed to prevent compromise of the network or other network assets by immediately shutting down all inbound/outbound connections and isolating itself, audit the event, and reboot to a "last known good" condition.; The device should have the capability to blacklist or block external network connections which disable the network connection, report/audit event, and automatically trigger a reboot to a "last known good" condition. | Device must have secure boot or secure BIOS technologies that perform integrity checks immediately upon power on and prior to normal operation. If anomalies or unexpected changes in the chain of trust are detected, a reboot and restore to a "last known good" condition should occur.; Whitelisting capabilities, at a minimum check for and validate digital signature prior to upgrade/installation of firmware and/or embedded solution(s). If anomalies or unexpected changes in chain of trust on firmware and/or embedded solution(s) during upgrade/install or during normal boot process are detected, the device should be designed to audit/report the event, and reboot to a "last known good" condition.; Devices will have continuous runtime validation/integrity technology designed to prevent/detect malware intrusion or the execution of arbitrary code. In the event that malware or an attempt to run untrusted code is detected, the device shall be designed to prevent compromise of the network or other network assets by immediately shutting down all inbound/outbound connections and isolating itself, audit the event, and reboot to a "last known good" condition.; The device should have the capability to blacklist or block external network connections which disable the network connection, report/audit event, and automatically trigger a reboot to a "last known good" condition. | Device must have secure boot or secure BIOS technologies that perform integrity checks immediately upon power on and prior to normal operation. If anomalies or unexpected changes in the chain of trust are detected, a reboot and restore to a "last known good" condition should occur.; Whitelisting capabilities, at a minimum check for and validate digital signature prior to upgrade/installation of firmware and/or embedded solution(s). If anomalies or unexpected changes in chain of trust on firmware and/or embedded solution(s) during upgrade/install or during normal boot process are detected, the device should be designed to audit/report the event, and reboot to a "last known good" condition.; Devices will have continuous runtime validation/integrity technology designed to prevent/detect malware intrusion or the execution of arbitrary code. In the event that malware or an attempt to run untrusted code is detected, the device shall be designed to prevent compromise of the network or other network assets by immediately shutting down all inbound/outbound connections and isolating itself, audit the event, and reboot to a "last known good" condition.; The device should have the capability to blacklist or block external network connections which disable the network connection, report/audit event, and automatically trigger a reboot to a "last known good" condition. | Device must have secure boot or secure BIOS technologies that perform integrity checks immediately upon power on and prior to normal operation. If anomalies or unexpected changes in the chain of trust are detected, a reboot and restore to a "last known good" condition should occur.; Whitelisting capabilities, at a minimum check for and validate digital signature prior to upgrade/installation of firmware and/or embedded solution(s). If anomalies or unexpected changes in chain of trust on firmware and/or embedded solution(s) during upgrade/install or during normal boot process are detected, the device should be designed to audit/report the event, and reboot to a "last known good" condition.; Devices will have continuous runtime validation/integrity technology designed to prevent/detect malware intrusion or the execution of arbitrary code. In the event that malware or an attempt to run untrusted code is detected, the device shall be designed to prevent compromise of the network or other network assets by immediately shutting down all inbound/outbound connections and isolating itself, audit the event, and reboot to a "last known good" condition.; The device should have the capability to blacklist or block external network connections which disable the network connection, report/audit event, and automatically trigger a reboot to a "last known good" condition. | N/A | N/A | N/A | N/A | |||||||
| No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | |||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | ||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | ||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | ||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | ||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | ||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | ||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | ||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. | ||||||||||||||||
| Device shall be FIPS 140-2 compliant. | No external resource connections may be made automatically without prior approval.; These features must be capable of being disabled FTP, Telnet, MDNS, image buffer, all versions of wireless, Wi-Fi Direct, and Bluetooth. OEM specific managment ports and software (if applicable) and other vendor proprietary ports must be disabled by default. Must have configurable SNMP community strings that can be changed from public to a unique value. Must be capable of strong passwords, minimum of 10 characters to include alphanumeric and special characters. Device must have HTTPS capabilities and should possess the ability to enable HTTPS redirect which forces all HTTP network connections to and from the device to utilize HTTPS. |
Device shall be FIPS 140-2 compliant.
| Device Remediation | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. | All licenses required for "remote centralized management" will be provided with the total cost of the printer. Printers must be capable of remote (batched) configuration, firmware upgrades, and management within VA deployed vendor applications. |
| Page Description Languages | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint. | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint. | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint. | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint. | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint. | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint. | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint. | Minimum supported: PCL5c, PCL6, PostScript3, native PDF printing (v1.7), Apple AirPrint. |
| Security Hardening | MFD hardening instructions, in accordance with current Defense Information Systems Agency (DISA) STIG must be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick Off Meeting. | MFD hardening instructions, in accordance with current DISA STIG must be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick Off Meeting. | The Contractor shall provide instructions on how to configure the unit to meet the current DISA STIG requirements. The instructions shall be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick-Off Meeting. | The Contractor shall provide instructions on how to configure the unit to meet the current DISA STIG requirements. The instructions shall be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick-Off Meeting. | The Contractor shall provide instructions on how to configure the unit to meet the current DISA STIG requirements. The instructions shall be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick-Off Meeting. | The Contractor shall provide instructions on how to configure the unit to meet the current DISA STIG requirements. The instructions shall be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick-Off Meeting. | The Contractor shall provide instructions on how to configure the unit to meet the current DISA STIG requirements. The instructions shall be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick-Off Meeting | The Contractor shall provide instructions on how to configure the unit to meet the current DISA STIG requirements. The instructions shall be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick-Off Meeting | The Contractor shall provide instructions on how to configure the unit to meet the current DISA STIG requirements. The instructions shall be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick-Off Meeting | The Contractor shall provide instructions on how to configure the unit to meet the current DISA STIG requirements. The instructions shall be forwarded to the assigned VA Technology Manager within 2 weeks after the Kick-Off Meeting |
| 508 Compliance/TAA Compliance | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint | MFD compliance with section 508 of the rehabilitation act of 1973. http://www.section508.gov and shall be TAA complaint |
| User/Graphical Interface | Minimum 5-inch color touch screen. | Minimum 5 inch color touch screen. | Minimum 108 inch color touch screen. | Minimum 108 inch color touch screen. | Minimum 10 inch color touch screen. | Minimum 10 inch color touch screen. | Minimum 10 inch color touch screen. | Minimum 10 inch color touch screen. | ||
| MFD Command Language | MFD commands shall be in English language. | MFD commands shall be in English language. | MFD commands shall be in English language. | MFD commands shall be in English language. | MFD commands shall be in English language. | MFD commands shall be in English language. | MFD commands shall be in English language. | MFD commands shall be in English language. | MFD commands shall be in English language. | MFD commands shall be in English language. |
| PIV Enabled | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. | Configurable to all MFD capabilities utilizing Active Directory (AD) and Public Key Infrastructure (PKI) certificates. Device must be PIV/CAC enabled and include a PIV/CAC reader that is FIPS 201 compliant with SHA 256. |
| Secure Print Capability | Offeror shall provide secure, PIV printing for both Veterans Health Information Systems & Technology Architecture (VistA), Cerner Millenium Military Health Record (MHR) and Microsoft print jobs: 1. In addition to receiving and processing normal print and scan jobs, an MFD on the network shall be able to receive any user-initiated secure print jobs via PIV Authentication (VistA terminal emulation, CPRS, Cerner Millenium (MHR), and other Windows applications print jobs) from workstations and allow only the specified user to view, or delete only their print jobs from the MFD. Unclaimed print jobs must be deleted by the system at configurable time intervals. 2. An MFD shall be able to capture the print job user metadata to associate the print job with the authenticated user at the output device. The MFD will not show other user’s jobs sitting in the queue. Only the authenticated user’s job will be shown as not to present a security vulnerability target. 3. The Contractor shall provide a PIV enabled secure print feature that allows users to retrieve printouts securely, using their PIV credentials. 4. The MFD shall be capable of allowing the user to authenticate at the MFD with PIV to release the held print job(s). 5. For auditing purposes, an MFD shall track username, print job name, and date/time stamp for all print jobs. 6. MFD shall support secure print release via use of VA supported PIV card and NT credentials entered on a key board. All licensing for this solution must be included in the cost of the device. | |||||||||
| Offeror shall provide secure, PIV printing for both Veterans Health Information Systems & Technology Architecture (VistA), Cerner Millenium Military Health Record (MHR) and Microsoft print jobs: 1. In addition to receiving and processing normal print and scan jobs, an MFD on the network shall be able to receive any user-initiated secure print jobs via PIV Authentication (VistA terminal emulation, CPRS, Cerner Millenium (MHR), and other Windows applications print jobs) from workstations and allow only the specified user to view, or delete only their print jobs from the MFD. Unclaimed print jobs must be deleted by the system at configurable time intervals. 2. An MFD shall be able to capture the print job user metadata to associate the print job with the authenticated user at the output device. The MFD will not show other user’s jobs sitting in the queue. Only the authenticated user’s job will be shown as not to present a security vulnerability target. 3. The Contractor shall provide a PIV enabled secure print feature that allows users to retrieve printouts securely, using their PIV credentials. 4. The MFD shall be capable of allowing the user to authenticate at the MFD with PIV to release the held print job(s). 5. For auditing purposes, an MFD shall track username, print job name, and date/time stamp for all print jobs. 6. MFD shall support secure print release via use of VA supported PIV card and NT credentials entered on a key board. All licensing for this solution must be included in the cost of the device. | ||||||||||
| Offeror shall provide secure, PIV printing for both Veterans Health Information Systems & Technology Architecture (VistA), Cerner Millenium Military Health Record (MHR) and Microsoft print jobs: 1. In addition to receiving and processing normal print and scan jobs, an MFD on the network shall be able to receive any user-initiated secure print jobs via PIV Authentication (VistA terminal emulation, CPRS, Cerner Millenium (MHR), and other Windows applications print jobs) from workstations and allow only the specified user to view, or delete only their print jobs from the MFD. Unclaimed print jobs must be deleted by the system at configurable time intervals. 2. An MFD shall be able to capture the print job user metadata to associate the print job with the authenticated user at the output device. The MFD will not show other user’s jobs sitting in the queue. Only the authenticated user’s job will be shown as not to present a security vulnerability target. 3. The Contractor shall provide a PIV enabled secure print feature that allows users to retrieve printouts securely, using their PIV credentials. 4. The MFD shall be capable of allowing the user to authenticate at the MFD with PIV to release the held print job(s). 5. For auditing purposes, an MFD shall track username, print job name, and date/time stamp for all print jobs. 6. MFD shall support secure print release via use of VA supported PIV card and NT credentials entered on a key board. All licensing for this solution must be included in the cost of the device. | ||||||||||
| Offeror shall provide secure, PIV printing for both Veterans Health Information Systems & Technology Architecture (VistA), Cerner Millenium Military Health Record (MHR) and Microsoft print jobs: 1. In addition to receiving and processing normal print and scan jobs, an MFD on the network shall be able to receive any user-initiated secure print jobs via PIV Authentication (VistA terminal emulation, CPRS, Cerner Millenium (MHR), and other Windows applications print jobs) from workstations and allow only the specified user to view, or delete only their print jobs from the MFD. Unclaimed print jobs must be deleted by the system at configurable time intervals. 2. An MFD shall be able to capture the print job user metadata to associate the print job with the authenticated user at the output device. The MFD will not show other user’s jobs sitting in the queue. Only the authenticated user’s job will be shown as not to present a security vulnerability target. 3. The Contractor shall provide a PIV enabled secure print feature that allows users to retrieve printouts securely, using their PIV credentials. 4. The MFD shall be capable of allowing the user to authenticate at the MFD with PIV to release the held print job(s). 5. For auditing purposes, an MFD shall track username, print job name, and date/time stamp for all print jobs. 6. MFD shall support secure print release via use of VA supported PIV card and NT credentials entered on a key board. All licensing for this solution must be included in the cost of the device. | ||||||||||
| Offeror shall provide secure, PIV printing for both Veterans Health Information Systems & Technology Architecture (VistA), Cerner Millenium Military Health Record (MHR) and Microsoft print jobs: 1. In addition to receiving and processing normal print and scan jobs, an MFD on the network shall be able to receive any user-initiated secure print jobs via PIV Authentication (VistA terminal emulation, CPRS, Cerner Millenium (MHR), and other Windows applications print jobs) from workstations and allow only the specified user to view, or delete only their print jobs from the MFD. Unclaimed print jobs must be deleted by the system at configurable time intervals. 2. An MFD shall be able to capture the print job user metadata to associate the print job with the authenticated user at the output device. The MFD will not show other user’s jobs sitting in the queue. Only the authenticated user’s job will be shown as not to present a security vulnerability target. 3. The Contractor shall provide a PIV enabled secure print feature that allows users to retrieve printouts securely, using their PIV credentials. 4. The MFD shall be capable of allowing the user to authenticate at the MFD with PIV to release the held print job(s). 5. For auditing purposes, an MFD shall track username, print job name, and date/time stamp for all print jobs. 6. MFD shall support secure print release via use of VA supported PIV card and NT credentials entered on a key board. All licensing for this solution must be included in the cost of the device. | ||||||||||
| Offeror shall provide secure, PIV printing for both Veterans Health Information Systems & Technology Architecture (VistA), Cerner Millenium Military Health Record (MHR) and Microsoft print jobs: 1. In addition to receiving and processing normal print and scan jobs, an MFD on the network shall be able to receive any user-initiated secure print jobs via PIV Authentication (VistA terminal emulation, CPRS, Cerner Millenium (MHR), and other Windows applications print jobs) from workstations and allow only the specified user to view, or delete only their print jobs from the MFD. Unclaimed print jobs must be deleted by the system at configurable time intervals. 2. An MFD shall be able to capture the print job user metadata to associate the print job with the authenticated user at the output device. The MFD will not show other user’s jobs sitting in the queue. Only the authenticated user’s job will be shown as not to present a security vulnerability target. 3. The Contractor shall provide a PIV enabled secure print feature that allows users to retrieve printouts securely, using their PIV credentials. 4. The MFD shall be capable of allowing the user to authenticate at the MFD with PIV to release the held print job(s). 5. For auditing purposes, an MFD shall track username, print job name, and date/time stamp for all print jobs. 6. MFD shall support secure print release via use of VA supported PIV card and NT credentials entered on a key board. All licensing for this solution must be included in the cost of the device. | ||||||||||
| Offeror shall provide secure, PIV printing for both Veterans Health Information Systems & Technology Architecture (VistA), Cerner Millenium Military Health Record (MHR) and Microsoft print jobs: 1. In addition to receiving and processing normal print and scan jobs, an MFD on the network shall be able to receive any user-initiated secure print jobs via PIV Authentication (VistA terminal emulation, CPRS, Cerner Millenium (MHR), and other Windows applications print jobs) from workstations and allow only the specified user to view, or delete only their print jobs from the MFD. Unclaimed print jobs must be deleted by the system at configurable time intervals. 2. An MFD shall be able to capture the print job user metadata to associate the print job with the authenticated user at the output device. The MFD will not show other user’s jobs sitting in the queue. Only the authenticated user’s job will be shown as not to present a security vulnerability target. 3. The Contractor shall provide a PIV enabled secure print feature that allows users to retrieve printouts securely, using their PIV credentials. 4. The MFD shall be capable of allowing the user to authenticate at the MFD with PIV to release the held print job(s). 5. For auditing purposes, an MFD shall track username, print job name, and date/time stamp for all print jobs. 6. MFD shall support secure print release via use of VA supported PIV card and NT credentials entered on a key board. All licensing for this solution must be included in the cost of the device. | ||||||||||
| Offeror shall provide secure, PIV printing for both Veterans Health Information Systems & Technology Architecture (VistA), Cerner Millenium Military Health Record (MHR) and Microsoft print jobs: 1. In addition to receiving and processing normal print and scan jobs, an MFD on the network shall be able to receive any user-initiated secure print jobs via PIV Authentication (VistA terminal emulation, CPRS, Cerner Millenium (MHR), and other Windows applications print jobs) from workstations and allow only the specified user to view, or delete only their print jobs from the MFD. Unclaimed print jobs must be deleted by the system at configurable time intervals. 2. An MFD shall be able to capture the print job user metadata to associate the print job with the authenticated user at the output device. The MFD will not show other user’s jobs sitting in the queue. Only the authenticated user’s job will be shown as not to present a security vulnerability target. 3. The Contractor shall provide a PIV enabled secure print feature that allows users to retrieve printouts securely, using their PIV credentials. 4. The MFD shall be capable of allowing the user to authenticate at the MFD with PIV to release the held print job(s). 5. For auditing purposes, an MFD shall track username, print job name, and date/time stamp for all print jobs. 6. MFD shall support secure print release via use of VA supported PIV card and NT credentials entered on a key board. All licensing for this solution must be included in the cost of the device. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .