## Slide 1 ![**SOSA™** Sensor Open Systems Architecture **WIInnComm 2021:** Sensor Open Systems Architecture V1.0 Overview November 30th, 2021 Nick Borton, SOSA Steering Committee Vice Chair (SRC Inc.) **THE Open GROUP**](.sosa-overview-winncomm-2021/slide-001.jpg) ## Slide 2 ![**The SOSA Approach in a Nutshell\*** The SOSA Consortium is a C5ISR-focused technical and business collaborative effort... **What** * Develop a unified technical Open Systems Architecture standard for RADAR, EO/IR, SIGINT, EW, and Communications – and the supporting business models **Why** * Improve sub-system, system, and platform affordability, re-configurability, upgradability, and hardware/software/firmware re-use – and to shorten cycle times to counter emerging threats **Who** * The Air Force, Navy, Army, other government agencies, industry and academia **How** * Developing an OSA via modular decomposition (defining functions and behaviors) and associated interfaces (including physical, protocol, and data structure) between the modules \* Based on abstract of “Sensor Open System Architecture (SOSA) Evolution for Collaborative Standards Development,” SPIE Open Architecture/Open Business Model Net-Centric Systems and Defense Transformation 2017 SOSA Sensor Open Systems Architecture THE Open GROUP 2](.sosa-overview-winncomm-2021/slide-002.jpg) ## Slide 3 ![The slide is titled 'Building with SOSA' and features the 'SOSA Sensor Open Systems Architecture' logo in the top right corner. The main body of text includes the following points: * **SOSA provides a set of tools to build a system with** * System designers choose what tools to use * For Example: only use the SOSA Modules necessary to achieve the Sensor’s Mission * Systems are built with SOSA Components, Systems are not SOSA in and of themselves * **All SOSA Components (or tools) are standardized interfaces** (Note: This text is partially obscured by a large image of a wooden toolbox filled with tools. The visible fragments read 'All SOSA Compo... ts (or tools) are ba... rrdized interfaces'). * Some compone * Other compone * Yet other comp To the right, a grey box labeled **Interface** contains three vertical columns of text: * Physical (Medium) * Protocol (Method) * Signal/Data Structure At the bottom, a light blue banner reads: **Example builds coming up**. The bottom right corner displays the logo for **THE Open GROUP**.](.sosa-overview-winncomm-2021/slide-003.jpg) ## Slide 4 ![Slide 4](.sosa-overview-winncomm-2021/slide-004.jpg) ## Slide 5 ![**Title:** SOSA V1.0 Modules **Logo:** SOSA Sensor Open Systems Architecture **Main Diagram: SOSA Sensor System** **Top Section:** SOSA Sensor Management * 1.1: System Manager * 1.2: Task Manager **Middle Section (Blue Background):** * **Transmission/Reception:** 2.4: Emitter/Collector; 2.3: Conditioner-Receiver-Exciter * **Process Signals/Targets:** 3.1: Signal/Object Detector and Extractor; 3.2: Signal/Object Characterizer; 3.3: Image Pre-Processor; 3.4: Tracker * **Analyze/Exploit:** 4.1: External Data Ingestor; 4.2: Encoded Data Extractor; 4.3: Situation Assessor; 4.4: Impact Assessor and Responder; 4.6: Storage/Retrieval Manager * **Convey:** 5.1: Reporting Services **Bottom Section (Grey Background): Support System Operation** * 6.1: Security Services * 6.2: Encryptor/Decryptor * 6.3: Guard/Cross-Domain Service * 6.4: Network Subsystem * 6.5: Calibration Service * 6.6: Nav Data Service * 6.7: Time & Frequency Service * 6.8: Compressor/Decompressor * 6.10: Power * 6.9: Host Platform Interface **Footer:** 5, THE Open GROUP](.sosa-overview-winncomm-2021/slide-005.jpg) ## Slide 6 ![**Title:** SOSA V1.0 Module High Level Data Flow **Logo (Top Right):** SOSA Sensor Open Systems Architecture **Top Section:** * **Box:** SOSA Sensor Management * 1.1: System Manager * 1.2: Task Manager * **Arrows between SOSA Sensor Management and 6.9:** * System Monitoring and Control * Sensor Tasking * **Box:** 6.9: Host Platform Interface (HPI) * **Arrows between 6.9 and Platform:** * Platform C2 * Sensor Products * **Box:** Platform * **Arrows associated with SOSA Sensor Management:** * Capabilities * Task Scheduling * Resource Management * Task Monitoring * State Control * Config * Health Monitoring * Processed Data * **Arrow below 6.9:** Selected Format from Standard Formats (i.e. JICD 4.2, etc.) **Middle Section (Processing Chain / Data Path):** * **Box:** Transmission/Reception * Emission * 2.4: Emitter/Collector * 2.3: Conditioner-Receiver-Exciter * Collection * Collected Digital Data * **Box:** Process Signals/Targets * 3.1: Signal/Object Detector / Extractor * 3.2: Signal/Object Characterizer * 3.3: Image Pre-processor * Processed Imagery * Characterizations * **Box:** Convey * 5.1: Reporting Services **Bottom Section (System Support Services):** * **Label:** System Support Services * **Box:** 6.2: Encryptor/Decryptor * Data * **Box:** 6.7: Time and Frequency * Time Data * Local Oscillator Frequency * **Box:** 6.6: Nav Data * Relative Pointing Info * Platform Nav **Logo (Bottom Right):** THE Open GROUP](.sosa-overview-winncomm-2021/slide-006.jpg) ## Slide 7 ![**Slide Title:** SOSA Software Runtime Environments (RTE) **Logo (Top Right):** SOSA Sensor Open Systems Architecture **Diagram (Left):** * A stacked block diagram illustrating software layers. * **Bottom Layer:** Orange block labeled 'Hardware Specific'. * **Middle Layer:** Blue block labeled 'SOSA Runtime Environment'. * **Top Layer:** A green block labeled 'Implementation' enclosed in a dashed box labeled 'SOSA Module Software'. * **Interface:** A yellow star labeled 'SOSA Runtime Environment Interface' points to the boundary between the 'Implementation' block and the 'SOSA Runtime Environment' block. * **Labels:** To the left of the stack, 'Software' and 'Hardware' are separated by a dashed line. **Text Content (Right):** The Runtime Environment provides an executable software infrastructure with defined profiles and interfaces which promote interchangeability, portability, and reuse. The profile choices are: * FACE * Containers (conforms to Open Container Initiative) * Virtual Machines (conforms to Open Virtualization Format) **Footer:** THE Open GROUP 7](.sosa-overview-winncomm-2021/slide-007.jpg) ## Slide 8 ![**SOSA Plug-In Cards** **SOSA Sensor Open Systems Architecture** **RF/Optical Payloads** * **Diagram 1 (Top Left)** * SE P0/J0 * Key * Utility Plane * Ground * Maint. Port * Reserved * Utility Plane * Data Plane — 1 Fat Pipe * Data Plane — 1 Ultra-Thin Pipe * CLK1, Maintenance Port * Control Plane — 1 Ultra-Thin Pipe * Expansion Plane — 16 Pairs * P2/J2 * VITA 65 Aperture Pattern H for optical/coax * Key * **Diagram 2 (Top Right)** * SE P0/J0 * Key * Utility Plane * GPIO * Maint. Port * GPIO * Utility Plane * 2 AXresets * 2 EPclocks * GPIO * Data Plane — 4 FP * Expansion Plane — 32 pairs * P3/J3 * 67.3C * Key * VITA 65 Aperture Pattern H for optical/coax * **Diagram 3 (Bottom Right)** * Serial Port(s) * Vid PWR,HPD * USB PWR * Serial Port(s) * Maint. Port * GPIO * Data Plane — 4 UTPs * Video lanes & clock — 1 TP * Video Aux & GP LVDS — 1 SP, 1 SP * 2 of USB — 1 TUTP * Control Plane — 2 UTPs * Control Plane — 2 TP * Expansion Plane — 32 pairs * P6/J6 * 67.3C * VITA 65 Aperture Pattern H for optical/coax * Key * **Diagram 4 (Bottom Left)** * SE P0/J0 * Key * Utility Plane * Ground * Maint. Port * GPIO * Utility Plane * Reserved * P2B/J2B * 67.3D * Key * Data Plane — 1 Fat Pipe * Data Plane — 1 Ultra-Thin Pipe * CLK1orGP, Maintenance Port * Control Plane — 1 Ultra-Thin Pipe * Expansion Plane — 32 Pairs * VITA 65 Aperture Pattern J for optical/coax **Data/Control Plane Switches** * **Diagram 1 (Top Left)** * SE P0/J0 * Key * Utility Plane * Maint. Port * Reserved * Utility Plane * Reserved * Reserved * P2/J2 * Key * Data Plane — 6 Fat Pipes * Ground * Control Plane — 7 Ultra-Thin Pipes * **Diagram 2 (Bottom Left)** * SE P0/J0 * Key * Utility Plane * Maint. Port * Reserved * Utility Plane * Maint. Port * Reserved * P2B/J2B * Key * Data Plane — 4 Fat Pipes * Ground * Control Plane — 7 Ultra-Thin Pipes * **Diagram 3 (Top Right)** * SE P0/J0 * Key * Utility Plane * Reserved * Maint. Port * Reserved * Utility Plane * Reserved * P2/J2 * Key * Data Plane — 14 FPs * **Diagram 4 (Bottom Right)** * SE P0/J0 * Key * Utility Plane * Reserved * Maint. Port * Reserved * Control Plane — UTP * P2B/J2B * Key * Data Plane — 2 TPs * Data Plane — 16 UTPs * Ground * Control Plane — 15 UTPs * VITA 65 Aperture Pattern J for optical/coax **Key Interfaces Provided:** * Mechanical * Electrical Signaling * Some Layer 2 Protocols **THE Open GROUP** 8](.sosa-overview-winncomm-2021/slide-008.jpg) ## Slide 9 ![**Title:** Electrical/Mechanical: Sample Output **Logo:** SOSA Sensor Open Systems Architecture **Diagram (Left):** A circular connector diagram displaying numbered pin locations. Visible numbers include: 1, 6, 7, 15, 16, 18, 19, 24, 25, 32, 33, 41, 42, 46, 53, 59, 60, 67, 68, 71, 74, 75, 76, 81, 82, 94, 99. Two central pins are marked with an asterisk (*). **Table: SOSA Electrical Interface Recommendations** *J2-Signal (25-7 insert, N-Keying)* *For Part Numbers insert receptacle choice (20 or 24) and relevant plating finish* *Sensor MIL-DTL-38999/**J7SN (receptacle with socket inserts)* *Platform Umbilical MIL-DTL-38999/26*J7PN (plug with pin inserts)* **Columns:** Conn/Desc., Pin, Wire Type, Signal Name, Signal Source, Signal Type, Used (EO-IR Turreted Sensor), Used (Radar/SAR Turreted Sensor), Used (EW Sensor), Used (SIGINT Sensor), Used (Comms) **Rows:** * **Ethernet:** Pins 28, 35, 36, 44, 53, 62, 45, 54, 63, 70, 71, 78. Wire: 100Ω STP - AWG24, CAT 6A, SAE AS 6070/6. Signals: DA+, DA-, DA Shield, DB+, DB-, DB Shield, DC+, DC-, DC Shield, DD+, DD-, DD Shield. Source: Platform/Sensor. Type: 1000BaseT. (Checkmarks present in all 'Used' columns). * **Serial Comms 1:** Pin 7. Wire: 100 Ohm STP 2419. Signal: TX1+. Source: Sensor. Type: RS422. (Checkmarks present in all 'Used' columns). * Pin 8. Wire: 100 Ohm STP 2419. Signal: TX1-. Source: Sensor. * Pin 17. Wire: SC-AWG24. Signal: 422_1 RTN. * Pin 16. Wire: 100 Ohm STP 2419. Signal: RX1+. Source: Platform. * Pin 23. Wire: 100 Ohm STP 2419. Signal: RX1-. Source: Platform. * **Serial Comms 2:** Pin 22. Wire: 100 Ohm STP 2419. Signal: TX2+. Source: Sensor. Type: RS422. (Checkmarks present in all 'Used' columns). * Pin 30. Wire: 100 Ohm STP 2419. Signal: TX2-. Source: Sensor. Type: RS422. * Pin 29. Wire: SC-AWG24. Signal: 422_2 RTN. Type: RS422. * Pin 37. Wire: 100 Ohm STP 2419. Signal: RX2+. Source: Platform. Type: RS422. * Pin 38. Wire: 100 Ohm STP 2419. Signal: RX2-. Source: Platform. Type: RS422. * **Emission Arming:** Pin 2. Wire: AWG22. Signal: MASTER_ARM. Source: Platform. Type: open/closed ckt. (Checkmark present in 'EO-IR Turreted Sensor'). * Pin 95. Wire: AWG22. Signal: MASTER_ARM_RET. Source: Platform. Type: open/closed ckt. (Checkmark present in 'EO-IR Turreted Sensor'). **Footer:** THE Open GROUP 9](.sosa-overview-winncomm-2021/slide-009.jpg) ## Slide 10 ![The slide is titled 'Inter-Module Interaction Bindings.' In the top right corner is the SOSA logo with the text 'Sensor Open Systems Architecture.' The slide content is divided into two main sections: **Left Side:** * **Bullet Point:** 'Specific Communications Technology choices to enable the following:' * **Sub-bullets:** * 'Interchangeability' * 'Upgradeability' * 'Portability' * 'Reuse' * **Image:** A photograph of a tangled pile of various black, blue, and red cables and connectors. * **Bullet Point:** 'Provides protocol structure and low-level data encodings for information exchange' **Right Side:** * **Header:** 'Current Binding List:' * **List:** * 'MORA' * 'OAS REST' * 'OMG DDS' * 'ZMTP' * 'AMQP' * 'NVMe (PCIe)' * 'NVMe over RoCEv2' **Footer:** * Bottom right corner displays 'THE Open GROUP' logo and the page number '10'.](.sosa-overview-winncomm-2021/slide-010.jpg) ## Slide 11 ![**Title:** SOSA Component Usage AKA Instantiation Examples **Logo:** SOSA Sensor Open Systems Architecture **Section 1 (Top Row):** * **Left Box:** 3.1: Signal/Object Detector and Extractor * **Middle Diagram:** A vertical stack labeled 'Process Address Space Software for SOSA Module' containing: * Green block: SOSA Module Software Implementation * Blue blocks: SOSA Interactions, FACE OSS Profile * Orange block: Host OS * Yellow block: Board Support / Drivers * Label at bottom: HW * **Text Note:** SOSA Module software is required to use the SOSA Interactions (i.e. FACE TSS) to communicate with other SOSA Modules. * **Legend:** SOSA Module Software, SOSA Runtime Environment, Processing Environment SW, Hardware Centric * **Right Box:** SOSA Interaction Infrastructure Bindings **Section 2 (Middle Row):** * **Left Box:** 2.4: Emitter/Collector * **Middle Diagram:** Labeled 'Firmware'. It depicts a VITA 65 connector with pinouts: * SE P0/J0 * S * E Diff * P1/J1 * P2/J2 * Key * **Text Labels:** Utility Plane, Ground, Maint. Port, Reserved, Utility Plane, Data Plane — 1 Fat Pipe, Data Plane — 1 Ultra-Thin Pipe, CLK1, Maintenance Port, Control Plane — 1 Ultra-Thin Pipe, Expansion Plane — 16 Pairs, VITA 65 Aperture Pattern H for optical/coax, Key * **Right Box:** SOSA Interaction Infrastructure Bindings **Section 3 (Bottom Row):** * **Left Box:** 4.6: Storage/Retrieval Manager * **Middle Diagram:** VITA 65 connector diagram (identical to Section 2). * **Right Diagram:** Vertical stack labeled 'Process Address Space Software for SOSA Module' (identical to Section 1): * SOSA Module Software Implementation * SOSA Interactions, FACE OSS Profile * Host OS * Board Support / Drivers * HW * **Text Note:** SOSA Module software is required to use the SOSA Interactions (i.e. FACE TSS) to communicate with other SOSA Modules. * **Legend:** SOSA Module Software, SOSA Runtime Environment, Processing Environment SW, Hardware Centric * **Right Box:** SOSA Interaction Infrastructure Bindings **Footer:** 11](.sosa-overview-winncomm-2021/slide-011.jpg) [🔗 Link to the original document](.sosa-overview-winncomm-2021/sosa-overview-winncomm-2021.pdf)