Attachment_0002_-_Performance_Based_Specification_20180123_Revised.pdf

PDF 2 MB Posted

Attached to
ELECTRO-OPTIC / INFRARED / LASER DESIGNATOR PAYLOAD PRODUCTION AND SYSTEM SUPPORT
Solicitation number
W909MY17R0016
Issued by

About this file

Attachment 0002-Performance Based Specification-20180123

View the file

Other files

File Type Posted
A01-W909MY17R0016-0007-Amendment_0007.pdf PDF
Questions_and_Answers-Amendment_0007.pdf PDF
W909MY17R0016-0006-Amendment_0006.pdf PDF
Attachment_0001_-__Performance_Work_Statement_20180130_Revised.pdf PDF
W909MY17R0016-Amendment_0005.pdf PDF
Question_and_Answer-Amendment_0005.pdf PDF
Amendment_0004-Questions_and_Answers_20180124.pdf PDF
Amendment_0004-Questions_and_Answers_20180123.pdf PDF
W909MY17R0016-Amendment_0004.pdf PDF
Attachment_0008_Price_Model_Amendment_0004-22_Jan_2018.xlsx XLSX spreadsheet
Amendment_0004-Questions_and_Answers.pdf PDF
W909MY17R0016-Amendment_0003-20180118.pdf PDF
Amendment_0003_-_Consolidated_Questions_and_Answers_20180110.pdf PDF
Attachment_0008_Price_Model_Amendment_0003-17_Jan_2018.xlsx XLSX spreadsheet
Exhibit_A-CDRLs_20180108.pdf PDF
Attachment_0001_-__Performance_Work_Statement_20180104_Revised.pdf PDF
Attachment_0005_DD254.pdf PDF
Attachment_0002_-_Performance_Based_Specification_20180103_Revised.pdf PDF
W909MY17R0016-Amendment_0002.pdf PDF
Attachment_0008_Price_Model_2018-01-03_Revised.xlsx XLSX spreadsheet
alignment_tool-Response_to_Q._45.pdf PDF
Stanchion_rigid-Response_to_Q.45.pdf PDF
Amendment_0002_-_Consolidated_Questions_and_Answers_20180110.pdf PDF
main_plate-Response_to_Q.45.pdf PDF
CSP_camera_arm-Response_to_Q.45.PDF PDF
W909MY17R0016-Amendment_0001.pdf PDF
Questions_and_Answers-Amendment_0001.pdf PDF
Attachment_0002_-_Performance_Based_Specification_171117_FINAL.pdf PDF
Attachment_0006-Test_Plan-20171207.PDF PDF
Attachment_0001_-__Performance_Work_Statement_20171213.pdf PDF
0-W909MY17R0016.pdf PDF
Attachment_0009_Past_Performance_Questionairre.docx DOCX document
Attachment_0007_Integration_Schedule_Events.pdf PDF
Attachment_0005_DD254.pdf PDF
Attachment_0010_-_Non_disclosure_Agreement_(NDA)-for_ICD_W909MY-17-R-0016.pdf PDF
Attachment_0004-QASP.pdf PDF
Exhibit_A-20171212.pdf PDF
Attachment_0008_Price_Model_2017-12-13.xlsx XLSX spreadsheet
Industry_Day_at_Yuma_Proving_Ground_Questions_and_Answers-Final.pdf PDF
21-25_of_132.pdf PDF
71-75_of_132.pdf PDF
31-35_of_132.pdf PDF
A07_-_Pre-Proposal_Conference_-_Shadow_Industry_Slides_at_YPG.PPTX PPTX presentation
91-95_of_132.pdf PDF
Photos_Industry_Day-YPG_6-10_of_132.pdf PDF
106-110_of_132.pdf PDF
61-65_of_132.pdf PDF
101-105_of_132.pdf PDF
26-30_of_132.pdf PDF
Industry_Day_at_Yuma_Proving_Ground_Questions_and_Answers.pdf PDF
Show 40 more

Latest 50 of 86 listed here. See the rest on GovTribe.

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

FOR OFFICAL USE ONLY

UNCLASSIFIED

Performance Based Specification For the Payload Subsystem

For The RQ-7Bv2 TUAS

Version 3.0

23 January 2018

Program Executive Office Intelligence, Electronic Warfare, and Sensors

Project Manager Terrestrial Sensors

Product Manager Electro-Optic/Infrared Payloads

LTC KECIA M. TROY

Product Manager, Electro-Optic/Infrared Payloads

APPROVED BY: COL RODNEY O. BRIGGMAN

Project Manager, Terrestrial Sensors

(U) Distribution Statement D. Distribution authorized to the Department of Defense and U.S. DoD contractors only by specific authority of AR 380-5. Date of determination is approval date of this document. Other requests for this document shall be referred to Project Manager Terrestrial Sensors (TS), ATTN: Aberdeen Proving Ground, MD 21005.

FOR OFFICIAL USE ONLY

SUBMITTED BY

Adam Terio Date Technical Director Product Manager, EO/IR Payloads

CONCURRENCE

Kecia M. Troy Date

LTC, MI

Product Manager, EO/IR Payloads

Rodney O. Briggman Date

COL, MI

Project Manager, Terrestrial Sensors

1 SCOPE

1.1 Background. This document is a performance specification for the Electro-Optic /Infrared/Laser Designator (EO/IR/LD) payload subsystem to be used in the RQ-7Bv2 Tactical Unmanned Aircraft System (TUAS). It defines the payload functional requirements, environmental conditions, mechanical and electrical interfaces, and the technical performance requirements for the payload. The requirements herein are selected to ensure that the payload-related requirements of the Performance Specification for the Shadow RQ-7Bv2 Tactical Common Data Link (TCDL) Tactical Unmanned Aerial Vehicle (TUAV) System (R39489-00064A) will be satisfied.

For traceability purposes Requirements Baseline (R.B.) numbers have been inserted after each requirement. A summary of these requirements and how they are to be verified is included in the traceability matrix in Appendix A.

1.2 System Description. The Payload is a single Line Replaceable Unit (LRU) containing imaging sensors and lasers mounted inside a stabilized assembly. The assembly rotates in azimuth and elevation in response to commands from the platform avionics. The payload also contains electronics for processing, status reporting, and control:

a. Imaging Functions: Visible and Infrared (IR) cameras generating full motion video (FMV) at a variety of magnification levels.

b. Laser Functions: Laser Target Marker (LTM), Laser Range Finder (LRF), and Laser Designator (LD) functions, each function operator selectable.

The payload operates in the same environmental conditions as the aircraft. Aircraft are moved from one location to another in a modified High Mobility Multipurpose Wheeled Vehicle. Payloads remain installed in the aircraft while in transit. Payloads may also be removed from the aircraft and moved in transit containers by truck, rail, air, and ship.

1.3 Document Overview. This document was developed In Accordance With (IAW) MIL-STD-961E, 9 January 2014. The section structure is comprehensive and may include section titles for which there are no current requirements. In order to maintain the document structure, while supporting future requirement development, sections without requirements include the comment “This section is not applicable to this specification.”

1.4 Threshold and Objective Requirements. In this document, threshold and objective requirements are indicated using a (T) or (O) respectively at the end of the requirement.

Any requirements for which neither a (T) nor an (O) are indicated shall be considered threshold requirements. Threshold requirements must be met to satisfy this specification. Objective requirements indicate Government goals but are not mandatory.

2 APPLICABLE DOCUMENTS

2.1 General. The documents listed in this section are specified in Sections 1, 3 and 4 of this specification. This section does not include documents cited in other sections of this specification or recommended for additional information or as examples. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements of documents cited in Sections 3 and 4 of this specification, whether or not they are listed.

2.2 Government Documents.

2.2.1 Specifications, Standards, and Handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified herein.

Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

Table 2-1. Government Standards.

Document Number Title

FED-STD-595 Colors Used in Government Procurement

MIL-C-85285A Coating: Polyurethane, Aircraft and Support Equipment

MIL-HDBK-454A General Guidelines for Electronic Equipment

MIL-STD-209K Lifting and Tie Down Provisions

MIL-STD-210B Climatic Extremes for Military Equipment

MIL-STD-704E Aircraft Electrical Power Characteristics

MIL-STD-810F/G Environmental Test Methods and Engineering Guidelines

MIL-STD-1425A Safety Design for Military Lasers and Associated Support Equipment

MIL-STD-961E Defense and Program-Unique Specifications Format and Content

MIL-STD-648 Specialized Shipping Containers

ADS-37A-PRF

Aeronautical Design Standard, Electromagnetic Environmental Effects, Performance, Verification Requirements, 28 May 1996

MIL-STD-1472 Lasers and Associated Support Equipment

ANSI STD Z535.4-2002 American National Standard for Product Safety Signs and Labels

ANSI STD Z136.1-2014 Safe Use of Lasers

AR 40-501 Chapter 7, Physical Profiling

(Copies of these documents are available online at http://quicksearch.dla.mil.)

2.2.2 Other Government Documents, Drawings, and Publications. The following other Government documents, drawings, and publications form a part of this document to the http://quicksearch.dla.mil/ extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

Table 2-2. Government Documents.

Document

Number Title

RD-TE-97-01

Electromagnetic Environmental Effects Criteria and Guidelines for EMRH, EMRO, Lightning Effects, ESD, EMP, and EMI Testing of US Army Missile Systems, 31 Jan 1997

2.3 Non-Government Publications.

2.3.1 Specifications, Standards, and Handbooks. The following Non-Government standards form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

Table 2-3. Non-Government Standards.

Title

MISB STD 0902.6 Motion Imagery Sensor Minimum Metadata Set

MISB STD

0102.11

Security Metadata Universal and Local Sets for Digital Motion Imagery

MISB 0601.5 UAS Datalink Local Metadata Set

MISB 0604.2

Time Stamping and Transport of Compressed Motion Imagery and Metadata

MISB 601.5 UAS Datalink Local Matadata Set

(ANSI Standards are available online at https://www.ansi.org .)

(IEEE Standards are available online at https://standards.ieee.org .)

(SAE Standards are available online at https://www.sae.org/standards .)

(MISB Standards are available online at http://www.gwg.nga.mil/misb .)

2.3.2 Other Non-Government Documents, Drawings, and Publications. The following Non-Government documents, drawings, and publications form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

Table 2-4 Non-Government Documents.

Title

R70436-01231 “Interface Control Document for the ESM 313 Second Source Payload Shadow aircraft Payload Mechanical and Electrical ICD” July 2015.

2.4 Order of Precedence. Unless otherwise noted herein or in the contract, in the event of a conflict between the text of this document and the references cited herein, the text https://www.ansi.org/ https://standards.ieee.org/ https://www.sae.org/standards http://www.gwg.nga.mil/misb of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. REQUIREMENTS

3.1 Recycled, Recovered, Environmentally Preferable, or Biobased Materials.

Recycled, recovered, environmentally preferable, or biobased materials should be used to the maximum extent possible, provided that the material meets or exceeds the operational and maintenance requirements, and promotes economically advantageous life cycle costs.

3.2 States and Modes

3.2.1 Payload States. The payload shall have two states, Non-Operate and Operate.

(R.B.02)

3.2.1.1 Non-Operate State. The payload shall be in the Non-Operate State when the input power supply voltage is zero. (R.B.03) The payload shall be capable of transportation and surviving long-term storage (up to 1 year) and the non-operating environmental conditions in Section 3.9 while in the Non-Operate State. (R.B.04) The payload shall transition between states within a maximum time of 4 seconds. (R.B.389)

3.2.1.2 Operate State. The payload shall transition to the Operate State when power is available at the unit’s input with voltage IAW the range specified in Section 3.6.3 and the discrete power enable interface is in an active state (closed/short circuit condition).

(R.B.06) The payload shall transmit a response over the aircraft avionics interface with the command execution acknowledgement. (R.B.07) The payload will be in the Operate State and in Stow Mode for takeoff and landing.

3.2.2 Payload Modes. The payload modes are defined relative to the payload’s three major components: Gimbal, Sensors, and Data as shown in Figure 3-1. The Gimbal and Sensors are physical components which operate independently of one another and define the configuration and operation of the payload. The third component, Data, communicates information obtained by the Gimbal and Sensor components.

3.3 Gimbal.

3.3.1 Gimbal Line of Sight (LOS) Modes. Capability and performance requirements specific to these gimbal modes are contained in Section 3.3.2. The payload shall have the pointing stabilization modes as described in the following subsections. (R.B.08) The payload shall be in one pointing mode at a time. (R.B.09)

Figure 3-1. Payload Components and Capabilities.

3.3.1.1 Inertial Mode. The payload shall have an Inertial Mode. (R.B.10) While in this mode the Gimbal shall move the payload in order to maintain the LOS fixed relative to an inertial coordinate frame. (R.B.11) While in the Inertial Mode, the gimbal shall move relative to the inertial coordinate system if LOS commands are sent over the aircraft avionics interface. (R.B.12)

3.3.1.2 Stow Mode. The payload shall have a Stow Mode. (R.B.13) The payload shall transition to the Stow Mode when commanded to the System Standby Payload sub-state. (R.B.14) The factory default pointing position for Stow Mode shall be the position which best protects the payload during aircraft launch and landing. (R.B.15) The payload shall protect each sensor lens from foreign object damage when in the stowed position. (R.B.371)

3.3.1.3 Cage Mode. The payload shall have a Cage Mode. (R.B.16) In Cage Mode, the Gimbal moves to a specific pointing angle with reference to the airframe centerline.

This mode is typically used to give the operator a “pilot’s window view” on command.

The factory default pointing angle for Cage Mode shall be 0 deg (± 0.5 deg) in azimuth and -20 deg (± 0.5 deg) in elevation. (R.B.17)

3.3.1.4 Cage Config Mode. The payload shall have a Cage Config Mode. (R.B.18) Cage Config Mode shall allow the operator to modify the default azimuth and elevation Cage Mode pointing angles. (R.B.19)

3.3.1.5 Heading Hold Mode. The payload shall have a Heading Hold Mode. (R.B.20) In Heading Hold Mode, the payload shall remain at the most-recently commanded pointing angle (relative to the aircraft). (R.B.21) While in Heading Hold Mode, the Gimbal shall move when the payload receives LOS commands from the aircraft avionics interface. (R.B.22)

3.3.1.6 Scan Mode. The payload shall have a Scan Mode. (R.B.23) In Scan Mode the payload shall automatically scan a pre-defined azimuth and elevation window. (R.B.24)

3.3.1.7 Scan Config Mode. The payload shall have a Scan Config Mode. (R.B.25) Scan Config Mode shall allow the operator to modify the default azimuth and elevation scan settings. (R.B.26). Scan Config shall allow setting an azimuth scan window.

(R.B.46) The size of the window shall be selectable to a maximum of not less than 90 degrees about any reference azimuth point. (R.B.47) Scan Config shall allow setting the LOS scan speed to a maximum of not less than 10 degrees/second. (R.B.48)

3.3.1.8 Track Modes. The payload shall have Automatic Track Modes. (R.B.27) Automatic Track Modes are used to automatically hold the LOS on a target of interest.

Only one of the Automatic Track Modes will be active at a time. Automatic track modes are described in Section 3.3.2.6.

3.3.1.9 Geo-Point Mode. The payload shall have a Geo-Point Mode. (R.B.28) This mode shall command the LOS to an operator-defined geographic coordinate. (R.B.29)

3.3.1.10 Emergency Mode. The Payload shall enter an Emergency Mode when commanded by the aircraft avionics interface in the event of an emergency (i.e. flight termination). (R.B.30) The Emergency Mode will protect the payload to the maximum extent possible from a parachute deployment. The parachute is located directly aft of the payload. If the payload’s Stow Mode does not interfere with parachute deployment, it can be used as the Emergency Mode. The payload shall slew to its emergency position at the maximum slew rate independent of field of view. (R.B.31) The payload’s emergency mode shall be a factory setting or configurable via the maintenance port only. (R.B.32)

3.3.2 Gimbal Capabilities and Performance.

3.3.2.1 Field of Regard. The payload shall have a Field of Regard (FOR) at a maximum elevation angle of not less than 20 degrees above horizontal to a minimum elevation angle of at least 90 degrees with the ability to successfully track through nadir. (R.B.33) The payload FOR in azimuth shall be continuous. (R.B.34)

3.3.2.2 Azimuth and Elevation Orientation. The payload azimuth shall be equivalent in orientation and sense to the aircraft yaw (i.e., yaw is a rotation about a vertical axis with positive yaw moving the Line of Sight (LOS) from the nose toward the starboard wing).

(R.B.35) The payload elevation shall be equivalent in orientation and sense to the aircraft pitch (i.e., pitch is a rotation about a horizontal axis through the wings with positive pitch moving the LOS from the nose toward the upward vertical). (R.B.36)

3.3.2.3 Pointing Angle Resolution. The payload azimuth angle report shall be available in increments not greater than 100 µrad. (R.B.37) The payload elevation angle report shall be available in increments not greater than 100 µrad. (R.B.38)

3.3.2.4 Sensor LOS. When the payload elevation report is 0 degrees, the magnitude of the angle between the sensor LOS and aircraft longitudinal axis shall be not greater than 2 mrad. (R.B.39) When the payload azimuth report is 0 degrees, the magnitude of the angle between the sensor LOS and the aircraft longitudinal axis shall be not greater than 2 mrad. (R.B.40) When the payload is installed in the aircraft and the azimuth pointing angle reads 0 degrees, the sensor LOS shall be toward the aircraft nose. (R.B.41)

3.3.2.5 Tracking (Track Mode). The payload shall include an Automatic Video Tracker (AVT). (R.B.49) The AVT shall function with either IR or EO sensor video. (R.B.50) The AVT shall automatically keep the LOS on a target or scene of interest. (R.B.51) The payload shall have a Point Track Mode. (R.B.52) While in Point Track Mode the Gimbal will remain affixed to a target of interest. The payload shall keep the LOS centered on the area of a target or scene where the LOS was viewing just prior to the mode activation. (R.B.53) The payload shall report track quality status to the operator (Low, Medium, or High). (R.B.54)

3.3.2.5.1 Tracking Performance. The payload shall track targets with a pixel size of not less than 3 x 3 pixels and minimum contrast between the target and background of not less than 6%. (R.B.55) The payload shall maintain track lock when the magnitude of the LOS angular rate is less than 10 degrees/second. (R.B.56) The payload shall maintain track lock when the magnitude of the LOS angular acceleration is less than

0.15 degrees/second2. (R.B.57)

3.3.2.5.2 Track Loss Conditions. The payload shall display a visual indication to the operator upon entering a track loss condition. (R.B.58) The payload shall attempt to reacquire the target when track loss is sensed and the payload remains over the target.

(R.B.59) The payload shall continue to execute laser designator fire commands in the event that a track loss condition is encountered during laser designator fire. (R.B.61) The payload shall enter Inertial mode when track is lost and Track Prediction fails.

(R.B.62)

3.3.2.5.3 Track Sub-Modes. The payload shall have not less than four track sub-modes: Track Adjust, Track Search, Track Prediction, and Offset Track. (R.B.63) No more than one Track sub-modes shall be active at a time. (R.B.64)

3.3.2.5.3.1 Track Adjust Sub-Mode. The Track Adjust Sub-Mode shall allow the operator to move the target track gate to a different point of the target while maintaining track lock. (R.B.65)

3.3.2.5.3.2 Track Search Sub-Mode. The payload shall allow the selection of a secondary target without losing track of the primary tracking target when in Track Search Sub-Mode. (R.B.66)

3.3.2.5.3.3 Track Prediction Sub-Mode. The payload shall automatically transition to Track Prediction Sub-Mode in the event of a track loss. (R.B.67) While in Track Prediction Sub-Mode the payload shall attempt to reacquire track of the target for a time not greater than three seconds. (R.B.68)

3.3.2.5.3.4 Offset Track Sub-Mode. The payload shall allow the track gate to be positioned at a position other than the center of the image when in Offset Track Sub- Mode. (R.B.69)

3.3.2.5.4 Track Gate Control. The payload shall offer both automatic and manual track gate sizing. (R.B.70)

3.3.2.6 LOS Properties.

3.3.2.6.1 Drift Rate. The payload LOS drift rate shall be less than or equal to 25 degrees/hour after all drift calibration, payload initialization, and stabilization have completed. (R.B.71)

3.3.2.6.2 LOS Velocity and Acceleration.

3.3.2.6.2.1 Velocity (Slew Rate). While in sensor Wide Field of View (WFOV), the LOS slew rate shall increase from 0 degrees/second to a maximum of not less than 50 degrees/second using proportional control slew rate commands. (R.B.72) While in sensor Narrow Field of View (NFOV), the LOS slew rate shall increase from 0 degrees/second to a maximum of not greater than 10 degrees/second using proportional control slew rate commands. (R.B.73)

3.3.2.6.2.2 Acceleration. The maximum LOS acceleration shall be not less than 50 degrees/second2. (R.B.74)

3.4 Sensor Assembly.

3.4.1 Sensor States and Modes.

3.4.1.1 Electro-Optical Sensor (EO). The EO image shall be valid within 60 seconds after the payload enters the Operate State. (R.B.75)

3.4.1.1.1 Focus Modes. The EO sensor shall have manual and automatic focus modes.

(R.B.76) In manual focus mode, the focus shall adjust in response to user commands.

(R.B.77) In automatic focus mode, the focus shall adjust to optimize the image clarity without requiring user interaction. (R.B.78) The EO sensor focus mechanism shall have a near-to-far focus travel time of not greater than five (5) seconds. (R.B.79)

3.4.1.1.2 Adjustment Modes. The EO sensor shall have manual and automatic adjustment modes. (R.B.80) The default mode shall be automatic when the payload enters the Operate state. (R.B.81) In manual adjustment mode, the image brightness and contrast shall adjust in response to user commands. (R.B.82) In automatic adjustment mode, the image brightness and contrast shall adjust to optimize the image without requiring user interaction. (R.B.83) The time required to adjust the sensor from one limit of the brightness/contrast range to the other shall be not greater than five (5) seconds. (R.B.84)

3.4.1.2 Infrared Sensor (IR). The IR sensor shall meet the cool-down requirement in Section 3.4.2.5.2. (R.B.85) The IR sensor shall be sensitive in the wavelength between 3-5 microns. (R.B.86)

3.4.1.2.1 Focus Modes. The IR sensor shall have manual and automatic focus modes.

(R.B.87) In manual focus mode, the focus shall adjust in response to user commands.

(R.B.88) In automatic focus mode, the focus shall adjust to optimize the image clarity without requiring user interaction. (R.B.89) The IR sensor focus mechanism shall have a near-to-far focus travel time of not greater than five (5) seconds. (R.B.90)

3.4.1.2.2 Adjustment Modes. The IR sensor shall have not less than two adjustment modes: manual and automatic. (R.B.91) The default mode shall be automatic when the payload enters the Operate state. (R.B.92) In manual adjustment mode, the image gain and level shall adjust in response to user commands. (R.B.93) In automatic adjustment mode, the image gain and level shall adjust to optimize the image without requiring user interaction. (R.B.94) The time required to adjust the sensor from one limit of the gain/level range to the other shall be not greater than five (5) seconds.

(R.B.95)

3.4.1.3 Laser Target Marker (LTM).

3.4.1.3.1 Laser Target Marker States. The LTM shall have three states: Standby, Arm, and Fire as depicted in Figure 3-2. (R.B.96)

3.4.1.3.1.1 Default State. The payload shall default the LTM to the “Off State” when the payload transitions to the Operate State. (R.B.157)

3.4.1.3.1.2 LTM Standby State. In the Standby state: the LTM shall be capable of transitioning to the Arm state but prohibited from entering the Fire state. (R.B.97) The LTM shall transition from Standby to Arm (and reverse) within less then 2 seconds.

(R.B.391)

3.4.1.3.1.3 LTM Arm State. In the Arm state, the LTM shall be capable of entering either the Standby or Fire state. (R.B.98)

3.4.1.3.1.4 LTM Fire State. In the Fire state, the LTM shall commence firing; in this state, the LTM shall be capable of transitioning to either the Standby or Arm states.

(R.B.99)

Figure 3-2 Laser Target Marker States.

3.4.1.4 LRF. The LRF shall contain its own set of states and sub-states as depicted in Figure 3-3. (R.B.100) It shall be possible for the payload to be in the operate state while the LRF is in its non-operate (Off) state. (R.B.101) The following sections describe the states and sub-states of the LRF.

Figure 3-3. Laser Range Finder States and Sub-States.

3.4.1.4.1 LRF States. The LRF shall have an Off state and an On state. (R.B.102)

3.4.1.4.1.1 LRF Standby Sub-State. The LRF shall transition between the Off state and the On/Standby (State/Sub-state) state in not less than 1 second when commanded by the aircraft avionics interface. (R.B.103)

3.4.1.4.1.2 LRF Fire Sub-State. The LRF shall transition from the On/Standby (State/Sub-state) to the Fire Sub-state and commence firing the laser in not greater than 1 second when commanded by the aircraft avionics interface. (R.B.105) The LRF shall transition from the Fire Sub-state to the On/Standby (State/Sub-state) or Off state in not greater than 1 second when commanded by the aircraft avionics interface. (R.B.104)

3.4.1.5 Laser Designator (LD).

3.4.1.5.1 LD States. The LD shall contain its own set of states and sub-states.

(R.B.106) It is possible for the payload to be in the operate state while the LD is in its non-operate (Off) state. The following sections describe the states and sub-states of the LD. The LD cannot be in the On State without the payload being in either the Standby, Arm, or Fire substate. Figure 3-4 depicts the State Diagram for the LD.

Figure 3-4 Laser Designator States and Sub-States.

3.4.1.5.1.1 LD Off State. The LD shall be in the Off state when payload power is applied. (R.B.107) The LD shall remain in the Off state until the aircraft avionics interface commands the payload to apply power to the LD. (R.B.108) The LD shall transition to the Off state from the LD On state when commanded by the aircraft avionics interface. (R.B.109) The transition to the Off state shall be complete in not greater than two (2) seconds of receiving the command from the aircraft avionics interface. (R.B.110)

3.4.1.5.1.2 LD On State. The LD shall complete the transition from the Off state to the On state within two (2) minutes in ambient temperatures not less than 25 deg Celsius.

(R.B.111) The LD shall complete the transition from the Off state to the On state within four (4) minutes in ambient temperatures not less than 0 deg Celsius and not greater than 25 deg Celsius. (R.B.112) The LD shall complete the transition from the Off state to the On state within seven (7) minutes in ambient temperatures not greater than 0 deg Celsius. (R.B.113)

3.4.1.5.1.3 LD On Sub-States.

3.4.1.5.1.3.1 LD Standby Sub-State. The LD shall contain a Standby Sub-state. In the Standby Sub-state the designator is disarmed. (R.B.114) The LD shall transition from the Off state to the Standby Sub-state when commanded by the aircraft. (R.B.115) The LD shall be able to transition to the Standby Sub-state only when the payload is in the Operate state. (R.B.116)

3.4.1.5.1.3.2 LD Arm Sub-State. The LD shall contain an Arm Sub-state. (R.B.117) The LD Arm Sub-state shall prepare the laser for transition to the Fire Sub-state.

(R.B.118) The LD shall not fire in this Sub-state. (R.B.119) The LD shall transition from the Standby Sub-state to the Arm Sub-state in not less than one (1) second. (R.B.120)

3.4.1.5.1.3.3 LD Fire Sub-State. The LD shall contain a Fire Sub-state. (R.B.121) Upon entering the Fire Sub-state the LD shall commence firing. (R.B.122) In the event that the payload reaches a duty cycle or thermal limit, the LD shall cease firing and transition to the state or Sub-state most conducive to laser cooling. (R.B.123) In the event that the payload receives an abort command, the LD shall transition to the Arm Sub-state. (R.B.124) The LD shall remain in the Fire Sub-state only while firing commands are received from the aircraft avionics at a rate of at least eight (8) Hz.

(R.B.127) The LD shall transition from the Firing Sub-state to the Arm Sub-state in not greater than one (1) second when the firing command is not received at eight (8) Hz.

(R.B.126) The payload shall validate the firing command prior to acting upon the firing command. (R.B.128) The validation is accomplished via field range values, pulse characteristics, etc. The payload shall discard invalid firing commands. (R.B.129)

3.4 2 Sensor Capabilities and Performance.

3.4.2.1 Sensor Latency. The mean sensor latency shall be not greater than 60 milliseconds. (R.B.130) Sensor latency is defined to be the time lag between the end of sensor image collection to the output of the first pixel of the corresponding frame.

3.4.2.2 Image LOS / Boresight Accuracy. The angle between the IR LOS and the EO LOS shall be not greater than 2 mrad. (R.B.131) The magnitude of the angle between the horizontal axis of the EO image and the pitch axis to which the EO sensor is mounted (i.e., EO sensor rotational error) shall be not greater than one (1) degree.

(R.B.132) The magnitude of the angle between the horizontal axis of the IR image and the pitch axis to which the IR sensor is mounted (i.e., IR sensor rotational error) shall not be not greater than one (1) degree. (R.B.133)

3.4.2.3 Picture-in-Picture (PiP). The payload shall place image data from the EO sensor onto the image of the IR sensor and vice versa in response to operator command. (O) (R.B.134) The sensor shall have the ability to configure placement of the PiP, independently control the FOV, as well as match FOVs. (O) (R.B.125)

3.4.2.4 EO Sensor.

3.4.2.4.1 EO Sensor - Recognition. The EO sensor recognition requirement is per the Johnson Criteria. The assumed operational altitude is 8,000 ft AGL. The EO sensor shall supply a video output of sufficient quality to recognize, with 70% probability of recognition (T) 90% (O), a 3.5m x 3.5m target at a slant range of not less than 13 km (T), 35 km (O) given an N50 of 3 cycles on target, relative humidity of 90%, visibility of 23 km, and a target contrast of 40%. (R.B.135)

3.4.2.4.2 EO Sensor - Spectral Response Band. The minimum wavelength of the EO sensor spectral response shall be not greater than 400 nm. (R.B.136) The maximum wavelength of the EO sensor spectral response shall be not less than 900 nm in order to be capable of detecting the LTM output. (R.B.137) Alternatively the color sensor may have a maximum cutoff of no less then 700 nm provided that some other means is provided to image the LTM return. The EO sensor shall produce color imagery.

(R.B.138)

3.4.2.4.3 EO Sensor FOV. The EO sensor shall have a continuous optical zoom.

(R.B.139) The EO sensor shall have an electronic zoom capability of not less than 2x.

(R.B.374) The EO sensor optical WFOV shall be not less than 20 degrees (horizontal).

(R.B.140)

3.4.2.5 IR Sensor.

3.4.2.5.1 IR Sensor Recognition. The IR sensor recognition requirement is per the Johnson Criteria. The assumed operational altitude is 6,000 ft AGL. The IR sensor shall supply a video output of sufficient quality to recognize, with 70% probability of recognition, a 3.5m x 3.5m target at a slant range of not less than 7 km (T), 35 km (O) given an N50 of 3 cycles on target, relative humidity of 90%, visibility of 23 km, and a target foreground-background temperature difference of four (4) degrees C. (R.B.141)

3.4.2.5.2 IR Sensor - Spectral Response Band. The IR sensor shall be sensitive in the wavelength between 3-5 microns. (R.B.86)

3.4.2.5.3 IR Sensor Cool Down Time. The IR sensor cool down time when transitioning from the Non-Operate to Operate State shall be not greater than 10 minutes when the ambient temperature is +60 degrees C and the input voltage is +22 Volts Direct Current (VDC). (R.B.142) The IR sensor cool down time when transitioning from the Non- Operate to Operate state shall be not greater than 7 minutes when the ambient temperature is +23 degrees C and the input voltage is +28 VDC. (R.B.143) Cool down time is defined as the time from entering the Operate state to when the IR image is useable.

3.4.2.5.4 IR Sensor FOV. The IR sensor shall have not less than three optical FOVs.

(R.B.144) The IR sensor shall have an electronic zoom capability of not less than 2x.

(R.B.145) The IR sensor optical WFOV shall be not less than 20 degrees (horizontal).

(R.B.146)

3.4.2.5.5 IR Sensor Polarity. The IR sensor shall be selectable between black hot and white hot polarity modes. (R.B.147)

3.4.2.5.6 IR Sensor Detector Non-Uniformity Correction (NUC). From the time the payload receives the NUC command to completion shall be not greater than 25 seconds. (R.B.148)

3.4.2.6 LTM.

3.4.2.6.1 TM Power. The LTM shall have an output power of not less than 90 mW.

(R.B.149)

3.4.2.6.2 TM Divergence. The LTM beam divergence shall be not greater than 0.6 mrad. (R.B.150)

3.4.2.6.3 TM Wavelength. The LTM shall have a wavelength of 850 nm +/- 50 nm.

(R.B.151)

3.4.2.6.4 TM Boresight. The magnitude of the angle between the LTM beam and the reticle used to indicate its position shall be not greater than 1.0 mrad. (R.B.152)

3.4.2.6.5 TM Duty Cycle. The LTM shall have not less than two lasing modes:

continuous and flashing. (R.B.153) In flashing mode, the LTM duty cycle shall be 50% (+/- 10%). (R.B.154) The LTM shall be capable of not less than five minutes of operation in the continuous mode. (R.B.155) The LTM flashing mode rate shall be such that it will attract the attention of an observer. (R.B.156)

3.4.2.6.6 LTM Nominal Ocular Hazard Distance (NOHD). The LTM shall be eyesafe on the ground when fired from an operational altitude of 6,000 ft AGL or greater. (R.B.388)

3.4.2.7 LRF.

3.4.2.7.1 LRF Range. The LRF shall have a maximum effective range of not less than 7 km (T), 10 km (O). (R.B.158) The LRF shall have a minimum effective range of not greater than 300 m. (R.B.159) The LRF effective range will be defined as the maximum range at which the LRF can meet the accuracy requirement of paragraph

3.4.2.7.2 assuming a 10% in-band target reflectivity.

3.4.2.7.2 LRF Accuracy. The magnitude of the LRF range error shall be not greater than 5 m to a 90% confidence. (R.B.160)

3.4.2.7.3 LRF Interface. The LRF measured range value shall be available to the aircraft avionics interface. (R.B.161) The LRF shall be selectable between using the first and last pulse return for range calculation. (R.B.390)

3.4.2.7.4 LRF Nominal Ocular Hazard Distance (NOHD). The LRF unaided NOHD shall be not greater than 500 m. (R.B.162)

3.4.2.7.5 LRF Duty Cycle. The LRF shall be capable of not less than five (5) minutes of continuous operation without a cool-down period. (R.B.163) The LRF shall measure range at not less than once per second. (R.B.375)

3.4.2.7.6 LRF Boresight. The magnitude of the LRF boresight error with respect to the IR sensor shall be not greater than two (2) mrad. (R.B.164) The magnitude of the LRF boresight error with respect to the EO sensor shall be not greater than two (2) mrad.

(R.B.165)

3.4.2.8 LD.

3.4.2.8.1 LD Range. The LD beam divergence, boresight error, and stabilization shall be such that not less than 90% of the designator beam energy falls on a 3.5m x 3.5m target not less than 90% of the time when the designator is fired from a range of 7 km (T), 10 km (O). (R.B.166)

3.4.2.8.2 LD Duty Cycle. The LD duty cycle shall be 20%, with a minimum of 3 minutes of continuous firing with 12 minutes of cool down time. (R.B.382)

3.4.2.8.3 LD Pulse Energy. The LD pulse energy shall be not less than 45 mJ (T) 60 mJ (O). (R.B.167)

3.4.2.8.4 LD Wavelength. The LD wavelength shall be 1064 nm (+/- 1 nm). (R.B.168)

3.4.2.8.5 LD Boresight Adjustment. The time required to verify and adjust the LD boresight shall be not greater than five (5) minutes to include installation and removal of any ground support equipment. (R.B.169) The boresight process shall be capable of being performed without removing the payload from the aircraft. (R.B.170)

3.4.2.8.6 LD Pulse Characteristics. The LD shall fire at programmed pulse rates when the aircraft avionics interface commands LD fire. (R.B.171) The LD pulse width shall be not less than 11 nsec and not greater than 25 ns. (R.B.172) The LD pulse timing shall be compliant with STANAG 3733. (R.B.173)

3.4.2.8.7 LD Pulse Modes. The LD shall support Pulse Repetition Frequency (PRF) mode. (R.B.174) The LD shall accept PRF changes while in either the stand-by or armed state. (R.B.175) The LD shall report PRF load errors to the aircraft avionics. (R.B.176) The LD shall store PRFs in volatile memory. (R.B.177)

3.4.2.8.8 LD Mode Switching. The payload shall power off the LD when payload power is removed (i.e., when the payload transitions to the Non-Operate State). (R.B.178)

3.4.2.9 Image Fusion. The payload shall be capable of fusing EO and IR images into a single image output when commanded by the aircraft avionics. (R.B.179) The degree of fusing shall be adjustable using the aircraft avionics. (R.B.180) The fused imagery shall not introduce artifacts in the imagery that degrade performance. (R.B. 389)

3.4.2.10 LTM Imaging. The payload shall be capable of imaging the LTM spot as described in Section 3.4.2.4.2. (R.B.181)

3.5 Data.

3.5.1 Target Location Error (TLE). The payload shall be capable of calculating 3-dimensional geographic coordinates of target objects along the sensor LOS. (R.B.182) TLE shall be not greater than 30 m circular (2-dimensional) to a 90% confidence (T), 15 m circular and linear (3-dimensional) to a 90% confidence (O) from an operationally-effective altitude (8,000 ft AGL-day, 6,000 ft AGL-night) and slant range of seven (7)

km. (R.B.183)

3.5.2 Global Positioning System (GPS) / Inertial Measurement Unit (IMU). The payload shall be equipped with an On-Board IMU to improve TLE. (R.B.184) The IMU shall be capable of reporting position and orientation data relative to the aircraft coordinate frame. (R.B.185) The payload shall be capable of receiving external position data from the aircraft Selective-Availability, Anti-Spoofing Module (SAASM) GPS module. The payload may be equipped with an internal SAASM GPS, but must retain the ability to receive GPS information from the aircraft. (R.B.186)

3.5.3 Metadata. The payload shall provide Key-Length-Value (KLV) metadata in compliance with MISB Minimum Metadata Set Standard 0902.6 “Motion Imagery Sensor Minimum Metadata Set” for all digital full motion video (FMV). (R.B.187) The payload shall provide metadata in compliance with MISB Standard 102.11 “Security Metadata Universal and Local Sets for Digital Motion Imagery.” (R.B.188) The payload shall provide any metadata not covered in MISB 902.6 or 102.11 via MISB Standard

0601.5 “UAS Datalink Local Metadata Set.” (R.B.189) The payload shall be capable of time aligning the metadata to a video frame using MISB Standard 0604.2. (R.B.190) Payload-generated metadata shall conform to Table 3-1. (R.B.191)

Table 3-1. Payload-Generated Metadata.

Name Comments

UNIX Time Stamp

Mission ID Provided by Airborne Computing Equipment (ACE)

Platform Tail Number Provided by ACE

Platform Heading Angle

Platform Pitch Angle

Platform Roll Angle

Platform True Airspeed

Platform Indicated Airspeed

Platform Designation Provided by ACE: “Shadow 200 RQ-7B ”

Image Source Sensor Provided by ACE: Consists of payload name followed by currently-selected sensor

Image Coordinate System Provided by ACE: “Geodetic WGS84”

Sensor Latitude

Sensor Longitude

Sensor Altitude (MSL)

Sensor Horizontal Field of View

Sensor Vertical Field of View

Sensor Relative Azimuth Angle

Sensor Relative Elevation Angle

Sensor Relative Roll Angle

Slant Range

Target width

Frame center latitude

Frame center longitude

Frame center elevation

Offset corner Lat 1 Optional; payload-provided. Upper left corner location offset from center of video

Offset corner Long 1 Optional; payload-provided. Upper left corner location offset from center of video

Offset corner Lat 2 Optional; payload-provided. Upper right corner location offset from center of video

Offset corner Long 2 Optional; payload-provided. Upper right corner location offset from center of video

Offset corner Lat 3 Optional; payload-provided. Lower right corner location offset from center of video

Offset corner Long 3 Optional; payload-provided. Lower right corner location offset from center of video

Offset corner Lat 4 Optional; payload-provided. Lower left corner location offset from center of video

Offset corner Long 4 Optional; payload-provided. Lower left corner location offset from center of video

Wind Direction Provided by ACE.

Wind Speed Provided by ACE.

Static Pressure Provided by ACE.

Density Altitude Provided by ACE.

Outside Air Temperature Provided by ACE.

Target Location Latitude

Target Location Longitude

Target Location Elevation

Target track Gate Width Optional; payload-provided. Track gate width of tracked target within field of view (pixels)

Target Track Gate Height Optional; payload-provided. Track gate width of tracked target within field of view (pixels)

Generic Flag Data 01

Provided by ACE.

Bit 0 – laser rangefinder firing Bit 1 – auto track onBit 2 – IR polarity (1 = black hot) Bit 4 – slant range source (1 = measured, 0 = calculated) Other bits set to zero

Security Provided by ACE.

Ground Range Optional; payload-provided. Standoff range (m)

UAS LDS version Provided by ACE

Checksum

3.6 Interface Requirements.

3.6.1 Mechanical Interface. The payload mechanical interface shall be compliant with Textron Systems report R70436-01231, “Interface Control Document for the ESM 313 Second Source Payload Shadow aircraft Payload Mechanical and Electrical ICD” July 2015. (R.B.192) For any new payload installation, isolation requirements and criteria shall be evaluated to determine compatibility with the existing optional mounting and isolation design. (R.B.193)

3.6.2 Payload Dimensions and Weight. The payload diameter shall be less than or equal to 10.3 inches for those portions of the payload that are at or above the hole in the fuselage. (R.B.194) When in the installation and removal position (i.e., payload stowed), the payload diameter shall be not greater than 10.4 inches for those portions of the payload that are below the hole in the fuselage. (R.B.195) When stowed, the payload shall extend not greater than 7.5 inches below the exterior edge of the aircraft.

(R.B.385) The total height of the payload shall not be greater than 16.3 inches.

(R.B.196) The total weight of the payload shall not be greater than 50 lbs. (R.B.197) Figure 3-5 depicts the available payload volume. The available volume in this figure supersedes the Shadow ICD, which only allows 15 inches.

Figure 3-5 Available Payload Volume

3.6.3 Electrical Interface. The payload electrical interface shall be compliant with the “Signal Descriptions” and “Payload Electrical Interface Connector Pinouts” Sections (3.3 and 3.4, respectively) of Textron Systems report R70436-01231, “Interface Control Document for the ESM 313 Second Source Payload Shadow aircraft Payload Mechanical and Electrical ICD” July 2015. (R.B.198) The maximum power requirement of the payload shall be no greater than 300 W. (R.B.01)

3.6.4 Maintenance Port Interface. The payload shall provide a serial interface independent of the aircraft avionics interface to support maintenance operations.

(R.B.199) The payload shall provide an Ethernet interface to support maintenance operations. (R.B.200) The payload shall accept payload software updates through the Maintenance Port. (R.B.201) The payload shall transmit the version of the installed software in the payload via the Maintenance Port interface and the aircraft avionics interface. (R.B.202)

Annulus is not available volume, but rather indicates floor of airframe.

3.6.5 Operator Interface.

3.6.5.1 General. The payload shall have a menu that can be overlaid on the output video and controlled through the aircraft-avionics-to- payload interface. (R.B.203) The payload shall provide an overlaid menu for payload configuration and diagnostics.

(R.B.204)

3.6.5.2 Payload Symbology.

3.6.5.2.1 Symbology Control. Symbology shall be readable independent of background when displayed against an image or field. (R.B.205) The payload Symbology shall use MIL-STD-1472D as a guide. (R.B.206)

3.6.5.2.2 Symbology Laws. The payload shall support selectable symbology configurations. (R.B.207) The payload shall provide the ability to remove all symbology, except as required for laser safety. (R.B.208)

3.6.5.2.3 Symbology Data. All payload information provided in the payload symbology shall also transmit duplicate information in the messages sent via the aircraft avionics interface. (R.B.209) The payload symbology shall include the following:

a) LOS Reticle

b) Az/El Indicators

c) Sensor Group Fields

d) Aircraft Group Fields

e) Date/Time Fields

f) FOV Indicator

g) North Indicator

h) Target Group Fields

i) Laser Group Fields

j) Payload BIT Failures

k) Non-Uniformity Correction In Progress Status

l) IR Sensor Cooling Status

m) LD Mode

n) LRF Mode

o) LRF Range

p) Target Coordinates

q) LD Inhibit Zone

r) Boresight Reticle Position X

s) Boresight Reticle Position Y (R.B.210)

3.6.5.2.4 Symbology Content. Reticles shall be displayed in a manner that results in minimal target obscuration. (R.B.376) All Symbology text shall be of equal font size.

(R.B.211)

3.7 System Safety. The following sections define the payload safety requirements.

3.7.1 General Safety. The payload order of precedence on safety shall be:

a) Eliminate hazards through component selection

b) Incorporate safety devices

c) Provide warning devices

d) Develop procedures (R.B.212)

3.7.2 Laser Safety. The payload shall support a hardware interlock function that would prevent Class 2 lasers and above from accidental firing. (R.B.214) The payload shall be able to command any supported lasers into their respective “Standby” sub-state at any time. (R.B.215) The payload shall halt laser firing when that laser is commanded into its “Standby” sub-state. (R.B.216) The payload shall report to the aircraft avionics interface when internal payload conditions exist that have disabled Class 2 and above lasers. (R.B.217) The payload shall report the cause for disabling any Class 2 and above lasers to the aircraft avionics interface. (R.B.218) The payload shall adhere to the provisions for laser safety as specified in MIL-STD-1425A, Safety Design for Military Lasers and Associated Support Equipment, MIL-STD-1472, and ANSI Z136.1-2014 Safe Use of Lasers. (R.B.219)

3.7.2.1 Hardware. The laser devices shall not present laser hazards when disconnected from the aircraft. (R.B.220) The LTM, LD, and LRF shall present no laser hazards while in the Off State. (R.B.221) The payload shall ensure all Class 2 lasers and above will not emit any harmful laser radiation when in the stowed position. (R.B.372 )

3.7.2.2 Erroneous Conditions. The LD shall detect uncommanded Class 2, 3 or 4 firing.

(R.B.222) The payload shall transition Class 2 lasers and above to the Off State if an uncommanded laser firing condition occurs. (R.B.223) The payload shall power off the LD if the LD becomes unresponsive to commands while the LD is in the Fire Sub- State. (R.B.224)

3.7.2.3 Laser Inhibit Zone Conditions. The payload shall implement inhibit zones to prevent the laser energy from reflecting off aircraft surfaces. (R.B.225) The payload shall be able to receive laser inhibit zone parameters from the aircraft avionics.

(R.B.226) The payload shall halt firing upon entering a laser inhibit zone. (R.B.227) The payload shall resume firing upon exiting a laser inhibit zone (provided that the laser is still being commanded to fire). (R.B.228) The payload shall transition the laser to the Arm state (Standby for the LRF), if firing, upon entering the laser inhibit zone. (R.B.229) The payload shall inform the aircraft avionics when the active laser in an Arm state enters a laser inhibit zone. (R.B.230) The payload shall inform the aircraft avionics when the active laser in a Fire state enters a laser inhibit zone. (R.B.231) The payload shall accept commands to arm the laser while in a laser inhibit zone. (R.B.232) The payload shall inform the aircraft avionics interface when the payload is in a laser inhibit zone and receives a command to transition to the Arm or Standby state. (R.B.233) The payload shall permit payload manipulation (e.g., FOV changes, AZ/EL changes) within a laser inhibit zone. (R.B.234) The payload shall permit switching lasers while in a laser inhibit zone. (R.B.235) The payload shall report laser inhibit zone indications separate from general laser inhibit conditions. (R.B.236)

3.7.2.3.1 Laser Near Inhibit Zone Notification. The payload shall inform the aircraft avionics if the laser is armed or firing when the laser’s LOS is within five (5) degrees of the laser inhibit zone. (R.B.237)

3.7.2.4 Overtemp Indications.

3.7.2.4.1 Approaching Laser Overtemp. The payload shall provide an indication when the laser is within five (5) degrees C of the overtemp condition. (R.B.238)

3.7.2.4.2 Laser Overtemp Reached. The payload shall provide an indication when the laser has reached the overtemp threshold. (R.B.239) The payload shall cease firing and transition to the state or sub-state most conducive to laser cooling when the overtemp condition is reached. (R.B.240) After the overtemp condition is removed the payload shall permit firing (i.e., the payload does not need to cool completely outside the “approaching overtemp” zone). (R.B.241)

3.7.2.4.2 Battle Short / Override. The payload shall accept an override command from the aircraft avionics that will allow the laser to fire through the overtemp condition.

(R.B.242) The payload shall allow the override command when the payload is approaching or in an overtemp condition. (R.B.243) If firing continues via the override and the laser fails the payload shall provide an indication that the laser is no longer functional. (R.B.244) The payload shall display the overtemp indicators on the payload video. (R.B.245)

3.7.2.5 Aircraft Avionics Communication Loss Conditions. The payload shall transition all lasers from the Armed or Firing states to the Standby state within 2 seconds of a communications loss from the aircraft avionics. (R.B.246) The payload shall continue to provide payload status to the aircraft avionics over the communication interface upon a communications loss from the aircraft avionics to the payload. (R.B.247) The payload shall transmit an indication to the aircraft avionics that a loss of communications has been detected. (R.B.248) The payload shall transmit an indication to the aircraft avionics when communications is restored. (R.B.249) The payload shall keep all Class 2 lasers and above in the Standby state after communications with the aircraft avionics interface is restored. (R.B.250) The payload shall display the aircraft avionics communications loss status on the payload video. (R.B.251)

3.7.3 Mechanical Safety. The payload exposed edges and corners shall be rounded to a minimum of 0.75mm (0.03 in) radius to prevent a safety hazard to personnel or potential damage to equipment during usage. (R.B.252)

3.7.4 Electrical Safety. The payload electrical components shall conform to MIL-HDBK- 454A for electrical safety. (R.B.253) The payload shall incorporate guards, grounding, interlocks, and warning placards alerting personnel to dangerous voltages or currents.

(R.B.254) The payload shall have full performance and functionality without upset, being damaged, or producing false signals, caused by normal surges/outages defined by MIL- STD-704E. (R.B.255) During both operation and maintenance, the payload shall not be damaged by abnormal surges/outages defined by MIL-STD-704E and return to normal operation once the transient(s) have ceased. (R.B.256) The payload electrical power shall meet power quality standards in accordance with MIL-STD-704E for all operating conditions. (R.B.257)

3.7.5 Personnel Safety. The payload shall not expose personnel to concentrations of toxic substances in excess of the limits specified in either the Department of Defense (DoD) Occupational…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.