Enterprise RFID Technology, Installation, and Azure WIMS Integration

United States Census Bureau (USCB) Enterprise RFID Technology, Installation, and Azure WIMS Integration REQUEST FOR INFORMATION (RFI) This RFI is solely for information and planning purposes it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. Further, the USCB is at the early stages of market research and is not, at this time, seeking proposals and will not accept unsolicited proposals. Interested parties are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. 1.0 Purpose The U.S. Census Bureau (USCB) issues this Request for Information (RFI) for market research under Federal Acquisition Regulation (FAR) Part 10 to understand current business practices and identify industry capabilities for furnishing, installing, configuring, testing, and integrating radio frequency identification (RFID) technology with the USCB s existing Warehouse Inventory Management System (WIMS). The USCB seeks industry input on these types of services and expertise in achieving the desired objectives in accordance with federal requirements. To date, the USCB has already developed a scalable WIMS platform using Microsoft technologies in its Microsoft Azure environment. This RFI does not seek a replacement warehouse management platform. The USCB s primary interest is to acquire industry recommendations on RFID equipment and supporting software, facility deployment and integration services, and secure delivery of RFID event data into the existing WIMS environment. The USCB believes industry has the best knowledge of current offerings and how to plan for, acquire, and integrate evolving technology trends. Vendors are encouraged to provide recommendations and describe innovative, commercially available, and proven approaches that address the objectives detailed within this RFI without being constrained by a prescriptive equipment design or configuration. 2.0 Background and Operational Environment The USCB manages survey forms, printing and mailing materials, shipping supplies, and other inventory supporting demographic, economic, and decennial programs, including preparations for 2030 Census tests. Inventory is received, stored, moved, issued, transferred, and shipped through multiple facilities. Automated identification and transaction capture can reduce manual inventory handling and improve the accuracy and timeliness of enterprise inventory records. Potential locations include National Processing Center operations in Charlestown, Indiana; Census Bureau Headquarters in Suitland, Maryland; a warehouse in Franconia, Virginia; Regional Offices; and other Government-designated facilities. Actual locations, installation scope, sequencing, and site access would be determined by the Government. These locations may have different layouts, physical security restrictions, network conditions, and operating requirements. 3.0 Objectives and Mission-Critical Capability Areas The USCB intends to leverage industry knowledge, feedback, recommendations, and expertise on proven approaches and best practices that achieve the objectives listed below. 3.1 RFID identification and multi-level tracking The USCB is interested in tracking at the item or box, pallet, and rack or storage-location levels. Industry recommendations may include passive or active RFID, hybrid approaches, or complementary identification methods where appropriate. Recommended solutions should support reliable identification and location/movement events during receiving, putaway, internal transfers, picking, shipping, cycle counting, and reconciliation. Input is requested to address read accuracy, interference, duplicate or missed events, and the practical limits of location precision. 3.2 Equipment provision, site assessment, and installation The contemplated effort includes facility assessments; design and equipment selection; provision of tags, readers, antennas, handheld or mobile equipment, portals, and supporting components as appropriate; physical installation and configuration; and operational testing. Respondents shall provide input into the considerations made in regards to site dependencies, secured-space work practices, commissioning, warranties, support, and expansion to additional facilities, as directed. 3.3 Secure integration with existing Microsoft Azure WIMS The RFID solution must exchange usable, timely data with the existing Government WIMS rather than create a competing inventory system of record. Respondents are requested to recommend integration of reader and edge-device feeds with Azure-hosted WIMS through appropriate secure interfaces, APIs, messaging, middleware, or other standards-based methods. Anticipated work may include event filtering, data mapping to Government inventory identifiers and locations, interface development, custom fields or components as needed, error handling, testing, documentation, and knowledge transfer. Specific Azure services and interface specifications will be coordinated with the Government during subsequent planning. 3.4 Security, reliability, and sustainment The USCB seeks recommended approaches and solutions suitable for controlled federal facilities and integration with its existing authorized cloud boundary, subject to applicable security review and approval. Respondents are requested to provide information which describes secure communications, device administration, access control, logging, resilience during network interruptions, patching, lifecycle support, and long-term costs. The USCB seeks recommended approaches which permit Government operation and sustainment without unnecessary vendor lock-in. 4.0 Industry Response and Feedback Questions A. RFID technology and operational performance 1. Describe your recommended technology and architecture for identifying and tracking individual items or boxes, pallets, and racks or storage locations in multiple warehouse facilities. Explain any recommended RFID or hybrid approaches. 2. Identify the major hardware and software components your recommended approach would provide, including tags, fixed or mobile readers, antennas, portals, edge components, and management tools. Distinguish commercial products from custom components. 3. How would your solution capture receiving, putaway, internal movement, picking, shipping, transfers, and cycle-count events, and associate them with the correct inventory identifiers and locations? 4. What read accuracy and location precision can realistically be achieved, and how do you address dense racks, metal, packaging, interference, missed reads, and duplicate events? 5. What mobile, handheld, exception-resolution, and offline or intermittent-connectivity capabilities are available for warehouse operators? B. Facility assessment, installation, and rollout 6. Describe your approach to surveying facilities, developing a site-specific equipment design, and determining reader, antenna, portal, and network placement. 7. Describe your ability to furnish, install, configure, and commission equipment in secured Government spaces at Charlestown, IN; Suitland, MD; Franconia, VA; Regional Offices; and other locations as directed. Identify subcontractor dependencies. 8. What facility, electrical, networking, physical security, access, and Government-furnished resources would typically be needed for installation and operation? 9. Identify a phased pilot-to-enterprise deployment approach, including indicative schedule, testing and acceptance criteria, and the approach for minimizing disruption to ongoing warehouse operations. C. Existing WIMS and Azure integration 10. Describe how RFID data would be securely transmitted, processed, and integrated into an existing Microsoft Azure-hosted WIMS, without replacing the Government s inventory platform. 11. What integration interfaces and patterns are available (such as APIs, webhooks, message queues, middleware, or edge processing), and how would your recommended approach accommodate Government-defined data schemas and custom fields? 12. How would your recommended solution convert raw RFID reads into reliable inventory events, manage duplicates and errors, reconcile exceptions, and preserve traceability and audit records? 13. What, if any, technical personnel or services would be recommended for Azure connectivity, interface development, configuration, end-to-end testing, documentation, and transfer of knowledge to Government IT staff? D. Security, sustainment, and market considerations 14. Identify cybersecurity and device-management controls, including encryption, authentication, access management, logging, patching, and operation within an existing federal cloud authorization boundary. Identify any external cloud services or data…