Att1_(U) PERFORMANCE SPECIFICATION FOR EOSS TO SUPPORT MK34 MK48 GWS 02012026.docx

U pERFORMANCE SPECIFICATION FOR THE

EOSS TO SUPPORT THE MK34 AND MK48 GUN WEAPON SYSTEMS

(U) SCOPE

(U) This performance specification identifies the required characteristics and defines the critical performance, physical, interface, logistic, quality, and qualification requirements for Electro-Optic/ Infrared (EO/IR) Sight System (EOSS) for the U.S. Navy MK 34 Gun Weapon System (GWS), the U.S. Coast Guard (USCG) MK 48 GWS, and future U.S. Navy, USCG, and Foreign Military Sales (FMS) GWSs.

(U) Background

(U) This program has been initiated to create a competitive environment for the replacement the MK 20 MOD 1 EOSS whose predecessors were MK 20 MOD 0 EOSS and MK 46 Optical Sight System (OSS).

(U) The EOSS is not a stand-alone system. The EOSS SHALL interface with the GWS Local Area Network (LAN) and be remotely controlled by government furnished MK 160 Gun Computer System (GCS) console(s) for both operations and maintenance.

(U) The EOSS will be installed on at least U.S. Navy Ticonderoga class cruisers (CG-47), U.S. Navy Arleigh Burke class destroyers (DDG-51), USCG Legend class National Security Cutters (NSC) (WMSL-750), and USCG Heritage class Off-shore Patrol Cutter (OPC) (WMSM-915).

(U) Primary use of the EOSS is to act as the gun sight for the MK34 and MK48 GWS in the visible and thermal spectrum.

(U) Ancillary uses of the EOSS may include enhancing the following: low-visibility and night navigation; coastal observation and surveillance; identification (ID) friend or foe; real-time situational awareness and threat warning; reconnaissance and surveillance; and documenting navigational hazards.

(U) ID

(U) The major Configuration Items (CI)s comprising the EOSS will be identified by specific Navy nomenclature. Official nomenclature assignments will be determined following any acquisition using this specification.

(U) LISTING OF APPLICABLE DOCUMENTS

(U) The following specifications and documents form a part of this specification to the extent specified herein. Unless otherwise specified, the version of these documents current as of March 24, 2025 SHALL be applicable. Updates to these specifications and documents will be monitored by both the government and contractor and updates after the date SHALL be discussed for relevance.

(U) Program Specific Documents

(U) Table 1 Program Specific Documents

(U) Military References

(U) Table 2 Military References

DoD Reliability, Availability, Maintainability and Cost Rationale Report Manual 1 June 2009

MIL-STD-2073-1E

w/Change 4 Standard Practice for Military Packaging

NAVSEA Standard Item 009-32 Cleaning and Painting Requirements; Accomplish

(U) Other Publications For Reference

(U) Table 3 Other Publications

National Geospatial-Intelligence Agency (NGA) Conformance Program Plan for Motion Imagery

NGA Conformance Test Plan for Motion Imagery

NGA.STND.0044

_1.3.2_MIE4NITF

NGA – National Imagery Transmission Format 2.1 Motion Imagery Extension

(U) Order Of Precedence

(U) In the event of a conflict between the text of this document and the references cited herein, the text of this document takes greater precedence to referenced EOSS SOW when conflicting data arises only. Nothing in this document supersedes applicable Federal, State or Local Laws and regulations unless a specific exemption has been obtained.

(U) Availability Of DOD Documents

(U) Government standards and handbooks are available from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094.

(U) REQUIREMENTS AND VERIFICATION METHOD

(U) Threshold is a minimum requirement. Thresholds throughout this document have a bracketed Unique Identification (UID) number beginning with “T‑” (e.g., [T‑9999]), which appears near the end of each requirement before the verification methods.

(U) Objectives are desired capabilities rather than requirements. Objectives throughout this document have a bracketed UID number beginning with “O‑” (e.g., [O‑9998]), which appears near the end of each requirement before the verification methods.

(U) Verification methods are located at the end of each requirement.

(U) Verification Methods

(U) A (By Analysis) – Produce documentation via calculations or other form of study to verify compliance with requirement

(U) M (Modeling and Simulation) – Predictive M&S to prove or verify compliance with requirement

(U) I (Inspection) – Visual verification of compliance with requirement

(U) D (Demonstration) – Requirement compliance verified through functional observation to verify expected output or function

(U) L (Lab Testing) – Quantitative data measurements in a controlled environment

(U) R (Range Testing) – Field data gathered from test events in a relevant environment (i.e., representative of the operational environment for the purposes of the test)

(U) P (Platform Test and Evaluation) – Data gathered from test events on the intended platform (e.g., ship)

(U) V (Post Test M&S Validation) – Post-test update and confirmation of predictive model

(U) DESCRIPTOR

(U) T (Threshold) – SHALL/Mandatory

(U) O (Objective) – SHOULD/Recommended

(U) RESPONSIBLE PARTY

(U) C (Contractor) – Contracted personnel should perform work and produce appropriate documentation to prove compliance with requirement

(U) G (Government) – Government personnel will perform work and produce documentation to verify compliance with requirement

(U) EXAMPLES

(U) L[T].C – Mandatory Contractor Lab Testing

(U) L[T].CG – Mandatory Lab Testing for both Contractor and Government

(U) L[T].C/G – Mandatory Lab Testing for either Contractor, Government, or both at program discretion

(U) Functional Architecture Diagrams

(U) The EOSS, subsystems, sensors, and components SHALL conform to the architecture shown in the Figures below. [T-0001] A[T].CG

(U) Figure 1

(U) The EOSS, subsystems, sensors, and components SHOULD conform to the architecture shown in the Figures below. [O-0002] A[T].CG

(U) Figure 8 CUI objective diagram redacted for (U) version of this performance specification.

(U) Modular Open Systems Approach (MOSA) Sensor Architecture And Interfaces

(U) Whenever possible, the sensor architecture and interfaces SHALL support the MOSA architecture and interface standards per 10 USC Subtitle A, Part V, Subpart F, Chapter 327, Subchapter I [T-0003] A[T].C, M[O].C, D[O].C, L[T].C, L[O].G

(U) The Grade A shock configuration ADE portion of the EOSS SHALL physically interface with the ship deck using the following hole patterns. Adapter plates are acceptable. [T-0004] A[T].C

(U) Figure 15 Ship deck hole pattern for Grade A shock configuration

(U) The Grade B shock configuration ADE portion of the EOSS SHALL physically interface with the ship deck using the following hole patterns. Adapter plates are acceptable. [T-0005] A[T].C

(U) Figure 16 Ship deck hole pattern for Grade B Shock configuration

(U) The EOSS SHALL interface with the MK160 Gun Computer System (GCS) in conformance with Interface Design Document (IDD) PRF-WS-35951 [T-0006] A[T].CG, P[T].CG

(U) Note: An LRU is any item which can be readily accessed in the field (via removal of access covers, environmental shrouds, etc.) and replaced in situ without further removal or disassembly of the CI of which the item is a component part.

(U) Any component, inseparable assembly or functional sub-system with a system de-rated (under powered) operational life of four thousand five hundred hours (4,500 hrs.) or less SHALL be an Organizational level (O‑level) LRU per 22 CFR Part 120.45. [T-0007] A[T].CG, M[O].C

(U) LRUs SHALL be plug-in/plug-out modules and include waterproof, quick-connect protective caps. MIL-HDBK-454 provides guidance on interchangeability. [T-0008] A[T].C, D[O].C

(U) LRUs of common nomenclature and part number SHALL be designed to be interchangeable and interoperable. [T-0009] A[T].C

(U) Any engineering changes (software, hardware, and firmware) incorporated into an LRU SHALL be reverse compatible with all non-upgraded system LRUs. [T-0010] A[T].C, M[T].C, D[O].C, P[T].G

(U) The VIS SHALL be designed as an LRU. [T-0011] A[T].CG, M[O].C

(U) The TIS SHALL be designed as an LRU. [T-0012] A[T].CG, M[O].C

(U) The ELRF SHALL be designed as an LRU. [T-0013] A[T].CG, M[O].C

(U) The Director SHALL be designed as an LRU. [T-0014] A[T].CG, M[O].C

(U) Applicable electronic units SHALL be designed as LRUs. [T-0015] A[T].CG, M[O].C

(U) Motion Imagery (MI) / Metadata (MD)

(U) All EOSS element(s) and their subcomponents (LRUs or modules) SHALL comply with the requirements of the Motion Imagery Standards Profile (MISP) 2023.2 [T-0016] A[T].C, M[O].C, L[T].C, L[O].G

(U) MI/MD SHALL be verified as MISP compliant In Accordance With (IAW) the National Geospatial-Intelligence Agency (NGA) Conformance Program Plan for Motion Imagery and NGA Conformance Test Plan for Motion Imagery. [T-0017] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The MI Source Aspect Ratio (SAR) SHALL be in the range [0.25, 4.0] IAW MISB TRM 1404 and MISP‑2023.2: MISP‑2015.1-01. [T-0018] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The MI format at the imager (Sensor) and for any MI conversions or transcodes SHALL be a progressive-scan format IAW MISP‑2023.2: MISP‑2015.1-02. [T-0019] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Every MI frame SHALL include a timestamp representing Absolute Time consistent with MISB ST 0603.5 IAW MISP‑2023.2: MISP‑2018.3-116. [T-0020] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Where MD contains a timestamp item representing Absolute Time, the timestamp SHALL be IAW MISB ST 0603.5 IAW MISP‑2023.2: MISP‑2018.1-97. [T-0021] A[T].CG, M[O].C, L[T].C, L[O].G

(U) An instantiation of MI SHALL have only one (1) timestamp representation which represents Absolute Time IAW MISP‑2023.2: MISP‑2018.1-98. [T-0022] A[T].CG, M[O].C, L[T].C, L[O].G

(U) MI in digital form SHALL remain in digital form IAW MISP‑2023.2: MISP‑2015.1-06. [T-0023] A[T].CG, M[O].C, L[T].C, L[O].G

(U) KLV MD SHALL be encoded IAW SMPTE ST 336 IAW MISP‑2023.2: MISP‑2015.1-07. [T-0024] A[T].CG, M[O].C, L[T].C, L[O].G

(U) KLV MD SHALL be formatted IAW MISB ST 0107 and MISP‑2023.2: MISP‑2015.1-08. [T-0025] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When using KLV and mapping between floating point values and integer values, the mapping SHALL comply with MISB ST 1201 IAW MISP‑2023.2: MISP‑2015.1-09. [T-0026] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Multi-dimensional arrays of data expressed in KLV SHALL be formatted IAW MISB ST 1303 and MISP‑2023.2: MISP‑2015.1-10. [T-0027] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Only those containers specified in MISP‑2023.2 SHALL be used for Class 0 MI, Class 1 MI, and Class 2 MI IAW MISP‑2023.2: MISP‑2015.1-11. [T-0028] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Digital images extracted from Motion Imagery as a NITF (National Imagery Transmission Format) / NSIF (NATO Secondary Imagery Format) SHALL comply with ISO/IEC Joint BIIF Profile / NATO STANAG 4545 respectively IAW MISP 2023.2: MISP-2022.2-133. [T-0029] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, the MI sampling format for 1920x1080 progressive-scan High Definition (HD) MI SHALL be defined by SMPTE ST 274 IAW MISP‑2023.2: MISP‑2015.1-21. [T-0030] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, The MI sampling structures for 3840x2160 and 7680x4320 progressive-scan Ultra High Definition (UHD) MI SHALL be defined by SMPTE ST 2036-1 IAW MISP‑2023.2: MISP‑2015.1-22. [T-0031] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, Class 0 MI encapsulated in Material eXchange Format (MXF) SHALL comply with MISB ST 1606.1 IAW MISP‑2023.2: MISP‑2021.1-121. [T-0032] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Class 0 Motion Imagery placed into a JBP (Joint BIIF Profile) NITF (National Imagery Transmission Format) / STANAG 4545 NSIF (NATO Secondary Imagery Format) SHALL comply with MIE4NITF IAW MISP-2023.2: MISP-2022.2-132. [T-0033] A[T].CG, M[O].C, L[T].C, L[O].G

(U) While compressing Class 1 MI with H.264/AVC, the compression SHALL comply with ISO/IEC 14496-10 | ITU-T Rec. H.264 IAW MISP‑2023.2: MISP‑2015.1-32. [T-0034] A[T].CG, M[O].C, L[T].C, L[O].G

(U) While compressing Class 1 MI with H.264/AVC, the compression SHALL be profile Constrained Baseline, Main or High in the range of Level 1 to Level 4 inclusive IAW MISP‑2023.2: MISP‑2018.2-114. [T-0035] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When infrared MI with a pixel value range greater than 8 bits is converted into Class 1 MI and compressed using H.262/MPEG-2 or H.264/AVC the compressed imagery SHALL comply with MISB ST 0404.1 IAW MISP‑2023.2: MISP‑2015.1-37. [T-0036] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Class 1 MI SHALL contain a timestamp based on Absolute Time IAW MISB ST 0604.6 and MISP‑2023.2: MISP‑2018.1-104. [T-0037] A[T].CG, M[O].C, L[T].C, L[O].G

(U) A MIIS Core ID inserted into Class 1 Motion Imagery SHALL be in accordance with MISB ST 2101 IAW MISP-2023.2: MISP-2021.2-128. [T-0038] A[T].CG, M[O].C, L[T].C, L[O].G

(U) A MIIS Core ID inserted into Class 1 Motion Imagery SHALL be the same Core ID in its corresponding metadata IAW MISP-2023.2: MISP-2021.2-129. [T-0039] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Class 1 MI MD SHALL be represented using Key Length Value (KLV) IAW MISP‑2023.2: MISP‑2015.1-45. [T-0040] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, Class 1 MI encapsulated in a MPEG-2 Transport Stream container SHALL comply with ISO/IEC 13818-1 | ITU-T Rec H.222.0 IAW MISP‑2023.2: MISP‑2015.1-47. [T-0041] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, Class 1 MI encapsulated in a MPEG-2 Transport Stream container SHALL comply with MISB ST 1402.2 IAW MISP‑2023.2: MISP‑2015.1-48. [T-0042] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, Security MD encapsulated in a MPEG-2 Transport Stream container SHALL be inserted into only one (1) of the two (2) carriage mechanisms available: The Synchronous Stream Multiplex Method or the Asynchronous Stream Multiplex Method IAW MISB ST 1402.2 and MISP‑2023.2: MISP‑2015.1-49. [T-0043] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, Class 1 MI encapsulated in a MPEG-2 Transport Stream container SHALL meet the conformance requirements of ISO/IEC 13818-4 IAW MISP‑2023.2: MISP‑2015.1-50. [T-0044] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, Class 1 MI encapsulated in a Common Media Application Format (CMAF) container SHALL comply with ISO/IEC 23000-19 IAW MISP‑2023.2: MISP‑2021.1-122. [T-0045] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, Class 1 MI encapsulated in a CMAF container SHALL comply with MISB ST 1910.1 IAW MISP‑2023.2: MISP‑2021.1-123. [T-0046] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, Security MD encapsulated in a CMAF container SHALL be present in either the synchronous or asynchronous MD message boxes, but not both IAW MISP‑2023.2: MISP‑2021.1-124. [T-0047] A[T].CG, M[O].C, L[T].C

(U) Where graphic and text information are overlaid onto MI, the information SHALL be nondestructive to the MI content (i.e., “burned-in MD” is not allowed) IAW MISP‑2023.2: MISP‑2015.1-67. [T-0048] A[T].CG, M[O].C, L[T].C

(U) A MISB MD set SHALL conform to all requirements as specified for that MD set except where noted IAW MISP‑2023.2: MISP‑2016.1-92. [T-0049] A[T].CG, M[O].C, L[T].C

(U) MI SHALL contain a Core Identifier IAW MISB ST 1204.3 and MISP‑2023.2: MISP‑2015.1-68. [T-0050] A[T].CG, M[O].C, L[T].C

(U) Where supplemental identifiers are used with MISB ST 1204.3, the supplemental identifiers SHALL be defined by MISB ST 1301.2 IAW MISP‑2023.2: MISP‑2015.1-69. [T-0051] A[T].CG, M[O].C, L[T].C

(U) When implementing MISB ST 0801 the threshold and objective profiles for photogrammetric MD items, the items SHALL be defined by MISB ST 1107.4 IAW MISP‑2023.2: MISP‑2015.1-70. [T-0052] A[T].CG, M[O].C, L[T].C

(U) Transforming two‑dimensional (2D) MI from one (1) coordinate system into a second two-dimensional (2D) coordinate system SHALL comply with MISB ST 1202.3 IAW MISP‑2023.2: MISP‑2015.1-71. [T-0053] A[T].CG, M[O].C, L[T].C

(U) Where Standard Deviation and Correlation Coefficient MD is available, such MD SHALL be provided IAW MISB ST 1010.3 and MISP‑2023.2: MISP‑2015.1-72. [T-0054] A[T].CG, M[O].C, L[T].C

(U) MI SHALL include security MD IAW MISB ST 0102.12 and MISP‑2023.2: MISP‑2015.1-73. [T-0055] A[T].CG, M[O].C, L[T].C

(U) MI SHALL contain the MI Sensor Minimum MD Set IAW MISB ST 0902.8 and MISP‑2023.2: MISP‑2015.1-75. [T-0056] A[T].CG, M[O].C, L[T].C

(U) When MD items within an instantiating MD set are changed, the changed MD SHALL be signaled using the Amend Local Set and Segment Local Set as defined in MISB ST 1607.1 IAW MISP‑2023.2: MISP‑2017.1-95. [T-0057] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, A MPEG-2 Transport Stream encapsulated in Real Time Protocol (RTP) SHALL comply with MISB ST 0804.4 IAW MISP‑2023.2: MISP‑2015.1-76. [T-0058] A[T].CG, M[O].C, L[T].C

(U) When applicable, Class 1 MI encapsulated in Real Time Protocol (RTP) SHALL comply with MISB ST 0804.4 IAW MISP‑2023.2: MISP‑2015.1-77. [T-0059] A[T].CG, M[O].C, L[T].C

(U) When applicable, Class 1 MI and MD encapsulated per CMAF ISO/IEC 23000-19 for adaptive bitrate streaming SHALL comply with MISB ST 1910.1 IAW MISP‑2023.2: MISP‑2020.3-120. [T-0060] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, KLV to Cursor-on-Target (CoT) encoding SHALL be IAW MISB ST 0805.1 and MISP‑2023.2: MISP‑2015.1-80. [T-0061] A[T].CG, M[O].C, L[T].C, L[O].G

(U) When applicable, when requesting Class 1 MI or Class 2 MI from a platform that supports MISB ST 1101, the messages SHALL comply with MISB ST 1101 IAW MISP‑2023.2: MISP‑2015.1-81. [T-0062] A[T].CG, M[O].C, L[T].C

(U) When applicable, for file exchange, operational patterns 1a (OP‑1a) and 1b (OP‑1b) as per SMPTE ST 378 and SMPTE ST 391, respectively, SHALL be used IAW MISP‑2023.2: MISP‑2015.1-12. [T-0063] A[T].CG, M[O].C, L[T].C

(U) When applicable, MI and MD SHALL use the method of frame-based mapping within the generic container IAW SMPTE ST 379-1 and SMPTE ST 381-1 and MISP‑2023.2: MISP‑2015.1-13. [T-0064] A[T].CG, M[O].C, L[T].C

(U) When applicable, all data constraints for an Aerial Surveillance and Photogrammetry Applications (ASPA) MXF file SHALL comply with MISB ST 0301.5 IAW MISP‑2023.2: MISP‑2015.1-14. [T-0065] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The EOSS ADE and their subcomponents (LRUs or modules) SHALL output Class 0 MI to the BDE IAW MISB ST 1608.1. [T-0066] A[T].CG, M[O].C, L[T].C

(U) The EOSS BDE SHALL be capable of receiving and disseminating MISB compliant Class 0, 1, and 2 MI. [T-0067] A[T].CG, M[O].C, L[T].C, P[T].G

(U) The EOSS BDE SHALL encode Class 0 MI in such a way to preserve the highest sampling format produced by the sensor to include, but not limited to, native frame rate, aspect ratio, color sampling, and quantization bits. [T-0068] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The EOSS BDE SHALL encode Class 1 MI with larger than 10-bit imagery using High Efficiency Video Coding (HEVC) / H.265 compression using the Main 4:4:4 16 Intra profile. [T-0069] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The EOSS BDE SHALL encode Class 2 MI with using HEVC / H.265 compression using the profile Main 4:4:4 16 Intra for large format imagery. [T-0070] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The EOSS BDE SHALL be capable of transcoding MI/MD after initial encoding IAW MISB TRM 0703.1 [T-0071] A[T].CG, M[O].C, L[T].C, L[O].G

(U) All EOSS ADE and their subcomponents (LRUs or modules) SHALL generate and insert MD IAW MISB ST 1801.2, but omit Mission ID, Platform Number, and Platform Designation. [T-0072] A[T].CG, M[O].C, L[T].C, L[O].G

(U) All EOSS ADE and their subcomponents (LRUs or modules) SHOULD generate and insert any additional MD required to communicate image content information to the Sensor Electronics Suite's image processing capabilities such as distortion maps, Non-Uniformity Correction (NUC) tables, Bayer filter, coefficients, frame rate, exposure/integration times, etc. [O-0073] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The EOSS BDE SHALL insert Mission ID, Platform Number, and Platform Designation and populate the Security Local Set and any applicable elements (i.e., Sensor Electronics Suite elements) as appropriate for full compliance with MISP and MISB ST 1801.2. [T-0074] A[T].CG, M[O].C, L[T].C, L[O].G

(U) All EOSS ADE and their subcomponents (LRUs or modules) and Automatic Video Tracker (AVT) processing SHALL generate and insert MI Track MD (MISB ST 0903.6) IAW MISB ST 1608.1, MISB ST 1107.4, and MISB ST 1801.2. [T-0075] A[T].C, M[O].C, L[T].C, R[O].G, P[T].G

(U) The EOSS BDE electronics suite processing equipment that incorporates AVT SHALL generate MI Track MD IAW MISB ST 1801.2. [T-0076] A[T].CG, M[O].C, L[T].C, L[O].G

(U) EOSS AVT processing SHALL incorporate MI Track MD (i.e., MISB ST 0903.6) IAW MISB ST 1608.1 and MISB ST 1801.2. [T-0077] A[T].C, M[O].C, L[T].C, R[O].G, P[T].G

(U) Sensors using LOS for track localization SHALL provide MD with the MI in conformance with MISB ST 0903.6 and MISB ST 1608.1. [T-0078] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The EOSS BDE SHALL utilize the staging system standards in MISB ST 1801.2 and MISB ST 1906.2 to report all applicable constellation stages of sensor positional and alignment MD from ADE to BDE. [T-0079] A[T].C, M[O].C, L[T].C, R[O].G, P[T].G

(U) The VIS and TIS SHALL output GigE Class 0 MI and MD from sensors to BDE IAW MISB ST 1608.1. [T-0080] A[T].CG, M[O].C, L[T].C, L[O].G

(U) Any MISB ST 0601.19 MD elements that are available SHOULD be included in the EOSS MD stream except for Mission ID, Platform Number, and Platform Designation. [O-0081] A[T].CG, M[O].C, L[T].C, L[O].G

(U) The compression ratio and bitrates SHALL be programmable between the ranges specified in MISB RP 0802.2 for shipboard distribution. [T-0082] A[T].C, M[O].C, L[T].C, R[O].G, P[T].G

(U) The EOSS SHALL provide all MD that will allow the Navy to generate its own symbology for operations modes and apply them to unmarked MI. [T-0083] A[T].C, M[O].C, L[T].C, R[O].G, P[T].G

(U) The EOSS SHALL provide all command and control data in the MD that will allow the Navy to generate its own symbology for operations modes and apply them to unmarked MI. [T-0084] A[T].C, M[O].C, L[T].C, R[O].G, P[T].G

(U) No EOSS Components in the GCS

(U) All EOSS components SHALL exist at one (1) end of the GWS LAN. EOSS components SHALL NOT reside in the GCS. [T-0085] A[T].C

(U) EOSS Sensor Management

(U) Whenever possible, the EOSS SHALL comply with Army Integrated Sensor Architecture (ISA). [T-0086] A[T].CG, M[T].C, D[O].C, P[T].G

(U) Safety

(U) The EOSS SHALL be designed for safety IAW MIL-STD-882E Change 1. [T-0087] A[T].C, M[O].C, L[T].C/G, P[T].G

(U) Where EOSS safety design features must be compromised to achieve performance, alternate means for risk mitigation IAW MIL-STD-882E Change 1 SHALL be followed. [T-0088] A[T].CG, M[O].C, D[O].C, L[T].CG, R[O].G, P[T].G

(U) Known hazards SHALL be controlled to protect personnel, equipment, and ship's facilities without compromising the operational requirements of the ship. [T-0089] A[T].CG, M[O].C, D[O].C, L[T].CG, R[O].G, P[T].G

(U) The EOSS SHALL be designed so that no single failure (human, mechanical, or electrical) can produce a sudden and total failure from which recovery is impossible. [T-0090] A[T].CG, M[O].C, D[O].C, L[T].C, P[T].G

(U) When power to the main EOSS power bus is interrupted, automatic restraint of the director SHALL occur (regardless of state or mode) until power is restored and the operator selects the operate mode. [T-0091] A[T].C, M[O].C, D[O].C, L[T].C

(U) Electrical, mechanical, and software interlocks SHALL be provided to prevent personnel, equipment, and ship system damage during failures. [T-0092] A[T].CG, M[O].C, D[O].C, P[T].G

(U) Note: MIL-HDBK-454C, Requirement 1 may be used for guidance on equipment safety design criteria.

(U) Safety Switch

(U) In the case of the EOSS having protruding sensors, cables, components, or any items that could strike, pinch, smash, crush a user when they are in with the rotational arch of the EOSS, the system SHALL have a safety switch. [T-0093] A[T].C

(U) In the case of the EOSS having protruding sensors, cables, components, or any items that could strike, pinch, smash, crush a user when they are in with the rotational arch of the EOSS, the safety switch SHALL be installed outside the working volume of the EOSS. [T-0094] A[T].CG, M[O].C, D[O].C

(U) In the case of the EOSS having protruding sensors, cables, components, or any items that could strike, pinch, smash, crush a user when they are in with the rotational arch of the EOSS, activation of the safety switch SHALL prevent any movement of the EOSS from the GCS console commands. [T-0095] A[T].CG, M[O].C, D[O].C, L[T].C, P[T].G

(U) In the case of the EOSS having protruding sensors, cables, components, or any items that could strike, pinch, smash, crush a user when they are in with the rotational arch of the EOSS, activation of the safety switch SHALL engage the power off brakes. [T-0096] A[T].CG, M[O].C, D[O].C, L[T].C, P[T].G

(U) In the case of the EOSS having protruding sensors, cables, components, or any items that could strike, pinch, smash, crush a user when they are in with the rotational arch of the EOSS, activation of the safety switch SHALL send an indication to the GCS that the safety switch has been enabled. [T-0097] A[T].CG, M[O].C, D[O].C, L[T].C, P[T].G

(U) In the case of the EOSS having protruding sensors, cables, components, or any items that could strike, pinch, smash, crush a user when they are in with the rotational arch of the EOSS, the safety switch activation indication SHALL be displayed as part of the EOSS situational awareness display. [T-0098] A[T].CG, M[O].C, D[O].C, L[T].C, P[T].G

(U) In the case of the EOSS having protruding sensors, cables, components, or any items that could strike, pinch, smash, crush a user when they are in with the rotational arch of the EOSS, activation of the safety switch SHALL disable all EOSS power including disabling the ELRF. [T-0099] A[T].CG, M[O].C, D[O].C, L[T].C, P[T].G

(U) In the case of the EOSS having protruding sensors, cables, components, or any items that could strike, pinch, smash, crush a user when they are in with the rotational arch of the EOSS, the safety switch SHALL have some redundancy so that a failed switch does not disable the EOSS. [T-0100] A[T].CG, M[O].C, D[O].C, L[T].C, P[T].G

(U) Electrical Safety

(U) All high voltage electrical equipment SHALL have fail-safe interlocks to prevent injury to personnel during installation, operation, maintenance, and repair functions. [T-0101] A[T].CG, M[O].C, D[O].C, L[T].C/G

(U) Electrical connectors SHALL be designed or specified so as to prevent connections that will cause the system to work improperly. [T-0102] A[T].CG, D[O].C

(U) All cabinets SHALL be grounded IAW MIL-STD-1310H. [T-0103] A[T].C, D[O].C, L[T].C/G, P[O].G

(U) All EOSS cables and cable assemblies SHALL meet the electrical safety requirements in Title 46 CFR Part 111 for the voltage and current loads of the system. [T-0104] A[T].C, M[O].C, L[T].C/G

(U) The EOSS SHALL not produce an electromagnetic environment, which can cause safety and reliability degradation of ordnance items or a hazard to personnel. [T-0105] A[T].C, M[O].C, L[T].C/G

(U) The EOSS design SHALL protect personnel, fuels, and ordnance from hazardous effects of electromagnetic radiation using MIL-STD-464D. [T-0106] A[T].C, M[O].C, L[T].C/G

(U) The EOSS SHALL comply with current requirements for the protection of personnel against the effect of electromagnetic radiation IAW DODI 6055.11. [T-0107] A[T].C, M[O].C, L[T].C/G If the EOSS contains lithium battery(s), the EOSS SHALL operate in accordance with NAVSEAINST 9310.1accordance with NAVSEAINST 9310.1. [T-0108] A[T].C, M[O].C, L[T].C/G

(U) Laser Safety

(U) ELRF laser(s) SHALL be certified as a Class 1 system while operating at or below 1 (one) pulse per second and Class 1 or 1M system while operating above 1 (one) pulse per second per ANSI Z136.1 and verified by the Navy/Marine Corps Laser Safety Review Board (LSRB). [T-0109] A[T].C, M[O].C, L[T].C/G

(U) The ELRF SHALL be certified as Class 1 system while operating at or below 1 (one) pulse per second and Class 1M system while operating above 1 (one) pulse per second by the LSRB as specified in OPNAV 5100.27/MCO5104.1. [T-0110] A[T].CG, M[T].C, L[T].C/G, R[O].G, P[T].G

(U) The laser subsystem SHALL comply with the design standards of MIL-STD-1425. [T-0111] A[T].CG, M[O].C, L[T].C/G, R[O].G, P[T].G

(U) The ELRF laser(s) SHALL meet Laser Clearinghouse (LCH) requirements and register basic system parameters and concepts of operation with the Commander, United States Strategic Command (CDRUSSTRATCOM) per DoDI 3100.11 and Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3225.01. [T-0112] A[T].CG, M[O].C, L[T].C/G, R[O].G, P[T].G

(U) The ELRF SHALL emit a wavelength in the one and five tenths micron (1.5µm) to one and sixty-five hundredths micron (1.65µm) band that allows for EOSS to meet the safety requirements. [T-0113] A[T].CG, M[T].C, D[O].C, L[T].C

(U) The EOSS system SHALL allow installation and maintenance personnel to set Laser cutout zones in Az and El and be programmable to enable inhibit regions to be established and maintained. [T-0114] A[T].CG, M[O].C, D[O].C, P[T].G

(U) In the case where the ELRF cannot be fired because of the maintenance set cutout zones, the EOSS SHALL report that these maintenance set cutout zones are preventing the laser from firing. [T-0115] A[T].CG, M[O].C, D[O].C, P[T].G

(U) The maintenance set Cutout Zones SHALL be comprised of at least 32 coordinates to compile the cutout zone polygon or be approved by the Government if coordinate method is not used. [T-0116] A[T].CG, M[O].C, D[O].C, P[T].G

(U) The EOSS SHALL remember the previously recorded maintenance cutout zone coordinates so that when an LRU is swapped that it does not need to be reconfigured. [T-0117] A[T].CG, M[O].C, D[O].C, P[T].G

(U) The EOSS system SHALL allow installation and maintenance personnel the capability to set Geodetic Lasing Cutouts that take into account the dynamics of the ship as well as Relative Lasing Cutouts set for Az and El that can be overridden in need (i.e. battle conditions). [T-0118] A[T].CG, M[O].C, D[O].C, P[T].G

(U) In the case where the ELRF cannot be fired because of the Geodetic Lasing Cutouts, the EOSS SHALL report that these Geodetic Lasing Cutouts are preventing the laser from firing. [T-0119] A[T].CG, M[O].C, D[O].C, P[T].G

(U) The EOSS system SHALL provide an interface to a Deconfliction Safety System (DSS) IAW JLLDS-DSS_LS-IRS-0025-R and inhibit laser firings if indicated by the published message. [T-0120] A[T].CG, M[O].C, P[T].G

(U) In the case where the ELRF cannot be fired because of the DSS, the EOSS SHALL report that this DSS is preventing the laser from firing. [T-0121] A[T].CG, M[O].C, D[O].C, P[T].G

(U) The ELRF SHALL only output the designed wavelength across all environmental and look angles and be filtered below safe levels IAW ANSI-Z136.1. [T-0122] A[T].C, M[T].C, D[O].C, L[T].C

(U) Any ELRF pump wavelength(s) SHALL be filtered below safe levels as determined per LIA Z136.1. [T-0123] A[T].C, M[T].C, D[O].C, L[T].C

(U) ELRF SHALL ensure that lasers only fire when commanded to fire. [T-0124] A[T].C, M[T].C, L[T].C, P[T].G

(U) ELRF laser(s) SHALL have a label stating whether they are registered with the FDA as FDA compliant or MIL-EXEMPT. [T-0125] A[T].CG, I[T].C

(U) Class 1 laser(s) SHALL be labeled stating they are Class 1. [T-0126] A[T].CG, I[T].C

(U) Computer Hardware Requirements

(U) The EOSS SHALL use commercially available military / industrial quality server class Central Processing Unit (CPU) motherboards. [T-0127] A[T].CG

(U) The EOSS system SHALL reserve sufficient space in a below-deck processing rack to accommodate a specified DSS server. [T-0128] A[T].CG

(U) The EOSS SHALL use commercially available graphics processing units. [T-0129] A[T].CG

(U) The EOSS SHALL use commercially available video processing boards. [T-0130] A[T].C, L[T].C, P[T].G

(U) The EOSS SHALL at no time exceed fifty percent (50%) utilization of the system processing resources while meeting all image processing and dissemination requirements. [T-0131] A[T].CG, M[T].C, L[T].C, P[T].G

(U) The EOSS architecture SHALL be capable of future expansion to support one hundred percent (100%) growth in delivered capacity for computational processing, memory, and internal network bandwidth. [T-0132] A[T].CG, M[O].C

(U) The hardware to support this one hundred percent (100%) spare capacity need not be initially installed to support this requirement. [T-0133] A[T].CG

(U) The EOSS data, video, imagery, and MD storage capability SHALL be approved, certified per the Joint Interoperability Test Command (JITC), and listed on the Defense Information System Agency (DISA) DoD Unified Capabilities (UC) Approved Product List (APL) per DoDI 8100.04 and the UC APL Process Guide Version 2.4, or most current. [T-0134] A[T].CG, L[T].C

(U) The EOSS data, video, imagery, and MD storage capability SHALL meet and be certified to TEMPEST standard IAW Title 48 CFR, Part 239. [T-0135] A[T].C, L[T].C/G

(U) The EOSS data storage capability SHALL be evaluated and certified by the National Information Assurance Partnership (NIAP) to be accredited and conform to the Common Criteria for IT Security [T-0136] A[T].C, L[T].C

(U) The EOSS data storage capability SHALL be evaluated per ISO/IEC 15408 (Parts 1, 2, and 3) with the removable hard drives being listed on the NIAP product compliant list. [T-0137] A[T].C, L[T].C

(U) EOSS Network Infrastructure

(U) Due to the high bitrates associated with combined VIS and TIS architecture, a ten (10) Gigabit Ethernet network infrastructure or greater SHOULD be used within the EOSS. [O-0138] A[T].C, L[T].C, P[T].G

(U) The EOSS BDE SHALL have separate MI/MD outputs that are software configurable as to the Class of video that is output for external system video interfaces, the number of required ports are defined by the number of external systems interfaced, the required display presets, and individual imager feeds required with room for inclusion of additional ports for video distribution growth, with a minimum number related to the number of Human Machine Interface (HMI) display presets and number of imagers included. [T-0139] A[T].CG, M[O].C, L[T].C, P[T].G

(U) The EOSS SHALL provide any MI/MD to the GWS LAN that an operator may command through a DiVDS console. [T-0140] A[T].CG, M[O].C, P[T].G

(U) The EOSS SHALL provide any MI/MD to the GWS LAN that the DiVDS system may select. [T-0141] A[T].CG, M[O].C, P[T].G

(U) The EOSS SHALL receive ship’s Positioning, Navigation, and Timing (PNT) via the Combat System's LAN IAW navigation message definitions and formats. [T-0142] A[T].C, M[O].C, L[T].C/G, P[T].G

(U) The EOSS ADE and BDE SHALL provide software and user interface access to sensor raw image count value arrays within real time constraints. [T-0143] A[T].CG, M[O].C, L[T].CG, P[T].G

(U) The EOSS ADE and BDE SHALL provide software and user interface access to inject virtual image count value arrays within real time constraints. [T-0144] A[T].CG, M[O].C, L[T].CG, P[T].G

(U) The EOSS communications connections SHOULD comply with T9070-BY-DPC‑010/457-1, hereby known as DPC (Design Practices and Criteria), section 3-1.3.3. [O-0145] A[T].CG, M[O].C

(U) The EOSS video connections SHOULD comply with section 3-1.3.3 of the DPC. [O-0146] A[T].CG, M[O].C

(U) The EOSS auxiliary (if used) connections SHOULD comply with section 3-1.3.3 of the DPC. [O-0147] A[T].CG, M[O].C

(U) The EOSS SHOULD have a dedicated port for testing and maintenance of the VIS. [O-0148] A[T].CG, M[O].C, L[T].C

(U) Note: see section 3.25.5.

(U) The EOSS SHOULD have a dedicated port for testing and maintenance of the TIS. [O-0149] A[T].CG, M[O].C, L[T].C

(U) Note: see section 3.25.5.

(U) The EOSS SHOULD have a dedicated port for testing and maintenance of the ELRF. [O-0150] A[T].CG, M[O].C, L[T].C

(U) Note: see section 3.25.5.

(U) The EOSS SHOULD have a dedicated port for testing and maintenance of the Director. [O-0151] A[T].CG, M[O].C, L[T].C

(U) Note: see section 3.25.5.

(U) The EOSS SHALL have a dedicated port for testing and maintenance of the BDE. [T-0152] A[T].CG, M[O].C, L[T].C

(U) Note: see section 3.25.5.

(U) The EOSS SHALL have a dedicated port for testing and maintenance of the AVT. [T-0153] A[T].CG, M[O].C, L[T].C

(U) Note: see section 3.25.5.

(U) Built In Test (BIT)

(U) The EOSS SHALL have Built In Tests (BITs). [T-0154] A[T].CG, M[O].C, L[T].C, P[T].G

(U) The EOSS BITs SHALL detect and report faults to the appropriate LRU or module level. [T-0155] A[T].CG, M[O].C, L[T].C, P[T].G

(U) Note: A critical fault is defined as a fault which impacts a critical function and prevents the system from completing any one or more assigned mission tasks below.

a. Observe the target

b. Ability to maintain the EOSS line of sight on the target

c. Target bearing, elevation and range measurement

d. Confirmation of clear line of sight

e. Weapon aim adjustments

(U) The EOSS SHALL detect critical faults, which result in the loss of mission essential functionality while preparing for and performing the mission. [T-0156] A[T].CG, M[O].C, L[T].C, P[T].G

(U) All faults, regardless of criticality, SHALL be identified with enough terminology precision to support maintenance activity. [T-0157] A[T].CG, L[T].C, P[T].G

(U) All faults SHALL be traceable to the Failure Modes Effects and Criticality Analysis (FMECA), which will be the single point of failure mode determination. [T-0158] A[T].CG

(U) Note: Fault detection rate is defined as the number of correct detections divided by the total number of confirmed faults, with the result multiplied by one hundred (100) (to express the quotient as a percentage).

(U) The EOSS SHALL have a BIT hardware fault detection rate of ninety nine percent (99%) while in the Maintenance State. [T-0159] A[T].CG, M[O].C, L[T].C

(U) The EOSS SHOULD have a BIT hardware fault detection rate of one hundred percent (100%) while in the Maintenance State. [O-0160] A[T].CG, M[O].C, L[T].C

(U) The EOSS SHALL have a BIT critical fault detection rate of ninety five percent (95%) when installed on host platform. [T-0161] A[T].CG, M[O].C, L[T].C

(U) The EOSS SHOULD have a BIT critical fault detection rate of one hundred percent (100%) when installed on host platform. [O-0162] A[T].CG, M[O].C, L[T].C

(U) Note: BIT fault isolation rate is defined as the total number of failures correctly isolated by BIT to the faulty LRU or module divided by the total number of failures detected by BIT, with the result multiplied by one hundred (100) (to express the quotient as a percentage).

(U) The EOSS SHALL have a BIT fault isolation rate of greater than or equal to ninety percent (90%). [T-0163] A[T].CG, M[O].C, L[T].C

(U) The EOSS SHOULD have a BIT fault isolation rate of greater than or equal to ninety five percent (95%). [O-0164] A[T].CG, M[O].C, L[T].C

(U) BIT functions automatically initiated during system initialization SHALL not exceed the power state transition times of this specification. [T-0165] A[T].CG, M[O].C, L[T].C, P[T].G

(U) Multiple point failures and/or wiring faults SHALL be diagnosed by the collective use of BIT, equipment specific trouble shooting guides, general trouble shooting procedures, cable assembly and wiring schematics and operating procedures. [T-0166] A[T].C, M[O].C, L[T].C

(U) BIT reports SHOULD be recorded for use in analyzing and improving the EOSS as…