20RJM40_sol_0002_att1.pdf

PDF 406 KB Posted

Attached to
REGENERATIVE BATTERY TEST SYSTEM
Solicitation number
N0016420RJM40
Issued by

View the file

Other files

File Type Posted
20RJM40_SOL_0003.pdf PDF
20RJM40_sol_0002.pdf PDF
20RJM40_SOL_0001_att1.pdf PDF
20RJM40_SOL_0001.pdf PDF
20RJM40_SOL_att1.zip ZIP file
20RJM40_SOL.pdf PDF

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

Attachment 3

1. Question:

In regards to the technical requirement of paragraph 1.1 of the SOW in solicitation N0016420RJM40, is the battery to be tested going to be a single battery pack made up of 40-48 cells, or is it 40-48 individual battery cells that will need to be tested simultaneously? In other words, will the test system need to consist of just a single test channel or 48 separate test channels?

Answer:

The battery to be tested is going to be a single battery pack made up of 40-48 cells. The Battery Test System needs to consist of just a single test channel.

2. Question:

The pre-solicitation (back in May timeframe) stated 270 Calendar days after receipt of funded order. I now see 154 days in the more recent solicitation.

Can you confirm if this change was made appropriately, and if so, for what reason this deadline has been changed?

Answer:

The solicitation has been changed from 154 days to 270 Calender days after receipt of funded order to be in accordance with the synopsis.

3. Question:

The requirements identify that the Battery Test System communications and control actions are accomplished utilizing LabVIEW drivers. Do you have any details on the specific driver protocol?

Answer:

The drivers are different based on which instrument you are communicating with. They are SCPI and communicate over TCP/IP over a private network.

4. Question:

Does the LabVIEW system act as the GUI and Test Automation System or is it only managing the logic and algorithms to run the test cycle?

Answer:

The LabVIEW application runs on the cRIO and controls all automated aspects of the testing (instrument control, logic and algorithms, datalogging, relays, etc.). The GUI is separate but interacts with the Labview seamlessly to the operator.

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