Inactive

RFI Number: N68335-20-RFI-0062 Classification Code: 7035 ADP Support Equipment NAICS Code(s): 334118 Optical Readers and Scanners REQUEST FOR INFORMATION PURSUANT TO FAR 15.201(e) – THIS IS A REQUEST ... RFI Number: N68335-20-RFI-0062 Classification Code: 7035 ADP Support Equipment NAICS Code(s): 334118 Optical Readers and Scanners REQUEST FOR INFORMATION PURSUANT TO FAR 15.201(e) – THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued 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. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Government is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised the U.S. Government will not pay 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. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. The Government will not be liable for or suffer any consequential damages for any proprietary information not properly identified. Proprietary information will be safeguarded in accordance with the applicable Government regulations. Failure to respond to this RFI does not preclude participation in any future associated RFP that may be issued. If a solicitation is released, it will be synopsized on the beta SAM website: beta.sam.gov. It is the potential vendor’s responsibility to monitor this site fort the release of any follow-on information. BACKGROUND/PURPOSE/TECHNICAL REQUIREMENTS Naval Air Systems Command (NAVAIR) PMA260 is soliciting information and comments from industry on its ability to provide a developmental application for a Commercial Off The Shelf (COTS) Ruggedized Barcode Scanner. The development application(s) should allow the user to download a comma separated values (CSV) text file containing inventory data from the personal computer (PC). Data in this file will be stored in the scanner allowing the barcode to be validated as the inventory is scanned. If the barcode is not found, then the user would enter the data from the data plate into the scanner. Additionally, the development application(s) should allow the user to upload the scanned and keyed information from the scanner. The barcode scanner shall have the following capabilities: Receive inventory csv file and update inventory verification data CSV file will have the following fields: Barcode, AMMRL Activity Identifier (AAI), Work Center, Part Number, CAGE, Equipment Serial Number, Status Code, Nomenclature, and UII. The scanned barcode file will contain the following fields: Barcode, AAI, Work Center, Part Number, CAGE, Equipment Serial Number, Status Code, Nomenclature, UII, Scanned Date, Keyed UII, Keyed Barcode, Keyed AAI, Keyed Work Center, Keyed Part Number, Keyed CAGE, Keyed Equipment Serial Number, Keyed Status Code, Keyed Notes, Keyed indicator. The user will have the option to replace the existing file or to update it. If the user selects replace, the inventory verification file will be emptied and all the records form the csv file will be written to the inventory verification file. Otherwise, if the user selects update, the inventory verification file will have the records from the existing file updated. Allow the user to enter the AAI and Work Center prior to scanning inventory. If the activity is small, they may only enter the AAI. Scan Inventory Barcodes or UII Barcodes will use the 3 or 9 symbology. Valid barcodes will be either 10 or 11 characters long. When a barcode is scanned, the inventory validation data for that barcode will be displayed on the scanner. If the inventory data displayed differs from the data plate, the user should be able to key in the correct information. For example, if the scanner displays an equipment serial number of 90003 but the data plate shows an equipment serial number of 90003A, then the user should be able to enter the correct equipment serial number and store it in the Keyed Equipment Serial Number field. The Keyed Indicator will be set if values are entered in any of the keyed fields. The user should be able to enter data in the Keyed AAI, Keyed Work Center, Keyed Part Number, Keyed CAGE, Keyed Equipment Serial Number, Keyed Status Code, and Keyed Notes. If the AAI or Work Center entered is different than the AAI and Work Center (respectively) in the inventory verification data, the values entered in the step above will be written to the keyed AAI or Keyed Work Center fields. If the UII field is blank but there is a UII label on the equipment, the user should be able to scan the UII. If the UII does not exist in the inventory lookup file, the user will be prompted to confirm that the UII should be associated to the barcode. If the user confirms, then the UII will be copied to the Keyed UII field and the keyed Indicator will be set. When an UII is scanned and found in the Inventory verification file, the scanner will display the inventory record. If the inventory data displayed differs from the data plate, the user should be able to key in the correct information. For example, if the scanner displays an equipment serial number of 90003 but the data plate shows an equipment serial number of 90003A, then the user should be able to enter the correct equipment serial number and store it in the Keyed Equipment Serial Number field. The “Keyed Indicator will be set if values are entered in any of the keyed fields. They user should be able to enter data in the Keyed AAI, Keyed Work Center, Keyed Part Number, Keyed CAGE, Keyed Equipment Serial Number, Keyed Status Code, and Keyed Notes. If the AAI or Work Center entered is different than the AAI and Work Center (respectively) in the inventory verification data, the values entered in the step above will be written to the keyed AAI or Keyed Work Center fields. The scanner should allow the user to scan a barcode or UII and display the inventory verification data, and then scan the next barcode or UII without requiring any user to click anything on the scanner. This would be the normal scanning process while everything is being scanned and no updates need to be recorded. This flow would only be broken when the user scans a barcode or UII that is not found in the inventory data or the user wants to correct the inventory data displayed on the scanner. If the barcode scanned does not exist in the inventory data, the user will be expected to enter the Part Number, CAGE, Serial Number, Status Code and the values would be stored in the Keyed Part Number, Keyed CAGE, Keyed Equipment Serial Number, and Keyed Status Code fields. The UII field can be scanned into the Keyed UII field. The Keyed Indicator would be set. If the UII scanned does not exist in the inventory data and the previous item scanned was a barcode, the user will be prompted to see if the UII should be associated with the previous barcode scanned. If the user confirms, the UII will be stored in the Scanned UII field for the previously scanned barcode. Otherwise, the user will be prompted to enter the Part Number, CAGE, Serial Number, Status Code and the values would be stored in the Keyed Part Number, Keyed CAGE, Keyed Equipment Serial Number, and Keyed Status Code fields. The Keyed Indicator would be set. When a barcode or UII is scanned and exists in the Inventory Verification Data, the record will be updated so that the Scanned Date reflects the current date. When the status code field is updated, the only values are A1, A2, A3, A4, B1, C1, F1, F2, F3, F4, and F5. If the AAI and/or work center does not match what’s in the inventory verification file, the keyed in value will be added to the Keyed AAI and/or Keyed Work Center. Create Scanned File. After the inventory has been scanned, the user will need a process to create a scanned file. The scanned file will contain all the records from the verification file that have a date value in the Scanned Data field. The scanned file should be a CSV file that contains the following fields: Barcode, AAI, Work Center, Part Number, CAGE, Equipment Serial Number, Status Code, UII, Scanned Date, Keyed UII, Keyed Barcode, Keyed AAI, Keyed Work Center, Keyed Part Number, Keyed CAGE, Keyed Equipment Serial Number, Keyed Status Code, Keyed Notes, Keyed Indicator. Download Barcode. A process will be needed to allow the user to download the scanned barcode file from the scanner to the PC. The user would need to select the location of the data file on the PC. This should be PC-based software that initiates the data download. Scanner should connect to the PC via a docking station. (WIFI is not allowed at many Fleet activities and therefore we will not be pursuing a WIFI solution.) Camera Capability: User needs to be able to disable the capability to take pictures so if scanners are used in a secure location then the picture taking capability can be disabled. Otherwise, the camera feature may be useful to take pictures of data plates or inventory while conducting the inventory. Since many of the Fleet users are familiar with Android, an Android based scanner that allows scans from an arm’s length away is required. Scanners would need to be ruggedized, have a pistol grip for taking inventory, and a docking station for communicating with the PC. Scanners will be required to be certified for use on USMC, NMCI, and CANES networks. RESPONSES Requested Information Section 1 of the response shall provide administrative information, and shall include the following as a minimum: Organization name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and name and e-mail of designated contractual point of contact. Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUB Zone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business). Section 2 of the response shall provide technical information, and shall include the following as a minimum: Interested parties shall respond with existing capabilities or products that meet all or a subset of the aforementioned attributes. Reponses that include information detailing potential tradeoffs or alternative solutions is encouraged. Respondents should provide a detailed description of the following characteristics of their solution in their submission: Production lead time for each major component, ensuring items with the longest lead time are identified Unit Price List of existing Certifications and Standards Licenses and air time requirements Reliability Data/ Test Results (mean time between failure (MTBF) information and mean time between demand (MTBD) per component) Air Time Services (available providers, units, global coverage areas, describe plans) (if applicable) Projected end of life (EOL) date Minimum economic order quantity (if applicable) Total quantity of units sold to date Date of delivery of first unit Date of delivery of most recent unit Any available discounts Describe warranty options Built-In Test and Built-In Test Equipment (BIT/ BITE) (calibration/ measurement/ traceability) (if applicable) Describe training/ technical materials Provide a functional block diagram of the product/ system, describing all inputs and outputs of external systems Describe how each major component is to be mounted Provide a list of the recommended spare parts for each major component of the product/ system Provide screenshots of the key operational screens for the primary user device, with a brief explanation of each screen Describe the Operating/ Technical characteristics for each major component: Dimensions (height x width x depth) Weight, in pounds AC/DC power requirements (voltage/ current while in operation and stand-by modes) Batteries: types and estimated battery life (if applicable) Environmental protections/ military standard ratings (water resistance, electromagnetic interference (EMI) certifications, shock/ vibration certifications, overvoltage, overcurrent, airworthiness certifications, etc.) Operating and storage temperature limits (maximum and minimum) (Celsius) Humidity range limits, in Relative Humidity (RH) (operating & non-operating) Frequency Ranges (MHz) and RF output power for each frequency band (if applicable) Signal Types of all inputs and outputs: format (Ethernet, audio, video, etc.), signal levels, quantities of each, and purpose of each signal Encryption/ decryption capabilities (if applicable) Identify the operating systems, if any, to include current revision information System test and diagnostic capabilities Input and output connector(s) descriptions Type of antenna connections (if applicable) Describe additional Navigation data interfaces Transmit RF power levels for each frequency range Channeling (analog, digital, etc.) Tunability (kHz steps) OTAR capability Method of configuration (front panel or external device such as a PC) Data at Rest capabilities (capacity, storage method, encryption capabilities, etc.) Number of loadable Common Key References (CKR) or Physical Identifier References (PID) Description of how radio is controlled remotely Methods to perform manual override of channel and power assignment Airworthiness data and documentation including any certifications What category/categories of the ITAR's (Traffic in Arms Regulation) United States Munitions List (USML) and/or the EAR's (Export Administration Regulation) Commercial Control List (CCL) apply to the system/subsystem being purchased? If applicable and able, respondents shall include a list of Department of Defense (DoD), Department of Justice (DoJ) or Department of Homeland Security (DHS) programs of record that currently employ their solution. It would be helpful if a sponsor POC for each program, with email address and phone number could be identified. The Government is interested in receiving vendors’ price lists for items they believe meet the need in this RFI. Supplying price data does not imply a contractual obligation and must be provided and marked as PRICE DATA. Respondents should include a list of authorized distributors. Respondents are requested to provide their estimated time it would take to submit a proposal After Request for Proposal release. HOW TO RESPOND Interested parties are requested to respond to this RFI with a PDF Document Format. Responses shall be limited to 10 pages and submitted via e-mail to the Contract Specialist, Sara Baye at Sara.Baye1@navy.mil The Contracting Officer, Eric Waterman, shall also be copied on email submissions at eric.waterman@navy.mil. Proprietary information, if any, should be minimized and must be clearly marked. Product specifications, sketches, or listings of authorized distributors will not count toward the page limitation. Responses are due no later than 20 Days after posting. Responses to this RFI will not be returned. Respondents will not be notified of the result of the review. If a solicitation is released, it will be synopsized on the beta SAM website: beta.sam.gov. It is the potential vendor’s responsibility to monitor this site for the release of any follow-on information.