E1. RFID Questions and Answers.docx

DOCX document 18 KB Posted

Attached to
UPDATE 8/28/2026 NMMC Standalone RFID Firearm Accountability System Federal contract opportunity
Solicitation number
M0026426Q0155
Issued by
United States Marine Corps

About this file

This is a Questions and Answers document for Solicitation M0026426Q0155, addressing clarifications on the National Museum of the Marine Corps' (NMMC) standalone RFID firearm accountability system requirement. The Q&A provides critical guidance on 13 industry questions spanning software flexibility, authorized reseller requirements, system architecture, compliance documentation, and data handling procedures.

Key clarifications include: contractor-developed software integrated with commercial RFID middleware is acceptable if it meets salient characteristics; small business prime contractors need not be direct authorized resellers for every OEM but must source through OEM-authorized distributors with verifiable documentation; directional detection means detection within a 12-foot radius (directional ingress/egress determination is not required); the system must operate independently of the NIPRNet but be Wi-Fi capable with the capability to synchronize databases between the Vault and Museum locations; offerors may submit their own compliance matrices addressing salient characteristics; RFID tags should contain a unique EPC identifier associated with four data elements (serial number, accession number, NSN, and location code) in the local database rather than requiring all data physically encoded on tags; the Government does not require source code or unlimited rights to contractor-developed software; current successor configurations of referenced hardware (Impinj R700 and Zebra RFD90 families) are acceptable; ruggedization must meet or exceed the Dell Pro Max 16 reference specification; portal read-zone coverage must achieve 100 percent tag-read reliability with directional detection not required; and firearm serial numbers are not classified as Controlled Unclassified Information (CUI). This amendment was posted on August 28, 2026, in response to pre-quotation inquiries.

View the file

Other files for this federal contract opportunity

Other files attached to UPDATE 8/28/2026 NMMC Standalone RFID Firearm Accountability System, newest first.
File Type Posted
E1. Amendment M0026426Q01550001 SF 30.pdf PDF
D1. RFID Description.pdf PDF
D1. Solicitation - M0026426Q0155.pdf PDF
C10. Wage Determination 2015-4281 (Prince William, VA).pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

M00264-26-Q-0155 RFID Questions and Answers

Q1 . Software / Custom Application: Section 7 identifies SmarTrak Digital Asset Tracking Software as the standard of quality under a Brand-Name-or-Equal requirement. May an offeror propose a contractor-developed, locally installed Windows application integrated with commercially available RFID middleware and hardware, provided the complete solution meets or exceeds all salient characteristics? Or must the software proposed under Line Item 8 be an existing commercially available software product at the time of quotation?

A1. Yes, if it meets the criteria, we don’t have an issue with this.

Q2. Authorized Reseller Requirement: The solicitation states that quotes will only be accepted from authorized resellers/distributors of the quoted supply. Must the small-business prime contractor itself be a direct authorized reseller/distributor for every hardware and software manufacturer included in the solution, or may the prime purchase hardware/software through manufacturer-authorized distributors and provide evidence of the authorized supply chain? How should this requirement apply to software developed directly by the prime contractor?

A2. In order to not restrict competition, the small-business prime contractor is not required to be a direct authorized reseller/distributor for every hardware and software Original Equipment Manufacturer (OEM) included in their quote. However, the prime contractor must source all hardware and third-party software exclusively through OEM-authorized distributors or resellers and provide verifiable supply-chain documentation. For software developed natively and owned by the prime contractor, the authorized reseller requirement does not apply.

Q3. Directional Detection: Section 6.3 requires directional detection. Please clarify whether this means the system must specifically determine entry versus exit (ingress versus egress) of each tagged firearm through each monitored doorway. If so, is there a required accuracy or acceptance threshold for direction determination?

A3. We didn’t think directional was an issue. It needs to be able to detect within a 12’ radius from the reader so we can get a few weapons that are high up.

Q4. Additional Sensors / Portal Architecture: If required to achieve reliable direction-of-travel detection, may the contractor incorporate additional antennas and/or supplementary non-RFID sensors while continuing to meet the required passive UHF RFID functionality and other salient characteristics?

A4. No need.

Q5. Air-Gapped System vs. Email/SMS Alerts: Section 2.1 requires the system to be fully air-gapped with no internet or external connectivity, while Section 7.4 requires automatic email and/or SMS alerts. Will the Government provide an internal SMTP, SMS, or other Government-network alert gateway? If no such gateway is available, will local visual and/or audible real-time alerts satisfy Section 7.4?

A5. It will not be on the NIPR network. It needs to be Wi-Fi capable. Air-gapped may be the wrong term here, but it needs to run independently of the NIPRNet.

Q6. Two-Site Synchronization: Section 3.1 states that each site's computing device will operate independently while "syncing over local Wi-Fi," while Section 2.5 indicates one separate local network per site. Are the Vault and Museum databases required to synchronize with each other? If yes, what Government-provided network connection between the two sites will be available? If no inter-site connectivity is provided, are two independently maintained local databases acceptable?

A6. If the database is updated while on the museum’s Wi-Fi, it should be no different from updating the database in the vault. Input at one location should be saved to both.

Q7. Missing Compliance Matrix: Section 1.0 states that offerors proposing "or equal" products shall submit a completed Compliance Matrix (Deliverable 2 / Attachment). The solicitation package appears not to contain this matrix. Will the Government provide the required Compliance Matrix, or may offerors prepare and submit their own matrix addressing each salient characteristic?

A7. This was poor wording in the instructions and should be referencing Attachment 1, which lists the brand name parts. Quoters can submit their own matrix addressing each salient characteristic in addition to supplying the requested supporting technical data.

Q8. RFID Tag Encoding: Section 4.8 requires each RFID tag to be pre-encoded using the NMMC-furnished serial number, accession number, NSN, and location code. Does the Government require all four data elements to be physically written into the RFID tag's EPC/user memory, or may the tag contain a unique EPC identifier that is associated with these fields in the local accountability database? If the data must reside on the tag, please provide the required encoding format/standard and field structure.

A8. Weapons are tracked by those four data points. Data will be provided via Excel spreadsheet.

Q9. Software/Data Rights: For contractor-developed software, does the Government require delivery of source code and/or unlimited rights in the application software, or is the requirement limited to a perpetual unlimited-use local software license, Government ownership of inventory data/configurations/logs, and unlimited reproduction rights for the training and system documentation identified in Section 8.3?

A9. USG does not require delivery of source code or unlimited rights to the application software.

Q10. Hardware Part Numbers: Attachment 1 identifies manufacturer part numbers including Impinj IPJ-R700-141 and Zebra RFD90-G20070US-110 and states that the part numbers are to be verified. May offerors quote the manufacturers' current successor/currently orderable configurations of the same R700 and RFD9090 product families when they meet or exceed all salient characteristics?

A10. Yes

Q11. Laptop Ruggedization: Section 3 describes a "ruggedized Windows 11 laptop," while Attachment 1 identifies the Dell Pro Max 16 MC16250 as the brand-name reference. Does the specified Dell Pro Max 16 MC16250 satisfy the Government's ruggedized requirement, or is a specific ruggedization standard such as a MIL-STD/IP rating required?

A11. The Dell Pro Max 16 or equivalent meets our needs.

Q12. Portal Acceptance / Site Conditions: Section 6.4 requires installation, range testing, and tuning based on actual door geometry and ambient RF conditions. What objective acceptance criteria will the Government use for portal read-zone coverage, tag-read reliability, and direction-of-travel performance? Will a pre-award site visit or additional doorway dimensions/power/network-location information be made available?

A12. Portal read zone must identify when a tagged firearm passes through the portal. Tag-read reliability must be 100%. Direction of travel is not required.

Q13. Inventory Data / Cybersecurity: Because the contractor must receive NMMC inventory data for approximately 3,500 firearms to initialize the system and pre-encode tags, will that Excel inventory be designated CUI or other controlled information? If so, please identify the required method for Government-to-contractor transfer and any contractor cybersecurity requirements applicable to handling the inventory prior to installation.

A13. Because the weapons are museum artifacts held in trust for the American public, their serial numbers are not considered CUI.

File details come from the government source that posted it. Updated .