DID FinderBack
Source
DI-SESS-82400A

System Architecture Model (SAM)

Defines the System Architecture Model (SAM), a SysML-based representation of system architecture capturing structure, behavior, data, and relationships used as the authoritative source for the system design baseline.

Approval DateJune 16, 2026
AMSC Number10678
Preparing Activity19
Project NumberSESS-2026-001
OPR—
DTIC ApplicableNo
GIDEP ApplicableNo
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Supersedes
DI-SESS-82400
Related
—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The System Architecture Model (SAM) is a representation of the system architecture that includes interrelationships between model elements and data and information. The SAM is the authoritative source of structure, behavior, data, and relationships among them (provided that it is consistent with the latest Government approved design baseline or release and changes are made through CM changed control). This Data Item Description (DID) is written for models developed in the Object Management Group (OMG) System Modeling Language (SysML) v1 [1] although many of the content requirements can be adopted to models developed in other languages such as SysML v2 [2], and the Unified Architecture Framework Modeling Language (UAFML) [3] for those views within UAFML that cover the same subject matter as SysML. Further information on rationale, acceptance criteria, tailoring, and additional comments is contained in a separate document [4].

This DID contains the format, content, and intended use for the data product resulting from the work task described in the contract Statement of Work/Performance Work Statement.

This DID supersedes DI-SESS-82400.

Definitions:

Acquiring Organization: The entity funded and responsible for producing the System of Interest (SOI) and that issues one or more contracts for the development of the SOI and the SAM

Contractually Required: An action, task, standard, or other requirement stated in the contract between the SOI developer, model developer and the Acquiring Organization.

Functional Architecture: An architectural model that identifies system function, subfunctions, and their interactions. It defines how the functions will operate together to perform the system mission(s). Functional architecture can be used as a framework to arrange information, processes, or other solution modules in an enterprise system. [5]

Logical Architecture: A set of related technical concepts and principles that support the logical operation of the system. It is traceable to Functional Architecture and the Physical Architecture. [6]

Physical Architecture: An arrangement of physical elements (system elements and physical interfaces) which provides the design solution for a product, service, or enterprise, and is intended to satisfy logical architecture elements and system requirements. It is implementable through identified technologies. [7]

Profile: A model package that contains definitions of stereotypes, relations, and related model elements that represent a cohesive set of concepts that extend or customize the system modeling language [8].

System of Interest (SOI): The system, behavior, process, item, or entity being represented as a whole or in part by the SAM.

View: A representation of an aspect of the SOI architecture from the perspective of specific system concerns [9].

Preparation Instructions

1Reference DocumentsThe applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified by the Acquiring Organization.
2FormatTool-Independent and Tool-Proprietary Formats. The SAM in its entirety, (i.e., including all profile changes, extensions, and modifications) shall be in the following formats: (a) the proprietary format of the SysML, UAFML, or SysML v2 -compliant modeling tool used to generate the SAM, (b) Extensible Markup Language (XML) Metadata Interchange (XMI) Specification [10] for SysML v1 and UAFML, and (c) ASCII [11] text files for SysML v2 models.
3Content
3.1General Attributes
3.1.1LanguageThe SAM shall be written in SysML v1, UAFML, or SysML v2 as specified by the Acquiring Organization.
3.1.2Model style guide conformanceThe SAM shall conform to Style Guide or other model syntax standards set forth by the Acquiring Organization.
3.1.3Naming and typing for interoperabilityThe SAM shall conform with all model interface, naming, model element typing, stereotyping, profiles, and library specifications set forth by the Acquiring Organization.
3.1.4Verification of internal mathematical modelsAll mathematical and analytical models contained within the SAM shall be verified.
3.1.5Internal Documentation for maintainabilityThe SAM shall include documentation within the model to describe design concepts, dependencies, naming conventions, model element descriptions, other model attributes, and verification procedures that are necessary to perform and test model updates.
3.1.6User InterfaceThe SAM shall include diagrams that enable the user to find information, locate elements in the containment tree, and navigate between diagrams.
3.1.7Model load timeThe SAM shall load within either 5 minutes or the time limit specified by the Acquiring Organization in the computing environment in which it is intended to reside.
3.1.8Table and diagram generation timeThe SAM shall load any view within the model (e.g. diagram or table) within either 5 minutes or the time limit specified by the Acquiring Organization in the computing environment in which it is intended to reside.
3.1.9Information SecurityThe SAM shall be marked and partitioned in accordance with information and program security requirements applicable to the program for which the model is being developed.
3.1.10Access ControlThe SAM and the environment in which it is executed shall control access to users by classification level, dissemination restrictions, and proprietary restrictions.
3.1.11Logging of ChangesThe SAM shall include a Model Change Log that captures baseline identifiers, what changed, when, why, approval authority, and change request identification. SAM model element or diagram changes shall be labeled with a specific designation (e.g., a change identifier or revision number).
3.1.12Development planThe SAM shall be developed and deployed in accordance with (1) a development plan such as DI-SESS-82380 ("MBSE Model Development Plan") or model management plan that specifies model content by development phase or program milestones, or (2) for Software Pathway programs, by capability drops, program increments, or other agile release events, as agreed upon by both the SAM developer and the Acquiring Organization.
3.1.13Model Intended UseThe SAM shall describe its purpose, i.e., how it is to be used in system development and sustainment
3.2Views and Exports
3.2.1Model Development ArtifactsThe SAM shall describe the model development methodology.
3.2.2Concept of operations documentThe SAM shall provide views and exports of all necessary model elements required to produce an SOI concept of operations document.
3.2.3System Requirements DocumentThe SAM shall provide views and exports of all necessary model elements required to produce an SOI system requirements document.
3.2.4Lower-Level Requirements DocumentsThe SAM shall provide views and exports of all necessary model elements required to produce requirements documents at all SOI architectural levels.
3.2.5Software Requirements DocumentThe SAM shall provide views and exports of all necessary model elements required to produce an SOI Software Requirements Specification.
3.2.6Interface Requirements DocumentThe SAM shall provide views and exports of all necessary model elements required to produce an SOI Interface Requirements Documents or Specifications.
3.2.7System/Subsystem Design DocumentThe SAM shall provide views and exports of all necessary model elements required to produce SOI system/subsystem design documents.
3.2.8Software Design DocumentThe SAM shall provide views and exports of all necessary model elements required to produce SOI software design documents.
3.2.9Verification, Validation, and Test PlansThe SAM shall provide views and exports of all necessary model elements required to produce SOI verification, validation, and test plans.
3.2.10Test ProceduresThe SAM shall generate test procedures.
3.2.11Test ReportsThe SAM shall either (1) provide a reference to current and authoritative SOI test reports or (2) generate SOI test reports based on current and authoritative data in the model.
3.2.12The SAM shall be able to produceall views and exports in formats that can be processed by commonly available application software to produce human readable documents such as Portable Document Format (PDF) [12], Hypertext Markup Language (HTML) [13], or Open Office XML (OOXML) [14], used by desktop productivity application suites such as Microsoft Office or LibreOffice [15]
3.3Modeling of System Requirements
3.3.1Traceability to Concept of OperationsThe SAM shall show the relationship (traces or dependencies) between the system concept of operations and the system requirements.
3.3.2SOI Security requirementsThe SAM shall include Communications Security (COMSEC), Cybersecurity, and Program Protection (PP) security requirements and identify model elements where they are implemented in accordance with DoD policies.
3.3.3SOI Electromagnetic Interference (EMI) and Electromagnetic Compatibility (EMC) RequirementsThe SAM shall include EMI/EMC requirements and allocate them to all affected items incorporated into the design.
3.3.4SOI User interface requirementsThe SAM shall include SOI User interface hardware and software requirements for operators, users, maintainers, and sustainers and allocate them to all affected items incorporated into the design.
3.3.5SOI Contamination Control RequirementsThe SAM shall include Contamination control processes and procedures requirements and allocate them to all affected items incorporated into the design.
3.3.6SOI Hazardous Material requirementsThe SAM shall include hazardous materials management and pollution prevention requirements and allocate them to all affected items incorporated into the design.
3.3.7SOI Reliability, Maintainability, and Availability requirementsThe SAM shall include reliability, maintainability, and availability requirements and allocate them to the appropriate model elements.
3.3.8SOI Data storage requirementsThe SAM shall include requirements for data storage including communications channel, storage, and processing capacity and allocate them to all affected items incorporated into the design.
3.3.9SOI Access control and data integrityThe SAM shall include requirements for access control by role or other user characteristics and allocate them to all affected items incorporated into the design.
3.3.10SOI Survivability, vulnerability, and threatsThe SAM shall include requirements for survivability, vulnerability, and threat for all categories of expected threats and threat environments and allocate them to all affected items incorporated into the design.
3.3.11SOI System SafetyThe SAM shall include requirements for System Safety and allocate them to all affected items incorporated into the design.
3.3.12SOI Environmental Safety and Occupational Health (ESOH)The SAM shall include requirements for ESOH and allocate them to all affected items incorporated into the design.
3.3.13SOI Environmental qualificationThe SAM shall include environmental qualification requirements and allocate them to all affected items incorporated into the design.
3.3.14SOI Requirements TraceabilityThe SAM shall show that the derivation and traceability of requirements from system to segment, subsystem and component levels are complete.
3.3.15SOI Quality and product assuranceThe SAM shall include requirements for quality and product assurance and allocate them to all affected items incorporated into the design.
3.3.16SOI Parts, Materials, and ProcessesThe SAM shall include requirements for parts, materials, and processes (PM&P) and allocate them to all affected items incorporated in the design.
3.3.17SOI SupportabilityThe SAM shall include supportability requirements and allocate them to all affected items incorporated into the design.
3.3.18Inclusion of all levels of SOI requirementsThe SAM shall include all system, subsystem, assembly, and lower requirements within the specification tree.
3.3.19SOI Interoperability requirementsThe SAM shall include all requirements for system interoperability and allocate them to all affected items in the design.
3.3.20SOI Functional and Performance requirementsThe SAM shall include all requirements for functional and performance and allocate them to all affected items in the design.
3.3.21SOI Space, weight, and power requirementsThe SAM shall include all requirements for space, weight, and power and allocate them to all affected items in the design.
3.3.22To Be Determined (TBD) and To Be Specified (TBS) itemsThe SAM shall include attributes for identifying and managing all TBD, TBS, and other incompletely specified requirements
3.4Functional Architecture
3.4.1Level of decompositionThe SAM shall define the Functional Architecture to the level (1) necessary to show satisfaction of system functional requirements, (2) enable the creation of a Physical Architecture and (3) to be allocated to Components of the Logical or Physical Architecture.
3.4.2Required Information for Each of the FunctionsThe SAM shall describe each of the functions, properties, interfaces, and data exchanges within the Functional Architecture.
3.4.3Traceability to requirementsThe SAM shall show the satisfaction of all functional requirements traceable to a function.
3.4.4Descriptive information in the Functional ArchitectureThe SAM shall describe or document all model elements in the Functional Architecture.
3.5Logical and Physical Architectures
3.5.1Logical Architecture
3.5.1.1Logical Architecture DescriptionThe SAM shall capture the Logical Architecture of the SOI.
3.5.1.2Descriptive Information in the Logical ArchitectureThe SAM shall describe or document all model elements in the Logical Architecture.
3.5.1.3Traceability to Functional ArchitectureAll model elements in the SAM Logical Architecture model shall be traced to at least one model element in the Functional Architecture model.
3.5.1.4Traceability to RequirementsAll model elements in the SAM Logical Architecture model shall be traced to at least one requirement.
3.5.1.5Labeling model elements of the Logical ArchitectureModel elements that are part of the Logical Architecture shall be identified as being part of the Logical Architecture.
3.5.2Physical Architecture
3.5.2.1Physical Architecture DescriptionThe SAM shall capture the Physical Architecture of the SOI. This description shall include detailed and specific component, interface, and connection information and behavioral descriptions to the level of detail needed for hardware or software design.
3.5.2.2Descriptive Information in the Physical ArchitectureAll elements in the Physical Architecture representing components, interfaces, connections actions, states, transitions, messages, and signals shall have a description.
3.5.2.3Traceability to RequirementsAll components in the SAM Physical Architecture model shall be traced to at least one requirement.
3.5.2.4Relationship to Functional ArchitectureThe SAM shall show the relationship of all applicable elements in the Functional Architecture to the Physical Architecture.
3.5.2.5Relationship to Logical ArchitectureThe SAM Physical Architecture shall show the relationship of all applicable Logical Architecture model elements to the Physical Architecture.
3.5.2.6Component AttributesFor each block or physical component represented by other model elements, the SAM shall include or reference attributes describing structural attributes necessary for design reviews, contractually required analyses, and any other contractually required purpose.
3.6Modeling of Behaviors
3.6.1General Behavioral Modeling
3.6.1.1Modeling of Internal BehaviorsThe SAM shall capture all behaviors specified in the SOI requirements.
3.6.1.2Modeling of External behaviorsThe SAM shall include behavioral representations of all interactions with the systems, actors, and other entities with which the SOI interacts.
3.6.1.3Descriptions of Behavior DiagramsEach behavioral diagram in the SAM shall document or depict on the diagram, assumptions about system behavior, design decisions, preconditions, and postconditions.
3.6.1.4Modeling of Error ConditionsSAM Behavioral diagrams shall depict error conditions and alternative control flows, object flows, state transitions, or execution sequences for all error conditions and contingency responses.
3.6.2Activity Diagrams
3.6.2.1Activity Partitions ("Swim Lanes")Activity diagrams in the logical and Physical Architecture shall depict the allocation of behavior to structural elements using activity partitions.
3.6.3Sequence Diagrams
3.6.3.1Capture of Interaction Behavior on Sequence DiagramsBehavioral Interactions of the SOI through internal and external interfaces shall be captured in sequence diagrams.
3.6.4State Machine Diagrams
3.6.4.1SOI statesThe SAM shall represent all significant modes and states of the SOI.
3.6.4.2State TransitionsThe SAM shall represent all possible (State) Transitions and events that can trigger transitions between the SOI's states.
3.6.4.3Actions occurring before, during, and after state transitionsThe SAM shall capture (1) behaviors to be performed before, during, and after state transitions and (2) actions to be performed upon entry, during, or upon exit of states.
3.6.4.4Transition inhibits and enablersThe SAM shall capture all conditions that enable or inhibit state transitions.
3.6.5Use Case Diagrams
3.6.5.1ActorsThe SAM shall capture all significant users and external systems with which the SOI interacts using either Actor modeling elements or SysML blocks with an Actor stereotype
3.6.5.2System Objectives, Functions, Services, and OperationsUse case diagrams shall depict all significant system objectives, functions, services, and operations
3.6.5.3Handling of exception conditionsUse cases shall include extensions to describe system behaviors and functions during failures, critical variations, and degradations.
3.6.5.4System objectivesThe SAM shall contain use cases that capture system and mission objectives
3.6.5.5Relations between Use Cases and RequirementsThe SAM shall show relationships between use cases and requirements
3.6.5.6Error ConditionsThe SAM shall capture alternatives and off-normal conditions in use cases.
3.7Modeling of Structure
3.7.1Diagrams depicting context and external interfacesThe SAM shall contain diagrams that describe all external input-outputs exchanged during interactions with systems, organizations, and personnel, and the external interfaces through which they are exchanged (e.g., a SysML internal block diagram in which the system is represented as a block and external interfaces are shown as ports). Such interfaces include but are not limited to those in the capability, operational, technical, and system, UAFML domains.
3.7.2Interface DescriptionsThe SAM shall include a description of all interfaces (e.g., physical, human, internal, external) including purpose, rationale, items flowing through the interface, and behaviors (if any). The descriptions of the interface shall be to the level needed for design reviews, analyses, and all other uses on the project for which the model is being used.
3.7.3Component RelationshipsThe SAM shall represent the relationships (e.g., satisfy, association, containment, dependency, allocate, generalization/specialization) for each block in the Functional, Logical, or Physical Architectures.
3.7.4ConnectionsThe SAM shall define and describe the connections between structural elements.
3.7.5Information and Data FlowsThe SAM shall define and describe the data, information, items, or physical flows within the connections.
3.7.6Constraints and Value PropertiesThe SAM shall include all value properties contained in or derived from requirements.
3.7.7Allocation of software to hardwareThe SAM shall show the allocation (or planned deployment) of software items to the hardware defined on which they will execute.
3.8SOI Performance
3.8.1Key Performance Parameters (KPPs) and Key System Attributes (KSAs)The SAM shall include current and authoritative values for all critical performance parameters or essential characteristics such as SOI KPPs KSAs, and ASAs
3.8.2Derivation of lower level performance parametersThe SAM shall include the derivation of all lower level performance parameters derived from KPPs and KSAs, and ASAs or other critical performance parameters or essential characteristics
3.8.3Allocated performance parameters in model elementsThe SAM shall show allocated performance requirement parameters as value properties or parameters in subsystems and components.
3.8.4Performance modeling data contentThe SAM shall include all SOI parameters and data necessary to analyze and calculate response time and throughput capacity at any architectural level.
3.8.5Performance analysis data import and export to external performance modelsThe SAM shall provide a means for importing and exporting external parameters and data to performance analysis tools and simulations.
3.8.6References to external performance analysis modelsThe SAM shall identify and provide links to external analysis models.
3.9Reliability/Availability
3.9.1Model representation of system designThe SAM shall include a current and authoritative system design model with sufficient detail to enable reliability analyses required by the Acquiring Organization.
3.9.2Representation of Failure Modes, Effects and Criticality Analysis (FMECA)The SAM shall (1) include all authoritative program FMECAs and produce FMECA reports as part of the SAM or (2) provide references to external current and authoritative FMECA analyses and reports. DID SESS-82426 may be used as a reference.
3.9.3Reliability, availability, and maintainability analysis dataThe SAM shall include current and up to date values of all allocation and prediction data necessary for analysis and calculation of SOI reliability and availability attributes required by the Acquiring Organization.
3.9.5Quantitative Reliability AnalysesThe SAM shall either (1) include profiles, plug-ins, and libraries capable of calculating reliability and availability results and produce suitably formatted reports required by the Acquiring Organization or (2) include references to current and authoritative analyses and associated data for all reliability and availability analyses required by the Acquiring Organization.
3.9.6Export of reliability, maintainability, and availability dataThe SAM shall export all data necessary to perform reliability analyses to all external reliability and availability analysis tools needed to perform analyses required by the Acquiring Organization.
3.10System Safety
3.10.1Safety data and reportsThe SAM shall either (1) reference authoritative and current documents required in the System Safety Plan of the SOI contract or (2) input, store, and export data and produce reports that are acceptably formatted for certification authorities for all system safety tasks specified in the SOI contract.
3.10.2Reporting on safety dataThe SAM shall produce reports acceptably formatted for all safety tasks and reports specified and required by the Acquisition Authority.
3.10.3Safety Views and custom reportsThe SAM shall either produce or reference authoritative and current views and custom reports to display the status of SOI activities required for safety certification or approval at any architectural level where certification or approval is required.
3.10.4Satisfaction of Safety RequirementsThe SAM shall show how system requirements for system safety, hazardous material handling, and Environmental Safety and Occupational Health (ESOH) are satisfied.
3.11Cybersecurity
3.11.1Traceability of SSE, COMSEC, cybersecurity, and Program Protection (PP) requirementsThe SAM shall show how SSE, COMSEC, cybersecurity, and PP security requirements are satisfied in the detailed design in accordance with DoD policies, directives, and system specifications.
3.11.2Access control designThe SAM shall show how user access control lists, data control, and data protection, incorporated into the SOI detailed design satisfy system requirements.
3.11.3Import, export and storage of cybersecurity dataThe SAM shall either (1) reference up to date documents for all cybersecurity documents required in the System Security Plan or the SOI contract or (2) input, store, export current and authoritative data and produce acceptably formatted reports for all tasks in all cybersecurity standards or instructions that are required by the Acquiring Organization.
3.12Logistics, Sustainment and Product Support
3.12.1Maintainability and product support dataThe SAM shall either (1) reference authoritative and current data, contractually required instructions, and standards related to maintainability; sustainability; storage; staffing; repair; and packaging, shipping, and handling or (2) provide the capability to input, store and export such data, reports, and standards.
3.12.2Maintenance InstructionsThe SAM shall either (1) reference current and authoritative maintenance instructions or (2) generate maintenance instruction documents from current and authoritative internal model data.
3.12.3Reports and views on maintainability and product support dataThe SAM shall either (1) reference current and authoritative reports for all tasks in all maintainability; sustainability; storage; repair; and packaging, shipping, and handling required by the Acquiring Organization or (2) produce such reports acceptably formatted based on internal model data.
3.12.4Long lead time itemsThe SAM shall either (1) refer to reports identifying long lead time items with associated production requirements or (2) produce such reports based on current and authoritative data stored as attributes of relevant model elements
3.13Specialty Engineering
3.13.1EMC/EMI control processesThe SAM shall either (1) reference current and authoritative documents showing how EMI control processes and procedures including EMI susceptibility are reflected in the detailed design or (2) produce contractually required reports containing such information based on accurate and up to date internal model data
3.13.2Threat environmentsThe SAM shall either (1) reference current and authoritative documents that enumerate the survivability and vulnerability threats, threat environments, and likelihood of occurrence, allocations for categories of expected threats, threat environments and their likelihood of occurrence or (2) produce contractually required reports containing such information based on accurate and up to date internal model data.
3.13.3Thermal, vibration, shock, and Highly Accelerated Life Test (HALT) requirementsThe SAM shall either (1) reference current and authoritative documents that describe how requirements derived from thermal, vibration, and shock environments are satisfied by the detailed design or (2) produce contractually required reports containing such information based on accurate and up to date internal model data.
3.13.4Environmental ParametersThe SAM shall either (1) reference current and authoritative documents that list all environmental parameters impacting parts performance or (2) produce contractually required reports containing such information based on accurate and up to date internal model data.
3.13.5Contamination control processesThe SAM shall either (1) reference current and authoritative documents that describe how Contamination control processes and procedures are incorporated into the detailed design to meet production, mission operations, maintenance, and disposal requirements or (2) produce contractually required reports containing such information based on accurate and up to date internal model data.
3.13.6Critical technologiesThe SAM shall either (1) reference current and authoritative documents that contain critical technologies lists that identify primary and alternate sources for all critical technologies or (2) produce contractually required reports containing such information based on accurate and up to date internal model data.
3.13.7Form, fit and function attributesThe SAM shall include all necessary form, fit, and function as attributes for those model elements representing Line Replaceable Units (LRUs), assemblies, and other replaceable items and produce contractually required reports containing such information based on accurate and up to date internal model data.
3.13.8Production testing and acceptanceThe SAM shall either (1) reference current and authoritative documents that include production testing requirements and production acceptance testing plans or (2) produce contractually required reports containing such information based on accurate and up to date internal model data
3.13.9Human Factors Engineering (HFE)The model shall either (1) reference current and authoritative documents that address requirements or standards on HFE. including, as applicable, considerations for the capabilities and limitations of humans; foreseeable human errors under both normal and extreme conditions; and specific areas where the effects of human error are serious or (2) produce contractually required reports containing such information based on accurate and up to date internal model data
3.13.10Integration with Software Architecture ModelIf DI-SESS-82514 (Software Architecture Model, SWAM) is required by the Acquiring Authority, the SAM shall either (1) show the relationship between model elements in the SAM and the SWAM that are not incorporated into the SAM, or (2) satisfy all requirements of the SWAM.

References

ISO/IEC 19514:2017 Information technology - Object management group systems modeling language (OMG SysML) https://www.iso.org/standard/65231.html

OMG System Modeling Language Specification Version 2.0 https://www.omg.org/spec/SysML/2.0/Language/PDF

Unified Architecture Framework Specification Version 1.2 https://www.omg.org/spec/UAF/1.2/UAFML/PDF

Functional Architecture https://acqnotes.com/acqnote/careerfields/functional-architecture

Systems Engineering Book of Knowledge - Logical Architecture https://sebokwiki.org/wiki/Logical_Architecture

Physical Architecture https://acqnotes.com/acqnote/careerfields/physical-architecture

ISO/IEC/IEEE 42010, Systems and software engineering - Architecture Description https://webstore.ansi.org/standards/ieee/IEEEISOIEC420102007

XML Metadata Interchange (XMI) Specification, Version 2.5 https://www.omg.org/spec/XMI/2.5/Beta1/PDF

ISO 32000-2:2020, Document management - Portable document format https://www.iso.org/standard/75839.html

HTML Living standard https://whatwg.org

ISO/IEC 29500, Information technology -- Document description and processing languages - Office Open XML File Formats https://www.iso.org/standard/71691.html

LibreOffice https://www.libreoffice.org/

Schema v3.0Community-maintained · Verify against ASSIST
Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer