TRD-GRRS- V1.2.pdf

Ground Recorder and Reconstruction System Technical Requirements Document

(TRD)

Version Date: 7 June 2010

Document Identifier: Ground Recorder and Reconstruction System V1.2 TRD.doc

Version: 1.2

Prepared By:

846 TSS/TSI

Eglin, AFB, FL 32542

850-882-2537 berard@eglin.af.mil

Ground Recorder and Reconstruction System TRD V1.0

Contents

1.0 Introduction

1.1 Purpose

1.2 Scope

1.3 References

1.3.1 Key Acronyms

1.3.2 Key Documents

2.0 Descriptions

2.1 GRS Terms and Definitions

2.2 GRS Hardware

2.3 GRS Software/Firmware

2.3 GRS Operations

3.0 GRS Interface Requirements

3.1 Mechanical

3.2 Electrical

3.3 Operator

3.4 Data

4.0 GRS Input/Output Requirements

4.1 Time Input

4.2 Time Output

4.3 PCM Input

4.4 PCM Output

5.0 GRS Operational Requirements

5.1 COTS Media Interface and Access

5.2 RMM Interface and Access

5.3 Tape Media Interface and Access

5.4 Input Recording

5.5 Output Reconstruction

5.7 Remote Interface

Revision Record

REVISION

DATE

REVISION

NUMBER

BRIEF SUMMARY OF CHANGES

05/06/09 1.0 Initial Release TRD.

06/02/10 1.1 Section 2.2.1.f: Add AIT-3 tape drive to GRS hardware.

Section 2.4: Number error, was 2.3 changed to 2.4.

Table 4.1: Changed time input termination to 75Ω.

Table 4.2: Changed time output termination to 75Ω.

Sections 4.3.1 & .1.a: Changed PCM input minimum bit rate to 100 kilo bits per second (100 kbps).

Sections 4.4.1, .1.a & .3: Changed PCM output minimum bit rate to 100 kilo bits per second (100 kbps).

Section 5.4.1.a: Changed from “Format 2” to “Format 1”.

Section 5.4.1.d: Changed from “Format 3” to “Format 2”.

Section 5.4.1.e: Changed from “Format 4” to “Format 3”.

Sections 5.4.1.c, 5.4.10.c, 5.5.14 & 5.5.16: Removed “unpacked”.

1.0 Introduction

1.1 Purpose

The purpose of this Technical Requirements Document (TRD) is to provide the functional and technical specifications for an IRIG106-07 and -09 Chapter 10 compliant Ground Recorder and Reconstruction System (GRS). This system will be utilized by engineers, technicians, and data analysts of the 46th Test Wing (TW), Air Armament Center (AAC), Eglin AFB in support of Department of Defense (DoD) developmental and operational flight test requirements related to a variety of weapon system platforms.

1.2 Scope

This TRD establishes requirements for performance, development, and test of a GRS.

The terms “threshold” and “objective” are in bold type, followed immediately by the stated requirement. Threshold requirements are the minimum required to be provided.

Objective requirements are defined as the ultimate goal, and depend on technology advancements. Additional information (sometimes stated in directive terms) is considered amplifying data.

The term “Shall” is used to dictate the provision of a functional capability; to denote something that is required.

The term “Will” is used as a statement of fact; to cite items that the operational environment is to provide to the capability being specified.

1.3 References

This section contains a list of reference material used by this TRD.

1.3.1 Key Acronyms

The following acronyms and definitions are used within this document.

CSV Comma Separated Value DTF Data Transfer File GUI Graphical User Interface IAW In Accordance With ICD Interface Control Document IRIG Inter-Range Instrumentation Group MRF Modified Recording File ORF Original Recording File PCM Pulse Code Modulation RCC Range Commanders Council RCF Recorder Configuration File RMM Removable Memory Module RTC Relative Time Counter SCSI Small Computer Systems Interface TG Telemetry Group TRD Technical Requirements Document TMATS Telemetry Attributes Transfer Standard XML eXtensible Markup Language

1.3.2 Key Documents

The documents listed in this section, hereunder, form a part of this specification to the extent invoked by specific reference in other paragraphs of this specification. In the event of conflict between the documents referenced below and the contents of this specification, the content of this specification shall be considered a superseding requirement.

RCC IRIG 106-07, -09

Telemetry Standards

Chapter 4 PCM Standard

Chapter 6 Digital Cassette Helical Scan Recorder/Reconstructor, Multiplexer/Demultiplexer, Tape Cassette, and Recorder Control and Command Mnemonics Standards

Chapter 8 Digital Data Bus Acquisition Formatting Standard

Chapter 9 Telemetry Attributes Transfer Standard

Chapter 10 Digital Recording Standard

DoD Standards

IEEE Standards

1394B-2002 High Performance Serial Bus – Amendment 2

802.3-2005 LAN/MAN CSMA/CD Access Method

EIA Standards

ICD’s

2.0 Descriptions

2.1 GRS Terms and Definitions

The following are GRS terms and definitions which will be used throughout this TRD:

1. “IRIG106”: refers to the IRIG106-07 and -09 released standards followed by the applicable chapter reference.

2. “Reconstruct” or “Reconstruction”: reconstruct the data contained within the defined packets during playback to their original timing and signal characteristics:

a. Output PCM channel data to TTL or differential signals.

b. Output Time channel data to IRIG-A, -B, or -G amplitude modulated signal.

3. “Record” or “Recording”: record an ORF from PCM and IRIG time inputs.

4. “Archival” or “Archive”: produce a DTF on Tape Media or a mounted NTFS volume on the GRS from one (1) or more ORF’s on a RMM or one (1) or more ORF’s and or MRF’s from a mounted NTFS volume on the GRS.

5. “Retrieval” or “Retrieve”: produce one (1) or more ORF’s and or MRF’s from a DTF on Tape Media or a mounted NTFS volume on the GRS.

6. “COTS Media”: any recording media (such as hard disks, solid state drives, RAID, and JBOD) that is ready-made and available for sale to the general public and is NTFS formatted.

7. “COTS Media Interface”: any recording COTS Media interface (such as PATA, SATA, SCSI, IEEE-1394, USB, Ethernet) that is ready-made and available for sale to the general public.

8. “Tape Media”: a tape cartridge from an AIT-3 tape device which contains a DTF and has a SCSI interface.

9. “CH10 Publish or “CH10 Publishing”: Ethernet data broadcast which complies with IRIG106 Chapter 10 section 10.3.11.

2.2 GRS Hardware

1. The GRS will be a self-contained standalone desktop or rack mountable unit and will be installed in environmentally controlled room that will utilize the GRS for recording data to disk, reconstruction data to electronic signals from a RMM, a tape or COTS Media, distributing data to Ethernet and down loading the data over a network. The GRS will provide the following capabilities:

a. Local GUI operator interface.

b. Remote GUI operator interface.

c. RMM IEEE-1394B interface (data and power) with 9 pin bilingual connector.

d. 1000baseT Ethernet interface.

e. SCSI interface to local Tape Media.

f. AIT-3 tape drive.

g. COTS Media interface to local storage media.

h. USB 2.0 External COTS Media Port.

i. RS-422 and TTL PCM Outputs.

j. Amplitude modulated IRIG-B time output.

k. RS-422 and TTL PCM Inputs.

l. Amplitude modulated IRIG-B time input.

2.3 GRS Software/Firmware

1. As a threshold the GRS shall have only one (1) software/firmware configuration which shall be IRIG106 Chapter 10. It is not permissible for the software/firmware to be provided within the GRS that allows the system to be configured or operate in a mode other than IRIG106 Chapter 10.

2. GRS software/firmware will consist of a self-contained program to support local GUI operator interfaces and to support the IRIG106 Chapter 10 Digital Recorder Standard which allows:

a. Recording to COTS Media compliant with IRIG106 Chapter 10 section 10.10.

b. Recording to ORF’s compliant with IRIG106 Chapter 10 section 10.11.

c. Reconstruction from an RMM, COTS Media, and Tape Media compliant with IRIG106 Chapter 10 section 10.5, 10.9, 10.10, section 10.11.

d. Reconstruction from of DTF’s, ORF’s, and MRF’s compliant with IRIG106 Chapter 10 section 10.11.

e. Recording Event marking.

f. CH10 Publish directly from compliant IRIG106 Chapter 10 ORF on an RMM’s and ORF or MRF on COTS Media IAW IRIG106 Chapter 10 section 10.10.1.c.

g. CH10 Publish directly from IRIG-B time input and PCM inputs IAW IRIG106 Chapter 10 section 10.10.1.c.

h. GRS setup operations.

i. Status and health monitoring.

3. GRS software will consist of a self-contained Microsoft Windows software application program to support remote GUI operator interface the IRIG106 Chapter 10 Digital Recorder Standard for:

a. Recording to COTS Media compliant with IRIG106 Chapter 10 section 10.10.

b. Recording to ORF’s compliant with IRIG106 Chapter 10 section 10.11.

c. Recording Event marking.

d. CH10 Publish directly from compliant IRIG106 Chapter 10 ORF on an RMM’s and ORF or MRF on COTS Media IAW IRIG106 Chapter 10 section 10.10.1.c.

e. CH10 Publish directly from IRIG-B time input and PCM inputs IAW IRIG106 Chapter 10 section 10.10.1.c.

f. GRS setup operations.

g. Status and health monitoring.

2.4 GRS Operations

1. The GRS will Record time and multiple PCM streams. The GRS will provide data monitoring and CH10 Publish capabilities while in or out of Record mode or while in Reconstruct mode. The GRS will Reconstruct time and multiple PCM streams from an ORF on a RMM, an ORF on COTS Media, a MRF on COTS Media or a DTF on Tape Media. The GRS will be configured and controlled locally with a GUI, or remotely via Ethernet and a GUI hosted on a Microsoft Windows PC.

2. When GRS’s are connected to an Ethernet network they shall be configurable and controllable from a central location or multiple remote locations requiring no local operator actions. Recorded data access and transfer shall also be conducted across the Ethernet network requiring no local operator actions. These and other requirements will be defined in detail in later sections of this document.

3.0 GRS Interface Requirements

1. As a threshold the GRS shall consist of four (4) types of functional interfaces;

mechanical, electrical, operator and data.

3.1 Mechanical

1. As a threshold a GRS self-contained rack mountable unit mechanical interface shall be no larger than a 19” EIA Rackmount unit. Maximum depth of the GRS shall be 30 inches. The mechanical interface if required for an external GRS user interface shall be a no larger than 1U EIA for display, keyboard and mouse unit.

2. The GRS self-contained standalone desktop does not have any mechanical requirements.

3.2 Electrical

1. As a threshold the GRS electrical interface shall consist of power, remote communications, and input/output signals. Remote communication, input/output signal interfaces shall be defined throughout this document where it applies to specific functionalities and requirements.

2. As a threshold the GRS rated input power shall be 100-240V AC at 50-60Hz.

Maximum AC power draw shall be 10 amps or less.

3. As a threshold the GRS shall provide a minimum of one (1) 1000BASE-T gigabit Ethernet (1 GigE) internal interface and a RJ45 connector for Cat 5 cable connection.

4. As a threshold the GRS shall provide a minimum of one (1) IEEE-1394B internal interfaces with a 9 pin bilingual connector. The port shall provide one

(1) amp at 12 volts DC power to the RMM via an IEEE-1394B cable with 9 pin bilingual connectors.

3.3 Operator

1. As a threshold the GRS operator interface shall consist of a GUI for local operations. Operator interfaces shall be defined throughout this document where it applies to specific functionalities and requirements.

2. As a threshold the GRS operator interface shall consist of a Microsoft Windows GUI for remote operations. Operator interfaces shall be defined throughout this document where it applies to specific functionalities and requirements.

3. As a threshold the GRS operator interface software application program for remote operations shall be capable of being installed on and executed from a Microsoft XP Professional 32 bit host operating system.

4. As a threshold the GRS operator interface software application program for remote operations shall be capable of being installed on and executed from a Microsoft XP Professional 64 bit host operating system.

5. As a threshold the GRS operator interface software application program for remote operations shall be capable of being installed on and executed from a Microsoft Vista Ultimate 32 bit or 64 bit host operating system.

a. As an objective the GRS operator interface software application program for remote operations shall be capable of being installed on and executed from a Microsoft 7 Ultimate 32 bit or 64 bit host operating system.

6. As a threshold the GRS operator interface software application program for remote operations shall be capable of installation and execution from an Administrator account.

7. As a threshold the GRS operator interface software application program for remote operations shall provided on-line software application program operations and help manual files. These shall be suitable for printing to hardcopy.

8. As a threshold the GRS system shall provide manuals to include GRS wiring interface diagrams and connector pin-outs.

3.4 Data

1. As a threshold the GRS data interface shall provide a minimum of two (2) removable internal COTS Media Microsoft Windows NTFS formatted drives.

Each internal COTS Media drive shall have a minimum capacity of 500GB and a COTS Media Interface.

2. As a threshold the GRS data interface shall provide one (1) AIT-3 Tape Media with a SCSI interface.

3. Contain a minimum of one (1) IEEE-1394B internal interface port. The port shall provide one (1) amp at 12 volts DC power to the RMM via a single IEEE- 1394B cable with 9 pin bilingual connectors.

4. As a threshold the GRS data interface shall provide a minimum of one (1) GigE adapter.

4.0 GRS Input/Output Requirements

4.1 Time Input

1. As a threshold the GRS shall provide one (1) time input channel. Time input shall be concurrent with each PCM input channel.

2. As a threshold the GRS shall synchronize to an external AC modulated IRIG A, B or G input IAW IRIG200-04.

a. As an objective requirement the GRS shall accept an external 1 PPS input.

b. As an objective the GRS shall synchronize to a GPS UTC time source.

The source shall be a GRS internal GPS receiver.

3. As a threshold the GRS shall support the following signal characteristics for time channel input:

Input Signal Amplitude Modulated IRIG-A, -B, or -G

IAW IRIG200-04

Input Levels 0.2 to 10Vpp

Input Termination / Coupling 75Ω / AC (Capacitor)

Input Over Voltage Protection ±11V

Input Synchronization Accuracy

IRIG-A < 1 Microsecond

IRIG-B < 10 Microseconds

IRIG-G < 1 Microsecond

Table 4.1 – Time Input Signal Requirements

4. As a threshold the GRS shall provide a BNC time input connector.

4.2 Time Output

1. As a threshold the GRS shall provide one (1) time output channel. Time output shall be concurrent with each PCM output channel.

2. As a threshold the GRS shall produce an external AC modulated IRIG-B output IAW IRIG200-04 from recorded data playback.

3. As a threshold the GRS shall support the following signal characteristics for the time channel output:

Output Signal Amplitude Modulated IRIG B IAW

IRIG200-04

Output Levels Any fixed level between 0.5 to 10Vpp

Output Termination / Coupling 75Ω / AC (Capacitor)

Output Over Voltage Protection ±15V

Output Synchronization Accuracy

IRIG-A < 1 Microsecond

IRIG-B < 10 Microseconds

IRIG-G < 1 Microsecond

Stability and Drift of the Internal Time Code with No Signal

Stability: +10 ppm

Drift: + 5 ppm per year

Table 4.2 – Time Output Signal Requirements

4. As a threshold the GRS shall reconstruct recorded time data to the accuracy of the IRIG time format.

5. As a threshold the GRS shall provide a BNC time output connector.

4.3 PCM Input

1. As a threshold the GRS shall provide four (4) PCM input channels each with a minimum sustained PCM data rate of one hundred kilo bits per second (100 Kbps) and a maximum sustained PCM data rate of twenty million bits per second (20 Mbps). The PCM inputs shall be concurrent with the Time input channel.

a. As an objective the GRS shall provide eight (8) PCM input channels each with a minimum sustained PCM data rate of one hundred kilo bits per second (100 Kbps) and a maximum sustained PCM data rate of twenty million bits per second (20 Mbps). The PCM inputs shall be concurrent with the Time input channel.

2. As a threshold the GRS shall provide NRZ-L and RNRZ-L 15 forward and reverse input for each channel IAW IRIG106 Chapter 4. Data that is de-randomized shall be recorded as NRZ-L.

a. As an objective the GRS shall provide a bit synchronizer input to each channel.

3. As a threshold the DRS shall provide differential RS-422 and single ended TTL for each PCM input channel. The differential RS-422 connectors with 120 Ω shall be tri-axial (Trumpeter 70/370 or equivalent) and TTL connectors shall be BNC with 75Ω termination.

4. As a threshold the GRS shall provide selection of differential RS-422 or single ended TTL for each PCM input channel.

4.4 PCM Output

1. As a threshold the GRS shall provide four (4) PCM output channels each with a minimum sustained PCM data rate of one hundred kilo bits per second (100 Kbps) and a maximum sustained PCM data rate of twenty million bits per second (20 Mbps). The PCM outputs shall be concurrent with the Time output channel.

a. As an objective the GRS shall provide eight (8) PCM output channels each with a minimum sustained PCM data rate of one hundred kilo bits per second (100 Kbps) and a maximum sustained PCM data rate of twenty million bits per second (20 Mbps). The PCM input shall be concurrent with the Time output channel.

2. As a threshold the DRS shall provide one (1) PCM programmable simulator for each PCM output channel that can be externally or internally routed to the DRS PCM input channels.

3. As a threshold the DRS shall provide NRZ-L output for each channel with corresponding zero (0) degree clock from a minimum sustained PCM data rate of one hundred kilo bits per second (100 Kbps) and a maximum sustained PCM data rate of twenty million bits per second (20 Mbps).

4. As a threshold the GRS shall provide differential RS-422 and single ended TTL for each PCM output channel. The differential RS-422 connectors shall be tri-axial and TTL connectors shall be BNC.

5. As a threshold the GRS shall provide selection of differential RS-422 or single ended TTL for each PCM output channel.

6. As a threshold the GRS PCM output bit rate accuracy and stability during any period of desired data shall not differ from the specified nominal rate by more than 0.1 percent of the nominal rate.

7. As a threshold the GRS PCM output jitter shall not exceed + 0.1 of a bit interval referenced to the expected transition time with no jitter. The expected transition time shall be based on the measured average bit period as determined during the immediate preceding 1000 bits.

5.0 GRS Operational Requirements

5.1 COTS Media Interface and Access

1. As a threshold the GRS GUI shall provide access to COTS Media and selection of one (1) ORF or MRF for Reconstruction.

2. As a threshold the GRS GUI shall provide access to COTS Media and selection of one (1) DTF.

a. As a threshold the GRS GUI shall present the directory volumes and files contained within the DTF.

b. As a threshold the GRS GUI shall provide selection of any ORF or MRF contained within the DTF.

5.2 RMM Interface and Access

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.

2. As a threshold the GRS GUI shall present the directory volumes and files contained within the RMM.

3. As a threshold the GRS GUI shall provide selection of any ORF contained within the RMM.

5.3 Tape Media Interface and Access

1. As a threshold the GRS GUI shall provide access to Tape Media for Reconstruction and support a block size of 32K (32,768) bytes per block.

2. As a threshold the GRS GUI shall present the directory volumes and files contained within the DTF.

3. As a threshold the GRS GUI shall provide selection of any ORF or MRF contained within the DTF for Reconstruction.

5.4 Input Recording

1. As a threshold the GRS shall provide Recording to a compliant IRIG106 Chapter 10 section 10.11 ORF on COTS Media containing the following IRIG106 Chapter 10 data types:

a. IRIG106 Chapter 10 section 10.6 Computer Generated Data Packets Format 1, Setup Record.

b. IRIG106 Chapter 10 section 10.6 Time Data Packets Format 1 from the time input as defined in section 4.1 of this document.

c. IRIG106 Chapter 10 section 10.6 PCM Packets Format 1 (IRIG106 Chapter 4/8) in packed, unpacked or throughput mode from any selected or all PCM inputs as defined in section 4.3 of this document.

d. IRIG106 Chapter 10 section 10.6 Computer Generated Data Packets Format 2, Recording Index shall be created for each time packet and event packet.

e. IRIG106 Chapter 10 section 10.6 Computer Generated Data Packets Format 3, Recording Event. Events shall be created locally from the

GRS GUI or remotely from the GRS Microsoft Windows GUI for remote operations.

2. As a threshold the GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 10 microseconds or less from external IRIG-B time input.

3. As a threshold the GRS shall provide IRIG106-09 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from external IRIG-A time input.

4. As a threshold the GRS shall provide IRIG106-09 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from external IRIG-G time input.

5. As a threshold the GRS shall provide IRIG106 Chapter 10 section 10.6 RTC time tagging of recorded PCM data to within 1 microsecond or less from all PCM input channels.

6. As a threshold the GRS shall provide an IRIG time input channel setup GUI.

The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS time input channel.

a. As an objective the GRS shall provide a 1 PPS time input channel setup

GUI.

b. As an objective the GRS shall provide a GPS time input channel setup GUI. The setup shall include GPS time offset correction entry.

7. As a threshold the GRS shall provide a PCM input channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS PCM input channels.

8. As a threshold the GRS shall provide a GUI to allow selection of a compliant IRIG106 Chapter 9 external TMATS file (*.tmt) to setup the time input channel and the PCM input channels. After setup of the time input channel and the PCM input channels from TMATS the operator shall be allowed to over-ride the settings from a GUI.

9. As a threshold the GRS shall provide an IRIG time channel data status display GUI. The display shall show IRIG time format, IRIG time lock status and IRIG time data. As a threshold status of IRIG-106 Chapter 10 packets (errors) and PCM status shall be provided.

a. As an objective the GRS shall provide a 1 PPS time channel data status display GUI. The display shall show 1 PPS status and 1 PPS indicator.

b. As an objective the GRS shall provide a GPS time channel data status display GUI. The display shall show number of GPS satellites acquired, GPS status and GPS time data.

10. As a threshold the GRS shall provide CH10 Publishing while Recording or while not Recording to the GRS Ethernet interface. The CH10 Publish shall containing the following IRIG106 Chapter 10 data types:

a. IRIG106 Chapter 10 section 10.6 Computer Generated Data Packets Format 2, Setup Record. The Setup Record shall contain the TMATS setup of the current recorder configuration and settings. The Setup

Record CH10 Publish rate shall be one per second and be enabled or disabled by the operator.

i. As an objective the Setup Record for CH10 Publish shall be externally selectable by the operator from an IRIG106 Chapter 9 TMATS file.

ii. As an objective the Setup Record CH10 Publish rate shall be selectable from once (1) per second, once per ten (10) seconds, or once per thirty (30) seconds.

b. IRIG106 Chapter 10 section 10.6 Time Data Packets Format 1 from the time input as defined in section 4.1 of this document.

c. IRIG106 Chapter 10 section 10.6 PCM Packets Format 1 (IRIG106 Chapter 4/8) in packed, unpacked or throughput mode from any selected or all PCM inputs as defined in section 4.3 of this document.

5.5 Output Reconstruction

1. As a threshold the GRS shall provide Reconstruction of IRIG106 Chapter 10 data from one of the following sources:

a. A compliant IRIG106 Chapter 10 section 10.11 ORF selected from an

RMM.

b. A compliant IRIG106 Chapter 10 section 10.11 ORF or MRF selected from COTS Media.

c. A compliant IRIG106 Chapter 10 section 10.11 ORF or MRF from a DTF on Tape Media.

2. As an objective the GRS shall provide Reconstruction of IRIG106 Chapter 10 data from one of the following sources:

a. A CH10 Publishing source from the GigE interface.

3. As a threshold the GRS shall be capable of automatically setting up channels for Reconstruction from the Setup Record packet TMATS attributes from the selected data source defined in section 5.5.1.a-c of this document. The operator shall be allowed to over ride these settings.

a. As an objective the GRS shall be capable of automatically setting up channels for Reconstruction from the Setup Record packet TMATS attributes from the selected data source defined in section 5.5.2.a of this document. The operator shall be allowed to over ride these settings.

4. As a threshold the operator shall be capable of selecting an external TMATS file compliant with the IRIG106 Chapter 9 standard to over ride settings in the Setup Record Packet from the selected data source defined in section 5.5.1.a-c of this document.

a. As an objective the operator shall be capable of selecting an external TMATS file compliant with the IRIG106 Chapter 9 standard to over ride settings in the Setup Record Packet from the selected data source defined in section 5.5.2.a of this document.

5. As a threshold the GRS shall provide a PCM output channel setup GUI. The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS PCM output channels.

6. As a threshold the GRS shall provide the capability for the operator to select a lower PCM output bit rate for any enabled PCM channel from the original recorded PCM bit rate. Example: if recorded PCM channel bit rate oversampled a one (1) mbps PCM stream and recorded it at ten (10) mbps the GRS shall allow the operator to reconstruct the PCM channel at the original one (1) mbps rate.

7. As a threshold the GRS shall provide the capability to for the operator to select any four (4) enabled channels for Reconstruction from the selected data source defined in section 5.5.1.a-c of this document.

a. As an objective the GRS shall provide the capability to for the operator to select any eight (8) enabled channels for Reconstruction from the selected data source defined in section 5.5.1.a-c of this document.

8. As an objective the GRS shall provide the capability to for the operator to select any four (4) enabled channels for Reconstruction from the selected data source defined in section 5.5.2.a of this document.

a. As an objective the GRS shall provide the capability to for the operator to select any eight (8) enabled channels for Reconstruction from the selected data source defined in section 5.5.2.a of this document.

9. As a threshold the GRS shall provide an IRIG time output channel setup GUI.

The operator GUI interface at a minimum shall provide setup and configuration applicable to the GRS time output channel.

10. As a threshold the GRS shall provide a Reconstruction control panel operator interface for the main packet stream (all packets) from the selected data source defined in section 5.5.1.a-c of this document.

a. As an objective the GRS shall provide a Reconstruction control panel operator interface for each channel in the packet stream.

11. As an objective the GRS shall provide a Reconstruction control panel operator interface for the main packet stream (all packets) from the selected data source defined in section 5.5.2.a of this document.

a. As an objective the GRS shall provide a Reconstruction control panel operator interface for each channel in the packet stream.

12. As a threshold the GRS main packet stream Reconstruction control panel operator interface minimum functions shall be:

a. Display main packet stream absolute time. The format shall be HH:MM:SS where HH = hours, MM = minutes, and SS = seconds.

b. Stop; which shall stop the main packet stream.

c. Play; which shall play main packet stream @ x1.

d. Fast Play; which shall play main packet stream @ x2, x4, x8, x16, x32.

e. Slow Play; which shall play main packet stream @ x1/2, x1/4, x1/8, x1/16, x1/32.

f. Step Forward; which shall step the main packet stream forward.

g. Step Backward; which shall step the main packet stream backward.

h. Goto; shall position the Reconstruction point based on Time (UTC), File Position (bytes), or Index (if Recording Index packets are enabled).

13. As a objective the GRS individual channel Reconstruction control panel operator interface minimum functions shall be:

a. Channel Pause/Play; shall pause or play the channel. When Reconstruction resumes from paused it shall be automatically (no operator action required) re-aligned to the current Reconstruction point of the main packet stream.

14. As a threshold the GRS shall reproduce time and PCM during Reconstruction from the selected data source defined in section 5.5.1.a-c of this document. The PCM data shall be either packed, unpacked or throughput modes. The time and PCM data shall be sent to the time output defined in section 4.2 and the PCM outputs defined in section 4.4 of this document. Time output shall be concurrent with all GRS PCM output channels.

15. As a threshold the operator shall be provided a method to select or deselect any of the enabled PCM channels be sent to the PCM outputs defined in section 4.4 of this document.

16. As an objective the GRS shall reproduce time and PCM during Reconstruction from the selected data source defined in section 5.5.2.a of this document. The PCM data shall be either packed, unpacked or throughput modes. The time and PCM data shall be sent to the time output defined in section 4.2 and the PCM outputs defined in section 4.4 of this document. Time output shall be concurrent with all GRS PCM output channels.

a. As an objective the operator shall be provided a method to select or deselect any of the enabled PCM channels be sent to the PCM outputs defined in section 4.4 of this document.

5.7 Remote Interface

1. GRS remote GUI operator interface shall provide the following operations over the Ethernet interface and IAW IRIG106 Chapter 10 section 10.11.1.b and section 10.7.1.2:

a. Recording to COTS Media compliant with IRIG106 Chapter 10 IAW IRIG106 Chapter 10 section 10.10.2 and section 10.10.3.

b. Recording to ORF’s compliant with IRIG106 Chapter 10 section 10.11.

c. Recording Event marking.

d. CH10 Publish directly from compliant IRIG106 Chapter 10 ORF on an RMM’s and ORF or MRF on COTS Media IAW IRIG106 Chapter 10 section 10.10.1.c.

e. CH10 Publish directly from IRIG-B time input and PCM inputs IAW IRIG106 Chapter 10 section 10.10.1.c.

f. GRS setup operations.

g. Status and health monitoring.