1\. How many tags are you looking to purchase?

The synopsis says \"twelve devices\" in the Deliverables section.  This
does not mean 12 \"systems\" each consisting of several devices. We want
12 tags and one scanner for prototype testing and technology
demonstration. 

2\. How large is the area in which you would like coverage?

We are soliciting independent (anticollision not required) RFID tags. 
The test material might be a flat slab 8\" square and 2\" thick.  One
tag would be bonded to one side of the material (which would have
thermocouples installed in it), and the TCs would be carefully attached
to the tag.  This assembly might be bonded onto some other structure. 
In any case, this system will be queried from the other side, i.e.
through 2\" of material. 

3\. Do you require any type of location accuracy/resolution?

No.  We will know where tags are located.  We only want the tag to
positively communicate its unique ID number and any data that were
taken.  In a future application, we might want anticollision tags that
need to work within 6\" to 9\" proximity of each other, but we would
still know where each tag was installed.

4\. Given the specific types of data in the RFQ, have any vendors been

evaluated thus far?

In FY00 we solicited a prototype device that was relatively large (2\"
size) and took data from only one thermocouple. Two years later, we feel
technology has advanced sufficiently to enable solicitation of an
improved 2nd-generation prototype. The following reference (pdf file
attached) to the synopsis contains information on previous work. 

F.S. Milos and J.B. Pallix, \"Wireless Subsurface Sensors for Health
Monitoring of Thermal Protection Systems on Hypersonic Vehicles,\"
*Structural Health Monitoring: The Demands and Challenges* (Proceedings
of the 3rd International Workshop on Structural Health Monitoring),
edited by F.-K. Chang, CRC Press, Boca Raton, FL, Sept. 2001, pp.
123-132.

[![](media/image1.jpeg){width="0.3333333333333333in"
height="0.3333333333333333in"}SHM3(sep01).pdf]()

5\. Do you also require any WLAN functionality?

No.

6\. Can the due date for quotation be extended?

Yes, the quotation due date has been extended to May 1, 2002. However
the work must be completed no later than 6 Months ARO.

7\. What do you expect to see along with the quotation? Do you want to
see a full technical proposal?

We need sufficient level of technical detail on what the vendor is
proposing to build (approx size, capability, frequency) so we can
evaluate whether or not the vendor understands the solicitation and can
meet or approach our goals.  Or if not, what other goals are more
reasonable and why. 

8\. For prototype testing, should the quoters meet all the three
demonstration specifications within 90 days? That is, should we
demonstrate a simple office use device, ground test device and a flight
experiment within 90 days?

The three cases provide a range of battery-drain scenarios.  We want one
device that can handle all three different scenarios.  If the vendor
thinks some cases are too severe for a device of the desired size,
please provide technical information on what should be achievable within
the size goal. 

Delivery has been revised to 6 months ARO.    

9\. What is the total amount of funds allocated for the deliverables?
Would we receive funding ARO or 90 days ARO?

Payments will be authorized by Performance-based Deliverables and
meetings, not dates. Please propose a Payment Schedule.

10\. What would be the ideal cost of each RFID tag and the scanner that
the deliverables should meet?

Protoype tags could be very expensive, because they are a custom-built
in a small quantity.  Future tags, if produced in a large quantity,
should cost less.

11\. May our final quotation be FAXED, and if so to which Fax number, or
does it need to go FEDEX or mail by the April 17 due date?

As stated in the Synopsis, your final quotation may be faxed to
Miin-Shiou Chen at 650-604-4357.

12\. If a firm has sufficient demonstrated electronics and software
development capabilities are the following requirements mandatory to bid
on this contract?

Yes.  (a) Active RFID tags: This is a specialized technology. A vendor
who has not previously produced products like this would have difficulty
in producing custom RFIDs. (b) Software to show what data these tags
acquired: Previously produced tags could not be used without software to
handle communications with them. Although a vendor might have previously
supplied RFIDs to a customer who developed and used their own software,
this procurement required both capabilities. 

13\. What would be required to substantiate sufficient capabilities in
electronics and software development if this is allowed?

See answer to question 12. 

14\. If a firm has submitted an application for 8(a) status and SDB that
may be approved before this contract is awarded is there a way to use
this information in our submission of a bid?

As required by the synopsis, please complete the representations and
certifications in 52.212-3.

15\. Will our status as Veteran-owned small business concern; emerging
small business; and Native American owned small business help us in this
contract?

This acquisition is subject to FAR 12, Acquisition of Commercial
Items-13, Simplified Acquisition Process. Also, as required by the
synopsis, please complete the representations and certifications in
52.212-3.

16\. What is the payment schedule for the contract?

See answer to Question 9. Recommended Schedule is: a design review
meeting to occur sometime between 1 and 3 months after award.  Half
payment after successful meeting.  The other half is paid after delivery
of product that meets requirements.

17\. There is a request for \"one thermocouple reference junction and
one independent temperature measuring device\" on the tag.  Is there a
total of 4 channels of data to be collected: 3 external K-type
thermocouples plus one CJ temperature?

 

Yes, there are four data channels.  Three are related to the
thermocouple temperatures, and one is related to the tag (reference)
temperature. 

18\. Can the thermocouples be attached to the RFID tag by soldering or
welding, or are connectors required?

 

Connectors, if available, are preferred because it will be difficult to
reliably solder 6 wires into a small area without damaging anything. 
This was a problem with a previous prototype. 

19\. Will the thermocouple accuracy requirement be approximately +/-10
degrees or closer to +/-1 degree?  This will make a big difference in
the size of the electronics.  Which will be more important, size or
temperature accuracy?

 

The size goal was specified in the synopsis, and there is not much room
for growth.  The accuracy can be estimated by each vendor; this will be
a technical evaluation criterion.  +/- 10 F is good for a TC that gets
very hot, but it is poor for a TC that sees little temperature change. 

Perhaps it is possible for the resolution to be variable, with the user
required to input the expected minimum/maximum temperature for each TC
after it is attached (there could be default values also).  The user
would input such estimates at his own risk (e.g., pegging the output).

20\. The maximum scan time should be the slowest sample interval (10
sec) times the storage capacity (2048 samples per channel), which is 340
minutes.  Is this what is intended?  Or is it 30 minutes as stated?

 

The maximum scan time is at least 30 minutes at 1-second data rate. 
That equals 1801 temperature measurements from each device.  The
synopsis listed 2048 points only because that is the next power of 2. 
If we take data less frequently, obviously either there is less data, or
we can take data for a longer period of time.  Alternatively, if we have
capability for 2048 points we can take data for a longer time at either
data rate. However, for all of the scenarios the heating period (during
which we actively take and store data) is less than 1 hour.

21\. When in use for longer than the maximum scan time, such as for 2
weeks during a flight, will the data be downloaded periodically?  Should
the slowest sample rate be specified as much slower than 10 seconds so
it can collect data continuously for two weeks?

 

Flight data cannot be downloaded until after the vehicle lands.  This is
a difficult scenario because the clock keeps running and the device must
periodically check temperatures.  Presumably data storage is initiated
by some function of a measured temperature whose occurence in time
cannot be predicted in advance.  For example, when the Shuttle launches
we don\'t know exactly when it will reenter.  So the tag needs to sit
quietly until it detects entry (perhaps by a near-surface temperature
suddenly rising).  Then the device actively takes and stores data (for
30 minutes or whatever time/frequency/number-of-points combination the
user specified). 

If a vendor thinks this scenario is impossible within the size
constraint of the device, please communicate why this is so.  Please
state what is possible, or alternatively suggest what change in
specifications is needed to enable this scenario.

22\. Will there be only the two ways specified for collecting data on
the RFID tag: continuous starting immediately, or continuous starting
when a temperature threshold is reached?

 

Flexibility in taking data is preferred.  On the ground, some scenarios
to start taking data are (note: we need to download the correct local
time from the PC to the tag):

    (a) at 2:15 pm today (i.e., user specifies a time)

    (b) 10 minutes from now (i.e., user specifies a time delay)

    (c) when TC #1 starts gets up to 150 F.  Please check this TC every

        10 seconds, but turn off after 2 hours if nothing significant
happens

        (i.e., user specifies a trip temperature for a particular TC and
some

        other parameters).

A complicated scenario, that a vendor might not want to handle, is:

    (d) some combination of the above. 

23\. The scanner size is specified as 30 cm square, but what volume can
it occupy?

 

We have used various commercial wand-type and gun-type RFID readers
(depending on RFID frequency) without any ergonomic problem.  The
scanner should not be ridiculously large in any dimension.  If required
to keep the scanner size or mass sufficiently low, there may be a small
electronics box between the scanner and the PC.