SOSA Consortium Charters

GOALS

Ensure that the SOSA Modules are defined with sufficient fidelity that systems can be built using their definitions (including both functionality and interfaces) to the Mission Thread priorities outlined by the Steering Committee
Ensure that SOSA Modules being defined for Missions Thread priorities focus on commonality first and specialization, second, if needed
Ensure coherence across the Technical Standard in terms of both content (coherence between the Modules and Infrastructure) and form (consistency of how the information is represented)
Ensure coherence between the TS, the Business Guide, and the Conformance Program (e.g., terminology and meaning)
Ensure SOSA Modules and Infrastructure are properly aligned with procurement and system/subsystem concepts
Ensure we are levying our resources against our goals e.g. not over taxing certain individuals
Foster commonality while enabling divide and conquer

TWG �� Chair: Jason Dirner �� Vice Chair: Kirk Avery

The Technical Working Group (TWG) reports to the Steering Committee. The TWG takes general direction from the Steering Committee with respect to objectives and priorities for future releases of the Technical Standard (TS) and provides guidance down to its member Committees and Subcommittees to execute the Steering Committee’s direction.

The TWG is the SOSA Consortium body responsible for maintaining and updating the SOSA TS and the Reference Implementation Guide (RIG). The TWG ensures coherence across the TS in terms of both content (coherence between the Modules and Infrastructure) and form (consistency of how the information is represented).

The TWG collaborates with the Business Working Group (BWG) and Conformance Standing Committee (CStC) to maintain coherence of the SOSA Technical Standard with the Business Guide and Conformance Program Guides, respectively, as well as resolve any disconnects. The TWG also works closely with the Architecture Standing Committee (AStC) to maintain the SOSA Architecture.

The TWG is the body responsible for approving proposed updates and modifications to the TS and RIG content. The TWG executes the change process for the TS and RIG. The TWG also manages any issues against the TS and RIG which require adjudication. The TWG reviews need statements to determine applicability of new change proposals and identify which Subcommittees or Task Teams are responsible for generating the content. The TWG also coordinates with the BWG, AStC, and CStC Chairs to determine whether need statements are within the scope of the Steering Committee’s direction.

Modules Committee �� Chair: Shawn Reese �� Vice Chairs: Jason Dirner (A)-Kirk Avery (A)

The SOSA Modules Committee reports to the Technical Working Group (TWG). Its responsibilities are:

Reviewing SOSA Module need statements for updates to the Technical Standard (TS) and conducting a straw poll before sending to the TWG, BWG, AStC, and CStC Chairs for approval.
Guiding SOSA Module development.
Reviewing SOSA Module change proposals and conducting a straw poll before sending to the TWG for review and approval.
Holding periodic meetings to provide status of its Subcommittees and associated change proposals.

The Modules Committee ensures balanced development of the Modules to achieve complete and mature Module definitions. The Modules Committee guides this development by:

Generating and reviewing need statements for change proposals under direction of the TWG Leadership. Ensuring need statements include a detailed rationale and trace to Steering Committee objectives.
Prioritizing need statements based on Steering Committee objectives, TWG Leadership direction, and Modules Committee resource availability.
Maintaining a backlog of need statements and associated change proposals that do not align with Steering Direction and are consequently not approved for execution.
Assigning need statement to Modules Subcommittees to develop the associated change proposal(s).

Reviewing change proposal material developed by the Modules Subcommittees to ensure commonality across the SOSA Modalities

Infrastructure Committee �� Chair: Patrick Collier �� Vice Chair: Keith Zell

The SOSA Infrastructure Committee reports to the Technical Working Group (TWG). Its responsibilities are:

Reviewing SOSA Infrastructure Element need statements for updates to the SOSA Technical Standard (TS) and conducting a straw poll before sending to the TWG, BWG, AStC, and CStC Chairs for approval.
Guiding SOSA Infrastructure Element development.
Reviewing SOSA Infrastructure Element change proposals and conducting a straw poll before sending to the TWG for review and approval.
Holding periodic Infrastructure Committee meetings to provide status of its Subcommittees and associated change proposals.

The Infrastructure Committee ensures balanced development of all SOSA Infrastructure Elements with fully defined interfaces used to implement SOSA Modules. The Infrastructure Committee guides this development by:

Generating and reviewing need statements for Infrastructure Element enhancements under direction of the TWG Leadership. Ensuring need statements include a detailed rationale and trace to Steering Committee objectives.
Prioritizing need statements based on Steering Committee objectives, TWG Leadership direction, and Infrastructure Committee resource availability.
Maintaining a backlog of need statements and associated change proposals that do not align with Steering Direction and are consequently not approved for execution.
Assigning need statement to Infrastructure Subcommittees to develop the associated change proposal(s).
Reviewing change proposal material developed by the Infrastructure Subcommittees to ensure commonality across the SOSA Infrastructure.

SOSA Management Modules �� Lead: Ray Dellefave �� Co-Lead: Dan Toohey

The SOSA Management Modules Subcommittee reports to the SOSA Modules Committee in the Technical Working Group (TWG). It is responsible for the content in the following sections of the SOSA Technical Standard (TS) which cover the SOSA 1.X Modules:

Technical Concepts and Overview: System Management Approach
System Management (all sections except for Out-of-Band Hardware Management)
Task Manager

In carrying out its responsibilities, the SOSA Management Modules Subcommittee may / will:

Generate rationales and need statements for changes or enhancements to the 1.X SOSA Modules. The explanation of need are sent to the Modules Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the 1.X SOSA Modules as directed by the Modules Committee
Provide suggestions for SvcV-1 updates for 1.X SOSA Modules to the Architecture Standing Committee (AStC)
Generate CPs for updates to the Function list (SvcV-4) for the 1.X SOSA Modules
Generate CPs for updates to the Interaction list for the 1.X SOSA Modules
Generate draft data products for 1.X SOSA Module homed interactions to send to the Data Model Subcommittee for final adoption
Collaborate with the Infrastructure Committee to ensure sufficient implementation options are available for 1.X SOSA Modules
Collaborate with other SOSA Module Committee subcommittees and the Infrastructure Committee on crosstalk issues

SOSA Transmit/Reception Modules �� Lead Derek Bailey �� Co-Leads: Finley Hicks, Bryan Clark

The SOSA Transmit/Reception Modules Subcommittee reports to the SOSA Modules Committee in the Technical Working Group (TWG). It is responsible for the content in the following sections of the SOSA Technical Standard (TS) which cover the SOSA 2.X Modules:

Transmission/Reception

In carrying out its responsibilities, the SOSA Transmit/Reception Modules Subcommittee may / will:

Generate rationales and need statements for changes or enhancements to the 2.X SOSA Modules. The explanation of need are sent to the Modules Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the 2.X SOSA Modules as directed by the Modules Committee
Provide suggestions for SvcV-1 updates for 2.X SOSA Modules to the Architecture Standing Committee (AStC)
Generate CPs for updates to the Function list (SvcV-4) for the 2.X SOSA Modules
Generate CPs for updates to the Interaction list for the 2.X SOSA Modules
Generate draft data products for 2.X SOSA Module homed interactions to send to the Data Model Subcommittee for final adoption
Collaborate with the Infrastructure Committee to ensure sufficient implementation options are available for 2.X SOSA Modules
Collaborate with other SOSA Module Committee subcommittees and the Infrastructure Committee on crosstalk issues

SOSA Processing, Analyzing, and Exploitation Modules: Lead: Niraj Srivastave �� Co-Leads: Bryan Clark, Bob Serafinkio

The SOSA Processing, Analyzing, and Exploitation Modules Subcommittee reports to the SOSA Modules Committee in the Technical Working Group (TWG). It is responsible for the content in the following sections of the SOSA Technical Standard (TS) which cover the SOSA 3.X and 4.X Modules:

Process Signals/Targets
Analyze and Exploit

In carrying out its responsibilities, the SOSA Processing, Analyzing, and Exploitation Modules Subcommittee may / will:

Generate rationales and need statements for changes or enhancements to the 3.X and 4.X SOSA Modules. The explanation of need are sent to the Modules Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the 3.X and 4.X SOSA Modules as directed by the Modules Committee
Provide suggestions for SvcV-1 updates for 3.X and 4.X SOSA Modules to the Architecture Standing Committee (AStC)
Generate CPs for updates to the Function list (SvcV-4) for the 3.X and 4.X SOSA Modules
Generate CPs for updates to the Interaction list for the 3.X and 4.X SOSA Modules
Generate draft data products for 3.X and 4.X SOSA Module homed interactions to send to the Data Model Subcommittee for final adoption
Collaborate with the Infrastructure Committee to ensure sufficient implementation options are available for 3.X and 4.X SOSA Modules
Collaborate with other SOSA Module Committee subcommittees and the Infrastructure Committee on crosstalk issues

Security Subcommittee �� Lead: Ken Walsh �� Co-Lead: Tony Pierce �� Frank Costantini

The Security Subcommittee reports to the Modules Committee in the Technical Working Group (TWG). The Security Subcommittee is responsible for making recommendations and performing evaluations of the security aspects (including cybersecurity, resiliency, and Zero Trust) of the SOSA Reference Architecture and for the content in the following sections of the SOSA Technical Standard(TS) which cover the SOSA 6.1, 6.2 and 6.3 Modules:

Security Services Module
Encryptor/Decryptor
Guard/Cross-Domain

In carrying out its responsibilities, the Security Subcommittee may / will:

Generate rationale or need statement for changes or enhancements to the 6.1, 6.2, and 6.3 SOSA Modules. The need statements are sent to the Modules Committee for review and potential forwarding to the TWG.
Generate Change Proposal (CP) content for the 6.1, 6.2, and 6.3 SOSA Modules as directed by the Modules Committee
Provide suggestions for SvcV-1 updates for 6.1, 6.2, and 6.3 SOSA Modules to the Architecture Standing Committee (AStC)
Generate CPs for updates to the Function list (SvcV-4) for the 6.1, 6.2, and 6.3 SOSA Modules
Generate CPs for updates to the Interaction list for the 6.1, 6.2, and 6.3 SOSA Modules
Generate draft data products for 6.1, 6.2, and 6.3 SOSA Module homed interactions to send to the Data Model Subcommittee for final adoption
Generate need statements and CPs for security-related updates to interactions.
Collaborate with the Management Modules Subcommittee (1XSC) on Security Management.
Collaborate with the Infrastructure Committee to ensure sufficient implementation options are available for 6.1, 6.2, and 6.3 SOSA Modules
Collaborate with the Infrastructure Committee on the security aspects of infrastructure elements
Participate, as requested, in subcommittees and task teams to assist in the development of change proposals that contain Security related topics.
After final adoption of a Security related CP, document the CP additions/modifications in the RIG.
Review, add and/or modify Security Related RIG content.

In the spirit of “baked in, not bolted on,�� the SSC does not produce security products distinct from the SOSA Technical and Business Architectures. Instead, the role of the SSC is to ensure that the security is cohesively infused into them.

Reference Implementation Guide �� Lead: Alva Webster �� Co-Lead: Brent Gessel

The Reference Implementation Guide (RIG) Committee reports to the SOSA Technical Working Group. The RIG Committee is chartered to develop and maintain the SOSA RIG document. The primary goal of the SOSA RIG is to provide practical application and understanding for implementation of requirements specified in the SOSA Technical Standard.

The RIG Committee interacts with all other SOSA TWG Committees and Subcommittees to ensure RIG information accurately interprets, and is consistent with, the SOSA Technical Standard. The RIG Committee is responsible for planning and executing content goals for each release based on direction from the TWG. The RIG Committee executes the configuration management plan for the RIG document which enforces style guidelines and ensures quality control.

SOSA Support System Modules: Lead: Michael Moore �� Co-Lead: TBD

The SOSA Support System Modules Subcommittee reports to the SOSA Modules Committee in the Technical Working Group (TWG). It is responsible for the content in the following sections of the SOSA Technical Standard (TS) which cover the SOSA 6.X Modules which are not Security centric:

Network Subsystem
Calibration Service
Position, Navigation, and Timing Service
Compressor/Decompressor
Host Platform Interface
Power

In carrying out its responsibilities, the SOSA Support System Modules Subcommittee may / will:

Generate rationales and need statements for changes or enhancements to the 6.X SOSA Modules. The explanation of need are sent to the Modules Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the 6.X SOSA Modules as directed by the Modules Committee
Provide suggestions for SvcV-1 updates for 6.X SOSA Modules to the Architecture Standing Committee (AStC)
Generate CPs for updates to the Function list (SvcV-4) for the 6.X SOSA Modules
Generate CPs for updates to the Interaction list for the 6.X SOSA Modules
Generate draft data products for 6.X SOSA Module homed interactions to send to the Data Model Subcommittee for final adoption
Collaborate with the Infrastructure Committee to ensure sufficient implementation options are available for 6.X SOSA Modules
Collaborate with other SOSA Module Committee subcommittees and the Infrastructure Committee on crosstalk issues

DEWS �� Lead: Grace Unangst �� Co-Lead: TBD

The DEWS Subcommittee reports to the Modules Committee under the Technical Working Group (TWG). This subcommittee extends the work started in the development of the Directed Energy Weapon Systems Reference Architecture (DEWS RA) and works to have the DEWS RA integrated with the SOSA Architecture. The DEWS Subcommittee is responsible for the DEWS appendix to the SOSA Technical Standard (TS).

In carrying out its responsibilities, the DEWS Subcommittee may / will:

Generate rationales or need statements for changes or enhancements to the DEWS-unique SOSA Modules, and harmonization of DEWS-SOSA common modules. The explanation of need are sent to the Modules Committee for review and potential forwarding to the TWG.
Generate Change Proposal (CP) content for the DEWS Modules as directed by the Modules Committee
Generate CPs for updates to the Function list (SvcV-4) for the DEWS Modules
Generate CPs for updates to the Interaction list for the DEWS Modules
Generate draft data products for DEWS Module homed interactions to send to the Data Model Subcommittee for final adoption
Collaborate with the Infrastructure Committee to ensure sufficient implementation options are available for DEWS Modules
Collaborate with other SOSA Module Subcommittees to create full compatibility with the SOSA-DEWS common modules
Collaborate with the Architecture Standing Committee (AStC) to add / update the SOSA-DEWS common modules

VICTORY �� Lead: Kase Saylor �� Co-Lead: Jason Broczkowski

The Vehicular Integration for C4ISR/EW Interoperability (VICTORY) Subcommittee (VSC) reports to the SOSA Modules Committee in the Technical Working Group (TWG). It is responsible for maintaining the VICTORY Standard Specifications that have not been adopted by the SOSA Technical Standard.

The VSC maintains associated specifications in separate documents until such time that they have been included in their entirety in the SOSA Technical Standard.

The VSC works with other subcommittees within the Technical Working Group (TWG) to incorporate relevant VICTORY specifications in the SOSA Technical Standard (TS) as directed by the Modules Committee.

SPACE SEGMENT �� Lead: Wesley Powell �� Co-Lead: Mehmet Adalier

The SOSA S3C reports to the SOSA Infrastructure Committee in the Technical Working Group (TWG). It is responsible for all sensor and avionics technical aspects that affect the development of SOSA Elements deployed in space.

The SOSA S3C works to achieve broad adoption of a convergence strategy across NASA and other Government Space Agencies and Industry. The convergence focuses on maximizing reuse and portability across a variety of platforms and use cases.

In carrying out its responsibilities, the S3C:

Generate rationales or need statements for changes or enhancements to existing SOSA Infrastructure specific to capabilities across multiple space sensor systems and space avionics.
The explanation of need are sent to the Infrastructure Committee for review and potential forwarding to the TWG.
Generate Change Proposal (CP) content as directed by the Infrastructure Committee.
Collaborate with other SOSA Infrastructure Subcommittees for CP content relative to deploying SOSA Infrastructure in space
Collaborate with other SOSA Module Committee Subcommittees to develop relevant technical content for functionality deployed in space
Collaborate with the Architecture Standing Committee (AStC) for use cases in space sensors, applications, and avionics.

Hardware Electro-Mechanical �� Lead: Paul Mesibov- Co-Leads:Herb Van Duesen-Terry Hulett

The Hardware Electro-Mechanical Subcommittee reports to the Infrastructure Committee under the Technical Working Group (TWG). This subcommittee specifies the mechanical, electrical, and low layer protocols utilized by SOSA Infrastructure Hardware Elements (Plug-in Cards (PICs), Chassis, Power Supplies, Apertures, and sub-derivatives thereof).

The Hardware Electro-Mechanical Subcommittee is responsible for the following sections of the Technical Standard (TS):

6.4 (and sub-sections) Out-Of-Band Management
13.1 PIC Use Cases
13.2 SOSA PICs Using OpenVPX
13.3 Alternate Module Profile Scheme (AMPS)
13.5 SOSA Aperture and Chassis Electrical and Mechanical Interface Standard

In carrying out its responsibilities, the Hardware Electro-Mechanical Subcommittee may / will:

Generate rationales and need statements for changes or enhancements to the SOSA PICs or Aperture and Chassis interfaces. The explanation of need are sent to the Infrastructure Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the SOSA PICs or Aperture and Chassis interfaces as directed by the Infrastructure Committee
Collaborate with the Management Modules Subcommittee concerning interactions involving SOSA PICs, Apertures, or Chassis
Collaborate with the Security Subcommittee concerning Security Module implementations and enabling security of the HW Elements

Small Form Factor �� Lead: Chris Schnelle �� Co-lead: Andy Walker

The Small Form Factor Subcommittee (SFFSC) reports to the Infrastructure Committee under the Technical Working Group (TWG). This subcommittee specifies the mechanical, electrical, and low layer protocols utilized by SOSA Infrastructure Hardware Element Plug-in Cards (PICs) utilizing VITA 90 VNX+.

The SFFSC is responsible for the following sections of the Technical Standard (TS):

13.4 SOSA PICs Using VNX+

In carrying out its responsibilities, the SFFSC may / will:

Generate rationales and need statements for changes or enhancements to the SOSA SFF PIC interfaces. The explanation of need are sent to the Infrastructure Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the SOSA SFF PIC interfaces as directed by the Infrastructure Committee
Collaborate with the Management Modules Subcommittee concerning interactions involving SOSA SFF PICs
Collaborate with the Security Subcommittee concerning Security Module implementations and enabling security of the HW Elements
Collaborate with the Hardware Electro-Mechanical Subcommittee concerning Apertures and Chassis utilizing SOSA SFF PICs

Interaction- Lead: Garrett Sargent �� Co-Lead: Matt Vergo

The Interaction Subcommittee reports to the Infrastructure Committee under the Technical Working Group (TWG). This subcommittee specifies the means by which the SOSA Interactions are implemented over physical mediums and via Software APIs.

The Interaction Subcommittee is responsible for the following sections of the Technical Standard (TS):

5.4 SOSA Inter-Module Interactions
15 Inter-Module Interaction Implementation

In carrying out its responsibilities, the Interaction Subcommittee may / will:

Generate rationales and need statements for changes or enhancements to the Interaction Bindings or Software APIs. The explanation of need are sent to the Infrastructure Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the Interaction Bindings or Software APIs as directed by the Infrastructure Committee
Collaborate with the Modules Committee and its subcommittees to ensure sufficient implementation options for the Modules
Collaborate with the Security Subcommittee to enable security of Interactions
Collaborate with the Architecture Standing Committee on updates to the SOSA Interaction fundamentals described in section 5.4
Develop any tooling required to generate Interaction Bindings from the Data Model

Develop any interface documents required to implement an interaction using an Interaction Binding

Software Environment �� Lead: Mike Majors �� Co-Lead: Mike Orlovsky

The Software Environment Subcommittee reports to the Infrastructure Committee under the Technical Working Group (TWG). This subcommittee specifies the interfaces between the SOSA Runtime Environments (FACE, Containers, and Virtual Machines) and the SOSA Module implementations utilizing them.

The Software Environment Subcommittee is responsible for the following sections of the Technical Standard (TS):

14.1 Overview
14.2 SOSA Configuration Files
14.3 FACE OSS Run-Time Environment Profile
14.4 SOSA Container Run-Time Environment Profile
14.5 SOSA Virtual Machine RTE Profile
14.6 Mixed Run-Time Environments

In carrying out its responsibilities, the Software Environment Subcommittee may / will:

Generate rationales and need statements for changes or enhancements to the SOSA Software Runtime Environments interfaces. The explanation of need are sent to the Infrastructure Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the SOSA Software Runtime Environments interfaces as directed by the Infrastructure Committee
Collaborate with the Management Modules Subcommittee concerning interactions involving SOSA Software Runtime Environments
Collaborate with the Security Subcommittee concerning Security Module implementations and enabling security of the SOSA Software Runtime Environments

Hardware Acceleration Environment �� Lead: Finley Hicks �� Co-Lead: Tim Coulter

The Hardware Acceleration Environment Subcommittee reports to the Infrastructure Committee under the Technical Working Group (TWG). This subcommittee specifies the interfaces between the SOSA Runtime Environments for FPGAs and GPGPUs and the SOSA Module implementations utilizing them.

The Hardware Acceleration Environment Subcommittee is responsible for the following sections of the Technical Standard (TS):

14.7 FPGA Run-Time Environment

In carrying out its responsibilities, the Hardware Acceleration Environment Subcommittee may / will:

Generate rationales and need statements for changes or enhancements to the SOSA FPGA and GPGPU Runtime Environment interfaces. The explanation of need are sent to the Infrastructure Committee for review and potential forwarding to the TWG
Generate Change Proposal (CP) content for the SOSA FPGA and GPGPU Runtime Environments interfaces as directed by the Infrastructure Committee
Collaborate with the Management Modules Subcommittee concerning interactions involving SOSA FPGA and GPGPU Runtime Environments
Collaborate with the Security Subcommittee concerning Security Module implementations and enabling security of the SOSA FPGA and GPGPU Runtime Environments
Collaborate with the Interaction Subcommittee to enable native FPGA and GPGPU Interaction Bindings or Software APIs

Business Working Group �� Chair: Mike Orlovsky �� Vice Chair: George Dalton

The Business Working Group (BWG) reports to the SOSA Steering Committee and is chartered to develop, document and advocate procurement and adoption strategies that are consistent with the SOSA vision and mission and are mutually beneficial to stakeholders (Government and Industry):

The BWG does this by engaging with stakeholders to:
- Establish a viable SOSA ecosystem of developers, suppliers, product certification, and standards evolution to continuing technology acceleration
- Develop business models, views, and use cases which benefit stakeholder interests
- Provide guidance for incorporating the SOSA Technical Standard into products and procurements
- Engage stakeholders to gauge standards adoption in products and application in procurements
- Promote development and adoption of the technical standard through various methods of outreach
- Advocate for improvement and sustainment of an enduring ecosystem supporting the technical standard
Documents championed (and comment adjudicated) by the BWG include:
- The Open Group SOSA�� Enterprise Overview
- The Open Group SOSA�� Business Guide
- The Open Group SOSA�� Acquisition and Contracting Guide
- The Open Group SOSA�� Supplier Guide
- The Open Group SOSA�� Marketing Guidelines

The Open Group SOSA�� Aligned Products Directory

Outreach Committee �� Chair: Valerie Andrew �� Vice Chair: Gina Peter

The Outreach Committee reports to the BWG to promote the SOSA approach (business and technical strategies) and advances the SOSA Consortium by doing the following:

Advise and support consortium members in promoting the consortium and the technical standard
- Reviews accuracy and consistency of marketing materials
- Advise on social media engagement messaging
- Designs and produces marketing materials for Consortium use
- Provides a means to record member adoption of the technical standard through product development
- Monitors procurements for adoption of the technical standard
Collaborate with Open Group marketing and events personnel
- Coordinates events, exhibits, speakers, and presentations
- Coordinates and drafts press releases and news articles
- Coordinates and publicizes the releases of Webinars, Guides, White Papers, and Consortium Data Sheets
- Coordinates other promotional activities, as required

Enterprise Guidance �� Lead: Scott Bailey - Jonathan Cain �� Co-Lead: Jeff Evans

The Enterprise Guidance Committee reports to the BWG and promotes the SOSA approach (business and technical strategies) and advances the SOSA Consortium by doing the following:

Produce and mature models, views and use cases which characterize the business aspects of the SOSA consortium, supporting ongoing development of the SOSA Technical Standard
Collaborate with Architecture Standing Committee (AStC) to align the elements of the SOSA ecosystem with the technical architecture
Collaborate with Conformance Standing Committee (CStC) to align the elements of the SOSA ecosystem with conformance approach, roadmap, and products
Gauge standard adoption in products and standard application in procurements to advise AStC and CStC

Creates guides for the SOSA Enterprise to improve stakeholders and users understanding

BWG Task Teams

Outreach Subcommittee
- Plugfest and Interoperability Demo Task Team
Enterprise Guidance Subcommittee
- SOSA Enterprise Overview Task Team
- Business Guide Task Team
- Acquisition & Contracting Guide Task Team
- Supplier Guide Task Team
- Integrator’s Guide Task Team
- SOSA Enterprise Webinar Task Team

PlugFest and Interoperability Task Team

Conformance �� Chair: Patrick Collier �� Vice Chair: Huan Dao

The Conformance Standing Committee (CStC) reports to the Steering Committee. It is tasked to guide the overall development of a SOSA Conformance Program that includes Verification and Certification arms to assist the creation of SOSA Conformant products through SOSA Conformance Certification.

The CStC coordinates to understand and develop a proper set of Conformant documents that apply equally to all aspects of the SOSA Consortium.

The CStC is responsible for the SOSA Conformance Policy (SCP), the SOSA Conformance Certification Guide (SCCG), Verification Authority Requirements Guide, Verification Matrices, Verification Procedures Document, a PR/CR program (process), and Certification and TMLA Agreements.

The CStC is also responsible for coordinating and guiding the development of Verification Matrices, Conformance Methodologies, all Verification Procedures (whether they are Hardware, Software, or Architecture related), Test Specifications, Test Report Template(s), and Test Suite(s). The CStC coordinates with the Technical Working Group (TWG), its committees and subcommittees, as they develop the Verification Matrices, Verification Procedures, Methodologies, Test Suites, Test Specifications, and Test Report Templates

The CStC is responsible for developing a Problem Report and Change Request (PR/CR) program for addressing updates to any existing Conformance process. The PR/CR program will create Problem Report templates and Change Request templates for use by SOSA Consortium members.

Architecture Standing Committee : Chair: William Shih �� Vice Chair: Steve Davidson

The Architecture Standing Committee (AStC) reports to the SOSA Steering Committee, and is chartered to define and develop formal architecture products that communicate a clear picture of the SOSA Enterprise suitable for a wide variety of Consortium and outside audiences

The AStC ensures internal consistency among the SOSA business strategy and technical architecture through collaboration and coordination with stakeholders that are both internal (e.g., other Subcommittees, Standing Committees, Technical Working Group, and Business Working Group) and external (e.g., related OSA activities)

The AStC also supports the SOSA Technical Standard by using end user input to develop rigorous technical and operational use cases (and associated scenarios and vignettes) that fully characterize the employment, development and evolution of SOSA sensors. The AStC also provides the Conceptual, Logical and Physical Data Models (DIV-1, -2, and -3) for the SOSA Technical Standard (through the Data Model SC),and is chartered to develop a digital model representation of the SOSA Technical Standard (through the Architecture Model SC).

The AStC is responsible for maintaining the content for the following sections of the SOSA Technical Standard:

Architectural Drivers: Quality Attributes and Architecture Principles
SOSA Architecture Overview: SV-1, SvcV-1, and SvcV-2
Technical Concepts and Overview: Taxonomy, Modular Decomposition Approach, SOSA Module Implementation Patterns, SOSA Inter-Module Interactions (in collaboration with the Interaction SC), and SOSA Data Model
AV-2 Integrated Dictionary

The AStC develops rationale for changes or need statements for updates to the above sections of the Technical Standard (TS) and conducts a straw poll before sending to the TWG, BWG, AStC, and CStC Chairs for approval. Once a need statement is approved, the AStC develops and reviews the associate change proposal and conducts a straw poll before sending to the TWG and BWG for final review and approval.

SOSA Use Case �� Lead: TBD �� Co-Lead: TBD

The SOSA Use Case SC (USC) operates under the Architecture Standing Committee (AStC) to make recommendations and perform evaluations of use cases which are broadly applicable across all SOSA Modalities and across all styles of deployment.

The USC is also responsible for identifying gaps in the architecture, functions, processes, interactions, or infrastructure that enable the SOSA Sensor to accomplish the use case. The USC collaborates with the Technical Working Group (TWG) and the Business Working Group (BWG) through the AStC to fill the identified gaps.

ob����

SOSA Consortium Charters

ob��