Refine Your Search

Search Results

Viewing 1 to 8 of 8
Standard

Data Dictionary for Quantities Used in Cyber Physical Systems (Enhanced License)

2021-12-15
CURRENT
AS6969B_DA
Enhanced License for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969B) allowing for greater usage as outlined in the terms of the Enhanced License. Terms can be reviewed prior to purchase once item is added to the cart. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969B) This data dictionary provides definitions for quantities commonly used in the command and control of cyber physical systems. It defines mathematical and logical terms, quantities, measurement units, reference systems, measurands, and measurements. It also defines common quantity modalities. The dictionary is structured to be convenient to data modelers. It is also extendable so that users can create their own quantity domains.
Standard

Data Dictionary for Quantities Used in Cyber Physical Systems (Enhanced License)

2018-06-13
HISTORICAL
AS6969_DA
Enhanced License for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) allowing for greater usage as outlined in the terms of the Enhanced License. Terms can be reviewed prior to purchase once item is added to the cart. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) This data dictionary provides a mathematically coherent set of definitions for quantity types used in data models for unmanned systems. In this data dictionary, a quantity is defined as a property of a phenomenon, substance, or body whose value has magnitude.
Standard

Data Dictionary for Quantities Used in Cyber Physical Systems (Enhanced License)

2020-10-10
HISTORICAL
AS6969A_DA
Enhanced License and UML Model for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) allowing for greater usage as outlined in the terms of the Enhanced License. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969A) This data dictionary provides definitions for quantities commonly used in the command and control of cyber physical systems. It defines mathematical and logical terms, quantities, measurement units, reference systems, measurands, and measurements. It also defines common quantity modalities. The dictionary is structured to be convenient to data modelers. It is also extendable so that users can create their own quantity domains.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Data Distribution Service (DDS)

2016-12-20
CURRENT
AIR6521
This platform specific Interface Control Document (ICD) provides an example mapping to the Object Management Group’s (OMG) Data Distribution Service (DDS) infrastructure middleware. The mapping is based on the Unmanned Systems (UxS) Control Segment (UCS) Architecture: Model, AS6518. A series of non-normative implementation choices have been made that are specific to this ICD. These implementation choices may not be appropriate for different system implementations. The machine readable ICD and result of this mapping and implementation choices are provided with AIR6521. Use and understanding of this document assumes a working knowledge of the UCS Architecture, the model structure and its contents.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Rhapsody Version of UCS ICD Model

2016-12-20
HISTORICAL
AIR6517
This User Guide describes the content of the Rhapsody version of the UCS Architectural Model and how to use this model within the Rhapsody modeling tool environment. The purpose of the Rhapsody version of the UCS Architectural Interface Control Document (ICD) model is to provide a model for Rhapsody users, derived from the Enterprise Architect (EA) model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6517 Rhapsody Model, have been validated to contain the same content as the AS6518 model for: all UCS ICD interfaces all UCS ICD messages all UCS ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service and Non-Functional Properties Models
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Conformance Specification

2022-03-16
CURRENT
AS6513B
This revision of AS6513 concerns conformance to the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Revision B, designated AS6512B (or later). The superseded AS6513A concerned conformance to the previous UCS Architecture, designated AS6512A. This document is the authoritative specification within the UCS Architecture for establishing conformance requirements for UCS products. The conformance of UCS products is determined by assessing the conformance of the UCS Product Description to the UCS Architecture. The UCS Product Description includes test artifacts.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Conformance Specification

2020-07-08
HISTORICAL
AS6513A
This revision of AS6513 concerns conformance to the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Revision A Library, designated AS6512A (or later). The superceded AS6513 concerned conformance to the original UCS Architecture Library, designated AS6512. This document is the authoritative specification within the UCS Architecture for establishing conformance requirements for UCS products. The UCS products addressed by this specification are UCS software components and UCS software configurations that provide one or more UCS services, and UCS systems that employ one or more UCS services. The conformance of UCS products is determined by assessing the conformance of the UCS product description to the UCS Architecture. The UCS product description includes test artifacts.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: UCS Architecture Model

2021-03-02
HISTORICAL
AS6518A
The scope and purpose of the UCS Architecture Library Revision A is provided in AS6512™A. The scope of this document is to identify the elements of the UCS Architecture Model Revision A as distributed in the AS6518A.zip file, establish the terms and conditions and user license agreement for the architecture model, and provide other metadata.
X