The file's text, extracted by GovTribe without its formatting.
M0026425Q0103
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION SF 30 - BLOCK 14 CONTINUATION PAGE
The following have been added by full text:
SITE VISIT Q&A
Q&A RFQ number M00264-25-Q-0103 RFID Inventory System
| 1. How many laptop workstations are required? |
| 2 |
| 2. can you please confirm whether any such certifications are required for this opportunity? If so, it would be helpful to know exactly what they are. If they’re looking for software that must already be federally certified, we want to be respectful of both your time and ours.” |
| no federal software certifications are necessary |
| 3. However, the specs mention that "RFID tags shall be secured through trigger guards." We're not certain whether this means the tags must physically pass through the trigger guard. If that’s the case, the current size (1.45 × 1.0 inches) may be too large to fit through most firearm trigger guards. Could you please help clarify this point? |
| Firstly, the tags have to be cabled through the trigger guard or sling swivel. Only the cable needs to fit through it, the tag does not. |
| 4. ADDENDUM 52.212-1 INSTRUCTIONS TO QUOTERS | 4 | Submission of Quotes, b. (attachment limit) | Given the explicit limitation that quote packages shall not exceed three (3) file/document attachments, could the Government clarify the preferred structure and content expected within these three attachments (e.g., Attachment 1: Signed SF1449/Reps&Certs, Attachment 2: Technical Quote, Attachment 3: Price Quote)? |
| The Government does not have a preferred structure or content expected other than the instructions provided in the RFQ and Amendments. | | | |
| 5. ADDENDUM 52.212-2 EVALUATION | 5 | Evaluation, (a)(2) 2. Past Performance | The RFQ states Past Performance is an evaluation factor for this LPTA acquisition, evaluated per FAR 13.106-2(b)(3)(ii) and DFARS Subpart 204.76, but does not request past performance submissions from offerors. Will the Government determine "neutral to satisfactory" past performance solely based on information available in Government systems like CPARS/SPRS? |
| Please review 52.212-2 Addendum posted with this RFQ, as well as the referenced FAR and DFARS clauses for evaluation criteria. | | | |
| 6. ADDENDUM 52.212-2 EVALUATION | 5 | Evaluation, (a)(2) 2. Past Performance | If an offeror has limited or no past performance history available in Government systems (CPARS/SPRS), how will their Past Performance factor be evaluated against the "neutral to satisfactory" requirement? Will this result in a neutral rating considered satisfactory? |
| Please review 52.212-2 Addendum posted with this RFQ, as well as the referenced FAR and DFARS clauses for evaluation criteria. IAW DFARS 204.7603, “Offerors or quoters without a risk assessment in SPRS shall not be considered favorably or unfavorably.”. | | | |
| 7. Is this a new requirement or a recompete? If recompete, can the government provide information on the Incumbent contractor? |
| This is a new requirement. |
| 8. SITE VISIT INFORMATION | NA | Important Note (DBIDS) / General Requirement | Beyond the DBIDS registration required for site visit attendees, are any specific background checks, security clearances, or suitability determinations required for contractor personnel who will be performing the system installation, testing, initial data entry, and training on-site? |
| No, just a visitor pass from the visitor center | | | |
| 9. ITEM DESCRIPTION | 7 | Salient Characteristics #11 (Install, Test, Data Entry, Train) / CLIN 0001 | CLIN 0001 is a single Firm-Fixed Price (FFP) line item for the "RFID Inventory System", which includes both supply items and services (installation, testing, data entry, training). Is the Government requesting or does it desire a separate breakdown of costs for the system hardware/software versus the associated services within the overall FFP? |
| The Government does not require a separate breakdown of costs. | | | |
| 10. ADDENDUM 52.212-2 EVALUATION | NA | Evaluation / Salient Characteristics | The Evaluation section states technical compliance is based on conforming to the solicitation, meeting salient characteristics, delivery dates, and terms/conditions. Are there any specific technical requirements or evaluation criteria for the RFID system beyond the listed Salient Characteristics? |
| All technical requirements and evaluation criteria required by the Government are listed in this RFQ and Addendum. | | | |
| 11. Will you provide a server where all the data shall be stored. |
| No. |
| 12. You mentioned 10 user - are there ten separate stations |
| No, up to 10 users for the two workstations. |
| 13. What all technical docs do we provide in order to bid |
| All information required to respond to the solicitation is listed in this RFQ and Addendum. |
| 14. We are registered with SAM.gov and have done government projects before, is that sufficient or we need to provide any other information. We are also a small business |
| All information required to respond to the solicitation is listed in this RFQ and Addendum. |
| 15. As per the scope there are only two vault doors, one dock door - so can we assume only 3 scanners will be required or we need more at different locations. |
| The three entry points are the only required stationary scanners. |
| 16. As per the scope on one handheld reader is required - please confirm |
| Two would be preferable. |
| 17. What is the height where we will install the scanners and antenas. |
| At whatever height best fits and allows the system to perform. |
| 18. Can we mount wireless scanners, if so then who will assign IP addresses. Will we work with your IT personnel. |
| Yes, wireless is preferable. |
| 19. What reference is good to bid on this project |
| All information required to respond to the solicitation is listed in this RFQ and Addendum. |
| 20. How will the fixed readers connect to the network? |
| A. Power over ethernet? |
| B. Who’s responsible for pulling the ethernet cabling? |
| Wifi |
| 21. If the connection is to be wireless, are there dedicated electrical outlets near the doors that can power the readers? |
| Yes |
| 22. If ethernet isn’t POE, will need electrical for readers. (is this possible?) |
| yes |
| 23. Laptop computer needs to be on same network backbone as readers and mobile wifi connection. (Is this possible?) |
| yes |
| 24. What is your vision on what the software needs to do/provide in terms of their operations?( will you need transactional functions incorporated ie. alarms when items are moved or checked out with and without authority?) |
| This will primarily be an inventory system to track the weapons both in the vault and in the museum. Sensors at the doors to record when weapons leave the vault/museum will be there to track weapons movements when we do move them between locations. Email and SMS alerts to authorized personnel when a weapon is moved out of either location are critical. |
| 25. Can you provide an example of the inventory as it is designed in excel ( what data is included relating to specific items ), ( are all items simply serialized? or, is each item uniquely identified and the vendor will use that description and develop a new item number? |
| The excel spreadsheet currently has weapon serial number, museum accession number, NSN, description, and location. |
| 26. I understand that some items are loaned out of storage to facilities off premise. Would you envision incorporating that transaction into the RFID solution? If so, please explain. |
| Items going out on loan to other organizations would be scanned out and the location would have to be manually updated as “on loan” |
27. a. NMMC will provide Wi-Fi access.
QUESTION – Is wired network / ethernet also available at each site, or must entire system run only on wifi with fixed readers communicating over wifi?
Wifi
28. c. Tablet/laptop is required for data entry, reports, and database management.
QUESTION – Does tablet/laptop need to be the database SERVER? Or can there be a separate server (example – Windows server with SQL database installed that communicates with fixed readers, handheld readers, and tablet/laptop)?
If server can be part of system architecture, does that server exist or should it be included in RFP? If should be included in RFP, what are standard set by NMMC?
The laptop will likely be the server. We currently do not have an external server for this requirement.
29. CAC reader is for access to the tablet/laptop.
QUESTION – Does CAC reader need to be integrated or can be accessory connected with USB or similar cable?
It can be a USB device.
30. System must not require any recurring subscriptions, 3rd party data storage, or recurring fees. All data must be stored on site and NMMC will retain full ownership and control of all data.
QUESTION – how many years of maintenance should be included with initial RFP proposal? Example – 1 year (standard), 3-year, 5-year or more Product support (non-warranty) should be offered for the lifetime of the system or as per industry standard.
| 31. How are firearms handled / stored during movement? Are they in a case, carried by hand, on cart, stacked on pallet, etc? If inside a case, is the case made of metal or other RFID interfering materials? Is the case like a common firearm case that has some metal, but is primarily made of non-RF blocking materials such as plastics or resins? |
| Weapons are usually moved in plastic “Pelican”-style cases. |
| 32. Can we have a picture of firearms as they are moving out of vault and also into museum at dock door? |
| no |
33. Can we have pictures of vault and dock door target installation sites (allowing us to dial in the hardware / mounting / positioning of fixed readers)?
No; that was the reason for the site visit.
| 34. If pictures cannot be provided, can you provide measruements and drawings? how wide is dock door? How tall is dock door? Can antennas be installed at ground level facing inwards or is overhead only install position? Same question for vault doors – where is there space to install fixed readers/antennas at vault doors? |
| No, that was the reason for the site visit. |
| 35. How far part are vault doors from one another? Can you provide drawings of the vault indicating where the doors are positioned? |
| No |
| 36. Can we have a floorplan of sites (presume not, but have to ask)? |
| No |
37. System must include Tech Support via phone, email, and/or help desk with response time within 24 hours.
QUESTION – Is this based on standard support hours, M-F, standard business hours? What constitutes a response?
Normal business hours. Response is human to human conversation regarding the problem and establishing a path forward.
38. The NMMC will provide the contractor with the inventory on an Excel spreadsheet upon contract award.
QUESTION – Will NMMC associate RFID tags with firearms using proposed RFID software solution, and attach those tags, or is expectation that RFID vendor will include labor hours to be on-site for enough time to associate RFID tags with firearms within proposed solution?
Vendor will encode all data on RFID tags and will work with NMMC staff to correctly place encoded tags on the appropriate firearms.
| 39. If vendor is expected to make tag to firearm association, are there any requirements from UMMC to vendor personnel to handle firearms? |
| This will be done in coordination with NMMC staff. |
| 40. Is a wired network/ethernet also available at each site, or must the entire system run only on Wi-Fi with fixed readers communicating over Wi-Fi? |
| Wifi |
| 41. How many years of maintenance and support should be included with initial RFP proposal? Example – 1 year (standard and will be included), 3-year, 5-year or more. We understand that there can be no charges beyond the initial purchase of the software for software license subscriptions renewals, 3rd party data storage, or reoccurring fees as it pertains to the software as it is delivered as part of the RFQ, but it is impossible to know at the time the RFQ if there will be updates to the operating systems of the laptop/tablet, server, or mobile device referenced in the RFQ that could possibly require updates to the proposed software to maintain the required functionality. |
| o | What is the intended process for maintenance and support? Annual renewal, bank of support hours, purchase support as needed, etc.? |
| o | Or is the assumption that the solution will go unsupported without maintenance and support after the first year? |
| See Q30 |
| 42. How are firearms handled/stored during movement? Are they in a case, carried by hand, on cart, stacked on pallet, etc.? If inside a case, is the case made of metal or other RFID interfering materials? Is the case like a common firearm case that has some metal, but is primarily made of non-RF blocking materials such as plastics or resins? |
| See Q31 |
| 43. What testing has been completed to ensure tag readability in this environment? Tag line of site, inlay type, and tag size are some of the major factors that would need to be confirmed to verify RFID effectiveness. |
| None, within the vault space, reader will never be farther than 3 feet from the intended tag to be read. |
44. For the hardware there is mention that it is “required for data entry, reports, and database management”, as it pertains to the software can you expand on any other required features other that what is listed in the RFQ. Are there any specific requirements beyond the following assumed items?
Data Entry:
i. Add/Edit/Delete firearms within system
ii. Schedule expected movement of firearms.
Reporting:
iii. History of firearm movement (firearm, location, expected flag, date/time)
· Current Firearm Inventory with Last Known Location
Quarterly, by-serial-number inventory reports, monthly barrel count reports.
45. For the email and/or SMS alert that are mentioned in the RFQ, can we leverage NMMC SMTP Server for Email Alerts? If not, is there a suggested way that they requirement be accomplished?
There is no NMMC server for this requirement
| 46. Will the chosen vendor have remote access to the server for updates and support, should maintenance and support be renewed/purchased beyond the first year? |
| There is no server, but we would expect remote updates, system patches, and regular maintenance to be performed as part of the package. |
| 47. Has an RFID feasibility study or any onsite RFID testing been completed? If a feasibility study has already been completed, can you post a copy of the report that would have been part of the deliverables? If not, may we propose an RFID feasibility study to be the first phase of this project. This would allow an RFID Engineer to come on site to do testing with multiple fixed and mobile readers and antennas, as well as different types of tags. There would be a cost for this type of assessment, but it would narrow down the RFID portion of this project and would give potential bidders more precise information to formulate a response |
| No feasibility study has been done. |
| 48. Will your team be supplying the necessary network equipment (e.g., router or switch) to support the static RFID readers, or should we include this in our proposal? |
| This should be included. |
| 49. Are there any specific limitations or restrictions related to drilling or mounting hardware within the facility? |
| No |
| 50. Would you require an RFID printer as part of the proposed solution? |
| Wifi access to the network printer is acceptable. |
| 51. Should the RFID system aggregate and report inventory data across both buildings at each location? |
| yes |
| 52. What specific data fields—and how much information—should be programmed into each RFID tag? |
| Serial Number, Accession Number, NSN and Location Code. |
| 53. Does the software need to comply with STIG requirements? Could you clarify any Information Assurance (IA) or Risk Management Framework (RMF) expectations? |
| No clarification available. |
| 54. Can you provide detailed floor plans for both locations to assist with system planning and coverage? |
| no |
| 55. Will automated alerts from the RFID system require emailing addresses ending in *.army.mil? |
| no, @usmcu.edu |
| 56. What are your data archiving policies and long-term storage requirements for RFID-collected information? (Laptop data can proliferate exponentially) |
| Data archiving policies are per SECNAC M-5210.1. External storage device would be ok. |
| 57. Will the RFID system need to integrate with any existing on-premise software platforms or databases? |
| no |
| 58. Given the availability of Wi-Fi in the facility, would you be interested in leveraging a mixed reality headset (e.g., HoloLens) to enhance asset tracking, inventory management, and real-time visibility? (Provides inventory, movement of asset visibility, and reports from anywhere) |
| no |
| 59. Would your team be open to a live demonstration of the technology?RFQ Requirement: "a. Alerts shall be sent to NMMC staff via email and/or SMS." Can additional clarification be provided regarding the need for being standalone if Alerts are needed? |
| No |
| 60. How often do the weapons move and the quantity of weapons at a time? |
| Usually 1-3, but for a new gallery install like we did last summer, it can be up to 100 or more. |
| 61. What type of containers (material, size, quantity) are the weapons moved in? |
| See Q31 |
| 62. How / what mode are the weapons relocated from the vehicle to the Museum? Humans, hand carts, bins, etc.. |
| See Q31 |
| 63. Is there any additional tracking considerations for the Museum regarding all ingress/egress points in the facility? |
| no |
| 64. Are there access restrictions to the weapons (authorized personnel) that needs to be taken into consideration for tracking purposes? |
| System access, yes. Weapons movement, no. |
| 65. Will the laptop and the RFID Sensors be on the same network at the Vault and the Loading Dock? |
| No, two separate wifi networks |
| 66. Will the laptop stay stationary at either location? |
| For the most part yes, although the ability to move it as needed is important. |
| 67. Will Ethernet connectivity or PoE be available for the RFID Sensors? |
| Wifi only |
| 68. Salient Characteristics # 3, page no 6 | What constitutes "authorization" to move a firearm? |
| Direction from the Arms & Armor Curator. | |
| 69. Salient Characteristics # 3, page no 6 | The requirement states, “The system shall have the ability to track firearm movements and schedule movements”. Can you please share more about the Scheduling of Movements? e.g., When are the items scheduled to be moved in relation to when they should be moved? Is the schedule in an automated system? How often are items moved? |
| The ability to plan movements by going into the system, clicking on the desired weapon serials and scheduling them for a move in advance gives us better flexibility in executing that movement. Items are rarely moved, but when installing new exhibits, or changing out existing exhibits, this will be a valuable tool. | |
| 70. Salient Characteristics # 1 c, page no 5 | What reports are you seeking? What do the reports need to contain? |
| Quarterly inventory reports, monthly barrel counts. | |
| 71. When does the Marine Corps anticipate awarding the business? Is the anticipated award prior to Sept. 30, 2025? |
| Once an acceptable solution has been identified; Yes. |
| 72. Salient Characteristics # 2, page no 6 | As long as data resides onsite, as required, is NMMC open to a FedRAMP Saas application, in support of the Cloud First/Cloud Smart directives, as part of the Federal Cloud Computing Strategy? |
| No, the intent is to keep this a standalone system off the MCBQ network. | |
| 73. Infrastructure Support: While the RFQ specifies that Wi-Fi access will be provided by NMMC, could you please clarify whether NMMC will also provide power and network drops where needed to support the RFID infrastructure at both project sites? |
| The intent is to keep this off the main MCBQ network as a standalone system. |
| 74. Data Flow Management: Could you elaborate on NMMC’s expectations regarding the flow of RFID data between the two sites? Specifically, how is this data intended to be managed using a single laptop, and are there any protocols or configurations already envisioned for this setup? |
| The vault is the primary site. Data from the museum will identify when new firearms arrive through the loading dock door and then scanned inventory data from the weapons on exhibit will update to both the museum and vault laptops. |
| 75. Server and Network Infrastructure: Will NMMC be providing the necessary IT server and network infrastructure to enable the collection and storage of RFID read event data across both locations? If so, could you provide details regarding the specifications or setup of this infrastructure? |
| No, this will be a standalone system not on the main network. |
| 76. Handheld Reader Requirements: Can you clarify whether a handheld RFID reader will be required at both sites simultaneously, or if one handheld unit will be sufficient to operate effectively between the two locations? |
| We want one handheld at each location. Moving weapons between the two locations is difficult enough with security requirements, etc. We don’t want to have to move a reader as well. |
| 77. Tag Encoding and Formatting Standards: Does NMMC have any established encoding schema or human-readable formatting standards that the selected Contractor will be required to follow for RFID tag programming and printing? |
| Priority data on the tags will be the weapon serial number, which will be a simple alphanumeric sequence. We do have unique location codes (ex. 3.2.10.1.1, indicating Building 3, Room 2, Row 10, Section 1, Shelf 1) that each weapon will need to be associated with as well. |
| 78. Purpose and Current State: Could you please provide insight into the primary objectives for implementing the RFID solution? Additionally, what is the current process in place for tracking or managing the relevant assets? |
| Inventories are currently conducted by hand and take on average 3 days for a team of 4 to complete. We do this quarterly, and so the addition of an RFID system will greatly reduce inventory time and increase our productivity. |
| 79. Firearm Transportation Process: How are firearms currently transported between the two sites (e.g., via open cart, caged cart, metallic cart)? |
| See Q31 |
| 80. Volume of Transported Firearms: On average, how many firearms are typically transported at one time between the two locations? |
| Usually 1-3, but for a new gallery install like we did last summer, it can be up to 100 or more. |
| 81. Under 1.a.: Is the provided Wi-Fi Local Area Network shared between the Arms Storage Building 2121 Rowell Road (Arms Room) and Loading Dock Door at 1775 Semper Fidelis Way (Loading Dock)? Are POE ethernet or electric outlets within 6’ of interior and exterior each Arms Room door and Loading Dock being provided by the government or should the Contractor provide? If Contractor provided, is plastic or metal conduit required? Is a Backup System with removable external storage required? |
| No, there are two separate Wifi networks, one at each location. |
| 82. Under 1.c.: Clarifying, this is a 2nd Tablet/laptop for data entry, reports and database management? |
| yes |
| 83. Under 1.d: Are gold image Windows 11 Operating System required since CAC Readers are required? Are CAC Readers required for each Mobile Computer or Tablet to secure these devices? |
| Just for the laptops. |
| 84. Under 3.a: Are any visual or audible alerts required at the Doors and Loading Dock Portals (e.g., green light for authorized, red light/buzzer for unauthorized) in addition to SMS or email alerts? |
| no |
85. Under 3: For any RFID tagged Checked Out assets from the Arms Room being returned through the Arms Room Doors, should they be Checked In or simply update the Location movement?
Yes, they should be checked in.
| 86. Under 4: Confirming a total of two hand-held RFID Readers/Scanners are required – one for Arms Room and one for Loading Dock? |
| Yes |
1. Under 5:
· For the RFID tag’s steel cable: Is crimp binding acceptable, requiring wire cutters for removal?
· For reduced cost, are encased RFID tags with reinforced holes and separate crimped steel cables acceptable?
· Would a smooth-edge steel band without plastic or rubber coating be accepted?
· For maximum economy, would a heavy-duty nylon zip tie with a minimum tensile strength of 50, 100, or 175 pounds be accepted?
· Given inherent limitations of RFID, are assets being grouped into Pelican cases or other packaging, and is the case or transport package intended to be RFID-tagged or manually scanned with handheld readers?
· Is the goal to track individual item movement, including through containers, without shielding the RFID tag?
· How are items typically transported past the Doors and Loading Dock (e.g., in cases, carts, or other carriers that may block RFID signals)?
· Are TAA-compliant RFID tags required, given this is a closed network and only identification numbers are stored in tag memory?
1- Yes 2- Yes 3- No – cannot have metal on metal 4- No zip ties 5- Movement out of the vault will be by pelican case 6- Yes 7- Pelican case or in the case of large weapons, without a case 8- In a case 9- No
| 87. Are any other sources of RFID interference other than was present during the Site Visit on May 8, 2025? |
| No |
(End of Q&A)
SECTION SF 1449 - CONTINUATION SHEET
SOLICITATION/CONTRACT FORM
The required response date/time has changed from 29-May-2025 11:00 AM to 12-Jun-2025 11:00 AM.
(End of Summary of Changes) image1.wmf