RESPONSE TO QUESTIONS INDUSTRY DAY F049SSFR.pdf

PDF 136 KB Posted

Attached to
AIRBORNE DATA RECORDER
Solicitation number
FA2823-10-R-0022
Issued by

About this file

RESPONSES TO QUESTIONS FROM INDUSTRY DAY

View the file

Other files

File Type Posted
Amendment 1-ADR.pdf PDF
DD254-ADR-c.pdf PDF
Delivery Info-ADR.doc DOC document
TRD- V1.2-ADR.pdf PDF
ADR CONFIGURATION 3 Compliancy Matrix.pdf PDF
FA2823-10-R-0022-ADR-.pdf PDF
ADR CONFIGURATION 4 Compliancy Matrix.pdf PDF
ADR CONFIGURATION 2 Compliancy Matrix.pdf PDF
ADR ATP 7-1-2010 .pdf PDF
DD254-ADR.pdf PDF
ADR CONFIGURATION 1 Compliancy Matrix.pdf PDF
Show all 11

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

REQUIREMENT QUESTIONS & COMMENTS Response

2.2 ADR Hardware Configurations

1. What is the intent of this contract? Is it to serve as a general procurement vehicle for all division of the DOD to obtain tested IRIG 106 CH 10 compliant hardware or is it specifically for project specific instrumentation? 2. If a product is not ready at the time of the initial testing but will be ready for testing in the future, will there be an opportunity to test and add hardware to the contract in the future. What are the mounting constraints? (ARINC

404 type or DZUS Rails compatible)

The intent of the contract is to meet 46 TW and 846 TSS requirements. Contracts will be awarded for required configurations. The 846 TSS will adapt installation to equipment purchased. Products need to be final and meet threshold requirements.

a. Configuration #1 (300 Mbps Continuous Sustained Data Rate). The ADR shall be less than or equal to 7.5 inches wide, 10 inches long, and 4.5 inches tall, exclusive of connectors, control knobs, eject mechanism, and memory access door.

If hardware exist that can meet the requirements except for size, will hardware be considered if it does not meet certain threshold requirements? Can the dimensions be made an OBJECTIVE? The requirement is as stated.

b. Configuration #2 (160 Mbps Continuous Sustained Data Rate). The ADR shall be less than 6 inches wide, 8.5 inches long, and 4.5 inches tall, exclusive of connectors, control knobs, eject mechanism, and memory access door. 2 PCM, 8 1553, 3 Video, 1 Ethernet, 1 16 PP 194 Can the dimensions be an OBJECTIVE? The requirement is as stated.

c. Configuration #3 (700 Mbps Continuous Sustained Data Rate). The ADR shall be less than or equal to 4.5 inches wide, 6 inches long, and 3.5 inches tall, exclusive of connectors, control knobs, eject mechanism, and memory access door. 2 Video, 2 Ethernet, RMM, Link Can the dimensions be an OBJECTIVE? The requirement is as stated.

d. Configuration #4 (200 Mbps Continuous Sustained Data Rate). The ADR shall be less than 6 inches wide, 6.5 inches long, and 5 inches tall, exclusive of connectors, control knobs, eject mechanism, and memory access door. 1553, Video, Ethernet, RMM Link Can the dimensions be an OBJECTIVE? The requirement is as stated.

REQUIREMENT QUESTIONS & COMMENTS

3.1 Recorder Firmware Configuration

2. As a threshold the ADR shall have software utility provided to configure, upload and/or communicate with the ADR to only have commands or features related to the IRIG106 Chapter 10 standard. a. As an objective the ADR shall allow firmware updates from the RMM as denoted by this TRD

The Eglin developed ATP terminal application is widely accepted and used by the Government, is it expected for the vendor to develop an equivalent tool?

Section 3.1‐2 specifies recorder firmware and loading requirements. This section does not specify recorder configuration requirements.

3.2 Operational Requirements

5. As a threshold any processing performed on the stored data by the ADR (e.g., for the purposes of internal system nagement, error detection and correction (EDAC), physical frame formatting, etc.)

shall NOT be part of the data file or stored in any part of the storage media

Please provide further detail as to exactly what not is allowed? What is the specific intent of this requirement?

No Computer Generated data, format 0, user defined packets are allowed as specified by section 3.3.2 of this TRD.

8. As a threshold the ADR shall provide RMM recorded data access the same IEEE‐1394B 9 pin bilingual connector interface in section 3.2.6 of this document. It is NOT acceptable for any other RMM interface/data access port to be provided (USB, eSATA, Ethernet, etc).

If the recorder provides the required IRIG 106 mandatory features, why is it that provision of features that exceed the specification is not allowed? The requirement is as stated.

9 As a threshold the ADR shall provide a recorded data block size of 512K bytes. The 512K block sized shall be IAW IRIG106 Chapter 10 section 10.5, table 10.2 “Block Size” directory.

There is either a conflict or typo. In the GRS specification another size is specified: 1. As a threshold the GRS GUI shall provide access to an RMM for Reconstruction and support a block size of 512 bytes per block. AIT3 tapes have mandatory 32 kByte blocks. The “block size” entry in the STANAG directory supports multiple block size compatibility. What is the purpose for making the block size fixed? What is the rational for using different block sizes between the field in the directory and the SCSI block size? The initial intent of the standard was to have only one block size (the one retrieved by the SCSI inquiry command). Using different block size for the directory is not in compliance with STANAG 4575. Correction made , 512 bytes is the requirement.

REQUIREMENT QUESTIONS & COMMENTS

3.2 Operational Requirements

5. As a threshold any processing performed on the stored data by the ADR (e.g., for the purposes of internal system management, shall NOT be part of the data file or stored in any part of the storage error detection and correction

(EDAC), physical frame formatting, etc.)

Please provide further detail as to exactly what not is allowed? What is the Reference requirement of Computer generated Data

8. As a threshold the ADR shall provide RMM recorded data access the same IEEE‐1394B 9 pin bilingual connector interface in section 3.2.6 of this document. It is NOT acceptable for any other RMM interface/data access port to be provided (USB, eSATA, Ethernet, etc).

If the recorder provides the required IRIG 106 mandatory features, why is it that provision of features that exceed the specification is not allowed? The requirement is as stated.

9 As a threshold the ADR shall provide a recorded data block size of 512K bytes. The 512K block sized shall be IAW IRIG106 Chapter 10 section 10.5, table 10.2 “Block Size” directory.

There is either a conflict or typo. In the GRS specification another size is specified: 1. As a threshold the GRS GUI shall provide access to an RMM for Reconstruction and support a block size of 512 bytes per block. AIT3 tapes have mandatory 32 kByte blocks. The “block size” entry in the STANAG directory supports multiple block size compatibility. What is the purpose for making the block size fixed? What is the rational for using different block sizes between the field in the directory and the SCSI block size? The initial intent of the standard was to have only one block size (the one retrieved by the SCSI inquiry command). Using different block size for the directory is not in compliance with STANAG 4575. 512 Bytes is the requirement

REQUIREMENT QUESTIONS & COMMENTS

4.3 PCM Input 1. As a threshold the ADR shall provide PCM

input channels IAW with configurations as defined in section

2.2 of this document. Each PCM channel shall have a minimum sustained PCM data rate of one hundred bits per second (100 bps) and a maximum sustained PCM data rate of twenty million bits per second (20

Can 100 bps be an OBJECTIVE since it is an extremely rare occurrence that a user would utilize such a slow rate? Can the lower threshold be set to approx. 1 kbps or above? If not, can oversampling be used to capture bit rates below 1 kbps using a higher rate internal clock? NOTE: 100 bps would only be 10 bits per packet. 100 Kbps corrected

4.5 16PP194 Input 1. As a threshold the ADR shall provide 16PP194 input channels IAW with configurations as defined in section 2.2 of this document. 2. As a threshold the ADR shall provide internal isolation transformers to allow for transformer coupled aircraft bus interface, 18‐27 Vpp for RT and 0.86‐27 Vpp.

There is a typo at the end of the sentence 2. Looks like it is cut off. Corrected

4.6 Video/Audio Input 14. As an objective video that is

played back shall contain the same overlay time as that made in the recording.

None of the 4 configurations require video playback Shall this requirement be deleted ? Req in error and deleted

5.0 ADR Operational Requirements

5.1 Operational Modes

2. As a threshold the ADR shall provide the ability to start and stop recording in the ON mode. If recorder power is removed while in the ON mode, the recorder shall initiate a soft power down. No loss of data shall be encountered on a soft power down to include meeting IRIG106 Chapter 10 time packet interval requirements and Recording Index packet requirements.

If a battery is needed: what type of battery is allowed ?

Or alternatively, is it acceptable to write a root index every second? No Batteries are permitted

REQUIREMENT QUESTIONS & COMMENTS

4. As a threshold the ADR BIT shall consist of ADR start‐up BIT, periodic, and initiated BIT. BIT shall detect 90 percent of all failures or out‐of‐tolerance conditions and isolate 90 percent of all detected failures to the ADR. False BIT detection or reporting shall be less than one in 1500 flight hours. BIT shall not be affected by normal system transients, power turn‐off or turn‐on, and shall not indicate a BIT failure for transient out‐of‐tolerance conditions. BIT results shall be reported via MIL‐STD‐1553 data bus. The ADR shall provide an indication of BIT status on the ADR. The indicator shall be a light emitting diode or other solid state device.

Can this requirement be moved to an objective? If not, how will the vendor be required to verify this requirement? Requirement is as stated

5.2 Discrete Command and Control

1. As a threshold the ADR provide discrete input and outputs IAW IRIG106 Chapter 10 section 10.7. The following table is a list of the required discrete inputs and outputs:

Event Input

There is a conflict with this requirement and the IRIG 106 CH 10 standard: There is no Event Input in Chapter 10 section 10.7. This is a specification requirement.

2.c “Recording Event Definition” attributes and “Recording Event” attributes shall be reserved for MIL‐STD‐1553 .EVENT commands as described in this TRD.

There is no clear requirement in this TRD for MIL‐STD‐ 1553 command and control or RT behavior This part of the requirement shall be removed ? Rrequirement clarified.

3. As a threshold the “Record” input discrete shall overwritten by a .STOP command.

This requirement is in conflict with IRIG 106 CH 10 standard. Req deleted

8. As a threshold the ADR discrete output (Fault, Erase, Record) shall provide a path to ground when active true.

The text is OK, but the drawing indicates that the discrete outputs are galvanically isolated from the recorder ground. Chapter 10 says: Control and Status Lines. Five contacts for discrete control and five lines for indicating status shall be provided. Grounding a control line (or causing the indicator line to go to ground) referenced to the recorders ground completes the circuit to activate a function as shown in Figure 10‐112.

Drawing is shown for reference. Drawing deleted to avoid confusion

11. As a threshold ADR erase output indicator state conditions; erase shall be indicated for the following conditions:

This requirement is not following the Chapter 10 standard? The requirement conflicts with Chapter 10:

Erase shall flash during erasing not during recorder initialization. Copy and Paste error in the requirement? Requirement is as stated

5.4 ADR Configuration

2. As a threshold the ADR setup source shall be configured using IRIG106‐09 Chapter 9 Video Data Type Attributes in the RCF:

“Video Data Type Attributes in the RCF ” ? Is this a cut and paste error. Corrected in TRD

5.5 Input Recording

2. As a threshold the ADR shall provide IRIG106 Chapter 10

RTC time tagging of recorded data to within 100 microseconds of external IRIG‐B time input.

This requirement is inconsistent with 4.1 where accuracy is better than 10 microsec. Ref updated TRD

REQUIREMENT QUESTIONS & COMMENTS

5.6 Internal or External RMM

1. As a threshold the ADR RMM shall be designed for compliant operation as a Class II IEEE‐1394 device, 45 Watts (8‐30VDC). It is not permissible to utilize an external power supply or multiple IEEE‐1394B 9 pin bi‐lingual connectors for

RMM power. This is a conflict‐is it 45 W or 12 W ? Requirement is as stated

4. As a threshold the ADR RMM recorded data capacity shall be sufficient to record an aggregate minimum data rate of three hundred (300) mega bits/sec for four (4) hours.

Which configuration is concerned by this requirement ?

300 Mbps * 3600 * 4 = 540 GBytes Is the intent of this

TRD to have only large capacity RMMs ? Missing table

2. As a threshold the internal RMM shall be installed in the ADR and shall be accessible within the constraints of the current videotape cassette recording systems.

What are the constraints of current videotape cassette recording systems? No tools

11. As a threshold the ADR RMM shall be no larger than seven (7.0”) inches by three and one half inches (3.5”) by one and one half inches (1.5”).

Due to the limited size for the specific configurations, if necessary, is it acceptable to have different size RMMs for the different configurations.

5.9 Time Sources and Synchronization 1. As a threshold

requirement the ADR shall have an external AC modulated IRIG B and IRIG‐G input. The time input is defined in section

4.1 of this document.

In section 4.1 (2) 2. As a threshold the ADR shall synchronize to an external AC modulated IRIG‐B or ‐G input IAW IRIG200‐04. This section conflicts with 5.9 (B and G). Additional message content definition is required for the time format. Ref TRD

4. As an objective the ADR shall time synchronize to the three monitored (MT mode) MIL‐STD‐1553 bus messages when enabled on the channel.

Please provide description of the 3 monitored messages?

Description of V‐X\TMS\FMT seems to be truncated in the table Not Required

6.0 ADR Serial Interface Requirements.

Comment: .IRIG‐106 is not in standard, (no dash in command) SANITIZE command seems to be missing? Corrected in TRD

8.0 Physical Characteristics

8.4 As a threshold the ADR shall perform satisfactorily from ‐

40 Deg C to 72 Deg C under the temperature‐altitude provided the below figure.

The figure associated to this requirement mandates ‐ 54°C to +95°C which is in contradiction with the text ‐40°C to 72°C Please clarify The requirement is ‐40 deg C

8.6.5 As a threshold the ADR shall be designed such that

direct exposure to rain environment shall not degrade performance.

Is it possible to make this an OBJECTIVE? If not, what is the standard? Requirement is as stated

10.0 Aircraft Power Interface

10.1 […] The maximum steady state power required shall not exceed 1 amp at 28 VDC.

Assuming this is 28W, which configurations does the

28W limit apply ? TRD updated

10.2.7 Lightning Protection. Lightning protection shall be

verified by a combination of analysis and test. Compliance with Electrostatic Discharge (ESD) protection requirements shall be verified by test and analysis. Analysis shall verify adequate control measures have been incorporated into the design, such as use of transient absorbing devices, series resistance, or proper electrical grounding and bonding.

Testing shall be performed to a minimal 4 kV to pins and equipment enclosure and casings, to verify compliance with Constellation requirements, through exposure to standard electrostatic discharge waveforms. Tests or analysis may be performed to document ESD susceptibility at higher levels up to 15 kV level.

Can this be set as an OBJECTIVE? This is typically more of an operational requirement and is traditionally not mandated for test recorders.

Recorders from this contract may be used in an operational environment

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