Attachment 0002 Technical Compliance Workbook.xlsx
XLSX spreadsheet 25 KB Posted
- Solicitation number
- PANROC26P0000031130
About this file
This is a Technical Compliance Workbook that serves as an administrative gateway review document and submission template for vendors responding to the Copier/Multi-Function Device Printers and Services solicitation (PANROC26P0000031130) issued by the Department of the Army Materiel Command Contracting Command Rock Island Arsenal. Vendors must submit this workbook alongside their narrative proposal, providing explicit compliance statements for each requirement supported by documentation applicable to the network environments in scope: WREN (USMA hybrid Active Directory/Azure environment), NIPRNET/Garrison, and MEDCOM/KACH hospital facilities. The workbook requires vendors to identify whether capabilities are native, third-party, or require additional licensing, and to provide a documentation register for all supporting artifacts with sufficient evidence to permit independent Government validation of compliance.
The technical requirements encompass an enterprise multifunction device (MFD) solution supporting 367 devices across three distinct security environments with specific capabilities including: centralized management with Azure SQL/Managed Instance support, secure printing from any device, SNMPv3 and 802.1x authentication, SYSLOG forwarding to Microsoft Sentinel, LDAPS integration with Active Directory and Azure Entra ID, role-based print queue management, minimum 40 PPM print speed, duplex and finishing options (3-hole punch, stapling), scanning of 11x17 tabloid paper with scan-to-email and OneDrive/SharePoint integration, support for Windows/MacOS/Linux/iOS/Android printing (USMA only), DoD CAC authentication (Garrison/Hospital), media sanitization per NIST 800-88, and compliance with applicable DoD STIG standards. The vendor must demonstrate remote management, reporting/monitoring capabilities (print volume, toner levels, device errors), support for at least two device relocations annually, and service level commitments including technician response within two business days and software resolution within ten business days.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Additional Q-A 2026-Aug-14.docx | DOCX document | |
| Attachment 0002 Technical Compliance Workbook v2.xlsx | XLSX spreadsheet | |
| Attachment 0003 Price Matrix Version 3.xlsx | XLSX spreadsheet | |
| Attachment 0001 RFQ_Amendment__Instructions .docx | DOCX document | |
| Price Matrix Version 2.xlsx | XLSX spreadsheet | |
| PWS_MULTI_FUNC_DEVICE_v12.docx | DOCX document | |
| Copy of QAs Second Postingv2_20260608.xlsx | XLSX spreadsheet | |
| Volume SEP 2024 - Feb 2025.xlsx | XLSX spreadsheet | |
| QA Responses.docx | DOCX document |
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
Sheet1
| PWS Requirements Supported | Required Submission Artifact/ Requirement | Product/Component applicability/integration. | Vendor Answer | Evidence Support Document (Document, Page, Paragraph, Line) | Additional Vendor Narrative |
| Technical Compliance Workbook | SECTION 1 is the initial administrative and compliance gateway review. | Vendor must submit a technical compliance workbook in addition to the narrative proposal. Vendor must provide explicit statements for each requirement, supported by documentation for each or all - applicable network enviroments. | Vendor must identify whether a capability is native, third-party, or requires additional licensing Vendor must provide a documentation register for all supporting artifacts. Vendor responses may include stated assumptions, but may not defer core compliance to a post-award assessment of the current USMA/WREN/NIPRNET/MEDCOM environment. | Vendor shall provide sufficient supporting documentation to permit the Government to independently validate compliance with applicable requirements. | Supporting documentation may include, but is not limited to, product data sheets, security technical guides, administrator guides, installation/deployment guides, authentication/CAC/directory integration guides, mobile print support documentation, service plan/SLA documentation, quality control plans, media sanitization procedures, architecture diagrams, scalability documentation, recovery/restore documentation, and data flow documentation. |
| SECTION 2 | |||||
| 2.3.2 Table 3 Item 1 | An enterprise solution is required. | All | |||
| 2.3.2 Table 3 Item 2 | Solution must be centrally managed on-site and support USMA hybrid Active Directory /Microsoft Azure Cloud environment and native Windows Print Management capabilities. | USMA | |||
| 2.3.2 Table 3 Item 3 | Must be able to print securely from anywhere from any device. | USMA | |||
| 2.3.2 Table 3 Item 4 | Print data and firmware must be secure; updates included; centrally manage device settings at scale. | All | |||
| 2.3.2 Table 3 Item 5 | Any requirement for installing MS SQL or similar SQL must be able to be installed in Azure SQL/Managed Instance. | USMA | |||
| 2.3.2 Table 3 Item 6 | Must have reporting/monitoring capabilities such as print volume per printer, toner levels, and device errors. | USMA | |||
| 2.3.2 Table 3 Item 7 | SNMP capability is required and must be v3 or greater. | All | |||
| 2.3.2 Table 3 Item 8 | 802.1x wired authentication on the network is required. | All | |||
| 2.3.2 Table 3 Item 9 | SYSLOG settings must allow log forwarding directly to Microsoft Sentinel or other internal SYSLOG server. | All | |||
| 2.3.2 Table 3 Item 10 | Must configure LDAPS lookups to Active Directory and/or Azure Entra ID for westpoint.edu email lookup. | USMA | |||
| 2.3.2 Table 3 Item 11 | Print queue management must be granular and allow specific people to manage jobs for specific printers without global admin privileges. | USMA | |||
| 2.3.2 Table 3 Item 12 | Must be able to relocate a copier by request at least twice per contract year. | All | |||
| 2.3.2 Table 3 Item 14 | Additional printers require customer approval before adding to agreement. | All | |||
| 2.3.2 Table 3 Item 15 | Relocated printers require new address and contact information. | All | |||
| 2.3.2 Table 3 Item 16 | Removed printers require update to Contracted Printer list. | All | |||
| 2.3.2 Table 3 Item 17 | Capability to bill for print jobs and set print quotas through third-party software such as PaperCut. | USMA | |||
| 2.3.2 Table 3 Item 18; 2.4(g) | Authorized individuals must order toner on demand and ship to designated address or autoship toner. | All | |||
| 2.3.2 Table 3 Item 19; 2.4(h) | Disk drives leaving site must be overwritten by internal or NIST 800-88 conforming process. | All | |||
| 2.3.2 Table 3 Item 20 | Must authenticate to AD and/or Entra ID and provide PIN, keycard, NFC alternatives that integrate with directory services. | USMA | |||
| 2.3.2 Table 3 Item 21 | Must authenticate with DoD CAC and integrate with Army and MEDCOM directory services. | GARRISON/HOSPITAL | |||
| 2.3.2 Table 3 Item 22 | Ability to send job to queue from any device and release job to any printer using existing enterprise capabilities such as PrintLogic. | All | |||
| 2.3.2 Table 3 Item 23 | Must have trays for 11x17, 8.5x14, and 8.5x11 paper. | All | |||
| 2.3.2 Table 3 Item 24 | Printer interface console must be identical for color and black/white models. | All | |||
| 2.3.2 Table 3 Item 25 | Must send secure print jobs with PIN release. | All | |||
| 2.3.2 Table 3 Item 26 | Must have duplex and allow duplex as default | All | |||
| 2.3.2 Table 3 Item 27 | Must have 3-hole punch capability as an option. | All | |||
| 2.3.2 Table 3 Item 28 | Must have staple capability as an option | All | |||
| 2.3.2 Table 3 Item 29 | Must scan 11x17 tabloid paper. | All | |||
| 2.3.2 Table 3 Item 30 | Must scan to email (self and restrict to westpoint.edu domain only.) | USMA | |||
| 2.3.2 Table 3 Item 31 | Must scan to OneDrive/SharePoint for each authenticated user. | USMA | |||
| 2.3.2 Table 3 Item 32 | Must copy and configure public copy with no authentication. | All | |||
| 2.3.2 Table 3 Item 33 | Must scan/copy multi-page documents including duplex. | All | |||
| 2.3.2 Table 3 Item 34 | USMA devices must accept print jobs from Windows, MacOS, Linux, Apple iOS, and Android. | USMA | |||
| 2.3.2 Table 3 Item 35 | Garrison/Hospital devices must accept print jobs from Windows systems. | GARRISON/HOSPITAL | |||
| 2.3.2 Table 3 Item 36 | Must have minimum print speed of 40 PPM (+/- 5ppm). | All | |||
| 2.3.2 Table 3 Item 37; 2.4(d); 2.3.2 Table 3 Item 37 | Must send technicians for repairs within two business days. | All | |||
| 2.3.2 Table 3 Item 38 | Must configure applicable DoD STIG for current versions of "Multifunction Device and Network Printers STIG", NETCOM, MEDCOM, ARCYBER, and DISA security standards. | All | |||
| SECTION 3 | |||||
| 2.1.1; 2.4(a) | Deliver/install complete packages segmented to each agency and perform standard operational test. | All | |||
| 2.4(b); 2.4(c) | Install at customer locations and provide initial orientation to users. | All | |||
| 2.4(e)(1); 2.3.2 Table 3 Item 14 | Additional printers require notification, approval, and KO modification before provisioning. | All | |||
| 2.4(e)(2); 2.3.2 Table 3 Item 15 | Relocated printer updates require new address/contact information. | All | |||
| 2.4(e)(3); 2.3.2 Table 3 Items 27-28 | Options such as 3-hole punch require KO coordination before price adjustment. | All | |||
| 2.4(f); 2.3.2 Table 3 Item 16 | Removed printers require Contracted Printer list update and KO-coordinated price adjustment. | All | |||
| 2.4(i); 2.3.2 Table 3 Item 12 | Relocate copier by request at least twice per contract year. | All | |||
| 2.4(j); 2.3.2 Table 3 Items 2, 4, 6 | MFD management services must remotely manage fleet after installation. | All | |||
| 2.4(k) | Software maintenance response within two business days and resolution within 10 business days. | All | |||
| 2.4(l) | Acknowledge all COR communications within one business day. | All | |||
| 2.4(m) | Provide pricing or adjustment information within seven business days for additions/removals. | All | |||
| SECTION 4 | |||||
| 2.3.2 Table 3 Item 5 | Azure SQL or Azure SQL Managed Instance must be explicitly supported. Other database solutions are insufficient if SQL is required by the solution. | All SQL or SQL-like Components | |||
| 2.3.2 Table 3 Items 2, 4, 6, 11; 2.4(j) | Central management must support enterprise management, configuration changes, firmware updates, monitoring, remote troubleshooting, and role-based administration. | All | |||
| 2.3.2 Table 3 Items 10, 20, 21 | Authentication must integrate with AD, Entra ID, Army/MEDCOM directory services, and supported alternate authentication methods. | All | |||
| 2.3.2 Table 3 Item 4; 2.4(j); 2.4(k); 4.1(g) | Vendor shall describe software version lifecycle, upgrade methodology, rollback capability, and supportability window. | All | |||
| 2.1.2; 2.3.1 Table 2; 2.3.2 Table 3 Items 1, 2, 4, 6; 2.4(j) | Vendor shall identify the tested and supported fleet scale of the proposed architecture, including whether it can support the 367-device profile in the PWS across WREN, NIPRNET/Garrison, and MEDCOM/KACH without changing the proposed architecture. | All | |||
| 2.3.2 Table 3 Items 4, 6, 9, 17, 19; 4.1(h); 6.17.1 | Vendor shall identify all operational, reporting, accounting, auditing, logging, and configuration data generated, stored, retained, or maintained by the proposed solution. Vendor shall identify data ownership, retention methods, export capabilities, available export methods, and any restrictions impacting Government access to or portability of the data. formats, retrieval | All | |||
| 2.1.2; 2.3.2 Table 3 Items 4, 5, 6, 9, 10, 20, 21, 31, 38; 2.3.3; 6.17.1 | Vendor shall identify all data flows to the maximum extent possible. For each operational, reporting, management, monitoring, authentication, logging, mobile print, scan, cloud, and support function, the vendor shall identify the source, destination, transmission path, storage location, external service dependency, encryption method, and access method. Vendor shall identify any cloud-hosted, vendor-hosted, externally managed, or internet-connected services that process, store, transmit, or receive Government data. | All | |||
| SECTION 5 | |||||
| 2.1.2; 2.3.2 Table 3 Items 7, 8, 9, 10, 20, 21, 38; 2.3.3 | Vendor shall describe the security and authentication model applicable to each environment. At a minimum, the response shall identify authentication sources, directory integration methods, CAC support, alternative authentication methods, SNMP version support, 802.1x support, logging architecture, syslog destinations, and applicable security-control implementation approach. | All | |||
| 2.1.2; 2.3.2 Table 3 Items 2, 4, 6, 7, 8, 9, 38; 2.4(j)- 2.4(m); 2.3.3 | Vendor shall describe how the proposed solution will be managed and supported within each applicable environment. The response shall identify remote-management capabilities, administrative responsibilities, support workflow, escalation workflow, access operational limitations, and any environment-specific support considerations. requirements, | All | |||
| 2.1.2; 2.3.2 Table 3 Items 2, 5, 6; 2.4(j) | Vendor must identify all management, reporting, database, and monitoring components per environment. | All | |||
| 2.1.2(a); 2.3.2 Table 3 Items 2, 3, 5, 10, 11, 17, 20, 30, 31, 34 | For WREN environments, vendor shall identify support for hybrid Active Directory and Azure integration, Azure SQL Managed Instance requirements, secure print, mobile print, Windows Print Management, LDAPS lookup, alternative authentication methods, OneDrive and SharePoint integration, scan-to-email capability, delegated administration, and billing/quota functionality where applicable. | WREN/USMA | |||
| 2.1.2(a); 2.3.2 Table 3 Items 3, 34 | USMA devices must support secure print anywhere and Windows, MacOS, Linux, iOS, Android. | WREN/USMA | |||
| 2.1.2(a); 2.3.2 Table 3 Items 10, 20, 30, 31 | Vendor shall describe how the proposed solution satisfies the WREN-related requirements identified within this solicitation, including identity integration, authentication, directory services integration, email integration, and cloud storage integration where applicable. The response shall identify any solution dependencies, supporting infrastructure, architectural considerations, implementation assumptions, or prerequisites required to support those capabilities. | WREN/USMA | |||
| 2.1.2(b); 2.3 Table 1; 2.3.2 Table 3 Items 4, 7, 8, 9, 21, 35, 38; 2.3.3; 2.4(j) | Vendor shall describe how the proposed solution satisfies the NIPRNET/Garrison-related requirements identified within this solicitation, including authentication, directory integration, client compatibility, security controls, and management capabilities where applicable. response shall identify any solution dependencies, supporting infrastructure, implementation The assumptions, prerequisites, or operational constraints required for operation within the NIPRNET/Garrison environment. | NIPRNET/GARRISON | |||
| 2.1.2(b); 2.3.2 Table 3 Items 7, 8, 9, 38; 2.3.3 | NIPRNET devices must comply with DISA STIG, NETCOM, ARCYBER, SNMPv3, 802.1x, syslog/SIEM. | NIPRNET/GARRISON | |||
| 2.1.2(c); 2.3 Table 1; 2.3.2 Table 3 Items 19, 21, 25, 32, 33, 35, 38; 2.3.3 | Vendor shall describe how the proposed solution satisfies the MEDCOM/KACH-related requirements identified within this solicitation, including authentication, directory integration, client compatibility, security controls, workflow capabilities, and operational where applicable. The response shall identify any solution dependencies, supporting requirements infrastructure, implementation assumptions, prerequisites, or operational constraints required for operation within the MEDCOM/KACH environment. | MEDCOM/KACH | |||
| 2.1.2(c); 2.3.2 Table 3 Items 7, 8, 9, 38; 2.3.3 | MEDCOM devices must comply with applicable secure requirements including SNMPv3, 802.1x, syslog/SIEM. | MEDCOM/KACH | |||
| 2.1.2(c); 2.3.2 Table 3 Items 19, 25, 32, 33; 2.3.3 | Hospital devices must support secure print, public copy, duplex scan/copy, and media sanitization. | MEDCOM/KACH | |||
| 2.1.2(c); 2.3.3 | If MEDCOM/DHA requirements conflict with baseline requirements, secure requirements take priority. | MEDCOM/KACH | |||
| 2.1.2; 2.3.2 Table 3 agency applicability; 2.3.3; RFQ / Evaluation Control | Compliance shall be evaluated independently for WREN, NIPRNET/Garrison, and MEDCOM/KACH environments when applicable. Evidence demonstrating functionality in one environment shall not be considered evidence of functionality in another environment unless the vendor explicitly identifies equivalent architecture, security controls, dependencies, and support model. | All |
File details come from the government source that posted it. Updated .