Questions and Answers.docx

DOCX document 22 KB Posted

Attached to
ITIPS Upgrade Telemetry Front-end Processor Systems Federal contract opportunity
Solicitation number
FA822823R0001
Issued by
Department of the Air Force Materiel Command Air Force Sustainment Center

About this file

This document contains questions and answers related to a federal solicitation for upgrading telemetry front-end processor systems. The solicitation seeks a contractor to provide a front-end processor capable of processing 32 channels of telemetry data and 1 channel of time in IRIG-B, IRIG-G, and GPS formats, and outputting IRIG-B, IRIG-G, and GPS time codes. The system must also support in-lock weighted, last-in-lock, and data merging modes for best source selection from combinations of PCM and TMoIP input channels. Additional requirements include fitting within a 4U rack space and supporting a demonstration of capabilities using sample PCM and Ethernet data streams provided by the Department of the Air Force during testing.

View the file

Other files for this federal contract opportunity

Other files attached to ITIPS Upgrade Telemetry Front-end Processor Systems, newest first.
File Type Posted
SOW Updated 8.16.23.docx DOCX document
Combined Solicitation-Synopsis 8.24.23.docx DOCX document
Combined Solicitation-Synopsis 8.21.23.docx DOCX document
SOW Updated 8.16.23.docx DOCX document
SOW Updated 8.16.23.docx DOCX document
Combined Solicitation-Synopsis 8.16.23.docx DOCX document
Questions and Answers.pdf PDF
SOW Updated.docx DOCX document
Combined Solicitation-Synopsis Updated.docx DOCX document
Questions and Answers.docx DOCX document
10182 - Combined Solicitation-Synopsis.docx DOCX document
CDRL A001 Operation and Maintenance Manual.pdf PDF
Solicitation - FA822823R0001.pdf PDF
Statement of Work.docx DOCX document
Show all 14

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

Questions and Answers

Question 1:

What kind of input signals are supplied to the system? Are both clock and data signals provided, and are the signals digital and reasonably free of noise? If digital signals are being provided, what signal levels can be expected – TTL, RS422, LVDS? This question tries to establish whether bits can be reliably captured digitally, potentially with clock recovery in the case of data-only signals, at the clock transitions, or whether some filtering or signal processing is required. Note that SoW item 2.1.8 appears to mention bit sync-related parameters, but otherwise the SoW does not explicitly call out bit sync capability as a requirement. Absent an explicit requirement, we need information about the signals in order to assess this.

Answer 1:

The input to the FEP is a digital PCM signal coming out of a TMoIP to PCM converter over approximately 3 feet of cable. The signal should be fairly free of noise. Both Data and Clock are present. The signal is TTL. Very minimal, if any at all, filtering or digital signal processing should be required.

Question 2:

SoW item 2.1.1 includes a requirement description for “32 Channels of Telemetry data, and, SoW item 2.1.2 includes a requirement description for “32 Channels of PCM data. Are those two requirement descriptions describing the same signal type?

Answer 2:

Section 2.1.1 is describing the total number of telemetry channels we need to process. Section 2.1.2 indicates one type of data we need to be able to process and Section 2.1.3 indicates a second type of data that we need to be able to process.

Question 3:

SoW item 2.1.7 includes a requirement description for three different operational modes, in-lock-weighted, last-in-lock, and data merging. May we have an expanded description of the operational expectations of these three modes? Which testing methodology will be used to demonstrate pass/fail compliance with this requirement?

Answer 3:

We understand that different companies use different algorithms to get the best data. This requirement is supposed to indicate that we would like some ability to determine how the system picks the best data and is not necessarily a requirement for a company to name their algorithms respectively. In general, we think “in-lock-weighted” indicates a data stream that is most often in-lock, “last-in-lock” would be a data stream that has most recently locked, and a “data merge” is an algorithm that attempts to create a unique best source stream that is not necessarily any of the incoming sources particularly but relies on selections from all the sources.

Again, we are not trying to dictate names for algorithms or how they should work, but we would like some control over how the best data output is configured so that we can adjust to different scenarios.

Question 4:

The introduction describes the current ITIPS systems as having the capability to monitor and analyse over 2,500 parameters, however, the requirements section (2.0) does not describe decommutation of parameters as a requirement. Is a decommutation capability a requirement for the new system, and if so, what parameter analysis is required?

Answer 4:

No decommutation is required at the Front-End Processor. ITIPS is more than just the FEP we are replacing. The best source output of the FEP will be sent to a decommutator for further analysis.

Question 5:

BDE supports in-lock-weighted, last-in-lock, data merging (bit vote), Question: Define “last-in-lock" and how it is different than in-lock weighted?

Answer 5:

We understand that different companies use different algorithms to get the best data. This requirement is supposed to indicate that we would like some ability to determine how the system picks the best data and is not necessarily a requirement for a company to name their algorithms respectively. In general, we think “in-lock-weighted” indicates a data stream that is most often in-lock, “last-in-lock” would be a data stream that has most recently locked, and a “data merge” is an algorithm that attempts to create a unique best source stream that is not necessarily any of the incoming sources particularly but relies on selections from all of the sources. Again, we are not trying to dictate names for algorithms or how they should work, but we would like some control over how the best data output is configured so that we can adjust to different scenarios.

Question 6:

Does this mean using any combination of PCM and TMoIP channels as an input for best source selection? If not, please define merging PCM channels with TMoIP channels.

Answer 6:

Yes, we would like the use any combination of TMoIP and PCM channels as inputs into the best source process.

Question 7:

What is the source of data for the output stream? Is it a mirror of one of the input channels? Is it one of the best sources of output channel? Is it comprised of parameter data? Is it something else?

Answer 7:

The source data would be either a mirror of the input streams, or any of the created best source streams.

Question 8:

Contractor sees these two requirements as an indication that bit synchronization is required for each PCM input stream, also implying these may be serial PCM data-only only inputs.

Please confirm bit syncs are indeed required for the PCM input streams as Contractor does not see any specific bit sync operational, or performance capabilities, detailed in the requirements.

Answer 8:

This was modified to hopefully remove bit sync requirements.

Question 9:

Section 2.5 covers “warranty”, which applies to hardware. So in section 2.4, is “technical support” the same as “software product support”? If not, then please clarify what is meant by “technical support”?

Answer 9:

Every vendor uses different terminology, but we think “software product support” would equal “technical support”.

Question 10:

Can you confirm that GPS: IRIG time code conversion capability is not a requirement for the 32-channel systems?

Answer 10:

This looks like an oversight in our solicitation and it will need to be added to serve as a replacement.

Question 11:

Is there a site demo test plan and is it available for review prior to visit? Can you provide a more detailed description of the test environment?

Answer 11:

The test plan/procedure is in work. A basic overview would be Wideband DRS8500 -> IMUX G2 -> Data Diode -> Computer running Omega NExT 3.0.0

Question 12:

During the site evaluation test will live or recorder file with PCM and Ethernet data be connected to the system? If so, what is the source of the data?

Answer 12:

A PCM recording played from a Wideband 8500 will be used for PCM data, and a IMUX G2 will be used for UDP CH10 data.

Question 13:

Is there sample data available, to use for early testing, and a description of the data, frame geometry, Bitrates, content within the data, etc.?

Answer 13:

Sample data used for testing is begin created, but four streams will be needed: Stream 1: 819.2kbps, 8192 bits/minor, no majors, F5CD00 sync. Stream 2: 1.6384Mbps, 8192 bits/minor, 2 major/minor. Stream 3: 500kbps, 1152 bits/minor, 8 minors/major, FAF320 sync. Stream 4: 1.6Mbps, 1600 bits/minor, 20 minors/major, FAF320 sync.

Question 14:

Do not see physical data replay requirement, so is one needed? Is it Single channel replay or multiple channel output replay?

Answer 14:

The front end processor will not need to replay PCM data.

Question 15:

What is the source device of the GPS timing signal that will be provided to the systems?

Answer 15:

We will bring an external puck-style GPS antenna and BNC cable to connect to the units under test.

Question 16:

What are the electrical properties of the signal?

Answer 16:

Not sure, but the cable is 100 feet long.

Question 17:

What connector type/gender is expected to be present on the selected system for receiving the GPS timing signal?

Answer 17:

The units will need a female BNC connector to receive the GPS signal.

Question 18:

Is this a separate piece of equipment in addition to the FEP, or is this stating that the FEP shall be capable of operating in this manner?

Answer 18:

Separate piece of equipment

Question: 19

There is no mention of this requirement in the SOW, is this equipment required?

Answer 19:

It is required in order to demonstrate some of the requirements, as we don’t have any RCC218-20 IP sources

Question 20:

Is this equipment required for the demo or just the final delivery?

Answer 20:

Demo only

Question 21:

Also, with respect to the requirement (2.1.11 of the SOW): Be capable of fitting in a 4U rack space with additional breakout boards if necessary. Is it required that the FEP and the PCM / TMoIP equipment fit in 4U of space or is additional rack space available for the PCM / TMoIP equipment added with Amendment 3?

Answer 21:

Only the FEP is required to fit withing 4U of rack space.

Question 22:

Will the customer supply IRIG or PTP Time Input to the PCM / TMoIP equipment, or should the contractor supply the time input?

Answer 22:

We will provide a GPS antenna connection, but can provide IRIG-G or IRIG-B if needed.

Question 23:

Is there additional rack space available for the time input equipment?

Answer 23:

We will have a rack for test, but the test equipment is not required to fit inside.

Question 24:

The combined solicitation changed as of 8/21/23. The first requirement (3.1) in the combined solicitation was changed to no longer include GPS / IRIG time conversion. The first requirement of the SOW (2.1.1) still includes the requirement for GPS / IRIG time conversion as of 8/21/23. Is GPS time I/O still required for the FEP?

Answer 24:

The combined solicitation has been corrected to match the SOW.

Question 25:

Requirement 2.1.1 of the SoW reads as:

2.1.1 Be capable of processing 32 channels of telemetry data and 1 channel of time in the following formats: IRIG-B-122, IRIG-G-142, and GPS time in. The unit must also output IRIG-B-122 and IRIG-G-142 time codes of the input GPS time.

Requirement 3.1 of the Combined Solicitation Synopsis reads as:

3.1 Be capable of processing 32 channels of Telemetry data plus 1 channel of time that supports both IRIG-B and IRIG-G sine wave amplitude-modulated formats.

Answer 25:

The combined solicitation has been corrected to match the SOW.

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