Your Selections

TEAAS4UCS
Show Only

Collections

File Formats

Content Types

Dates

Sectors

Topics

Publishers

Committees

Committee Codes

Data Dictionary for Quantities Used in Cyber Physical Systems

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AS6969
  • Current
Published 2018-06-13 by SAE International in United States
This data dictionary provides definitions for quantities, measurement units, reference systems, measurands, measurements and quantity modalities commonly used on the command and control of cyber physical systems. A cyber physical system as an engineered system that is built from, and depends upon, the seamless integration of computational algorithms and physical components. Cyber physical systems are often interconnected via data links and networks. The term encompasses intelligent vehicles and devices that operate in any environment, including robotic and autonomous systems.
Datasets icon
Annotation icon

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

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AS6969_DA
  • Current
Published 2018-06-13 by SAE International in United States

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.

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

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AIR6515
  • Current
Published 2016-12-20 by SAE International in United States
This User Guide describes the content of the Enterprise Architect (EA) version of the UCS Architectural Model and how to use this model within the EA modeling tool environment. The purpose of the EA version of the UCS Architectural Interface Control Document (ICD) model is to provide a working model for Enterprise Architect tool users and to serve as the source model for the Rational Software Architect (RSA) and Rhapsody models (AIR6516 and AIR6517). The AIR6515 EA Model has 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
Annotation icon

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Version Description Document

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AIR6520
  • Current
Published 2016-12-20 by SAE International in United States
Governance of the Unmanned Aircraft System (UAS) Control Segment (UCS) Architecture was transferred from the United States Office of the Secretary of Defense (OSD) to SAE International in April 2015. Consequently, a subset of the UCS Architecture Library Release 3.4(PR) has been published under SAE as the Unmanned Systems (UxS) Control Segment (UCS) Architecture, AS6512. This Version Description Document (VDD) describes the correspondence and differences between the two architecture libraries.
Datasets icon
Annotation icon

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

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AIR6517
  • Current
Published 2016-12-20 by SAE International in United States
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
Annotation icon

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

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AS6512
  • Current
Published 2016-12-20 by SAE International in United States
This document is the Architecture Description (AD) for the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture. This AD serves as the official designation of the UCS Architecture - SAE AS6512. The UCS Architecture is expressed by a library of SAE publications as referenced herein. The other publications in the UCS Architecture Library are: AS6513, AIR6514, AIR6515, AIR6516, AIR6517, AS6518, AIR6519, AIR6520, AIR6521, and AS6522.
Datasets icon
Annotation icon

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

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AS6518
  • Current
Published 2016-12-20 by SAE International in United States
This brief User Guide recaps the content of the AS6518 UCS Architectural Model described in detail in AS6512 UCS Architecture: Architecture Description. The purpose of the UCS Architecture Model is to provide the authoritative source for other models and products within the UCS Architecture as shown in the AS6512 UCS Architecture: Architecture Description.
Datasets icon
Annotation icon

UxS Control Segment (UCS) Architecture: Interface Control Document (ICD)

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AIR6514
  • Current
Published 2016-12-20 by SAE International in United States
This interface control document (ICD) specifies all software services in the Unmanned Systems (UxS) Control Segment Architecture, including interfaces, messages, and data model.
Datasets icon
Annotation icon

UxS Control Segment (UCS) Architecture: UCTRACE

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AIR6519
  • Current
Published 2016-12-20 by SAE International in United States
The Use Case Trace (UCTRACE) is SAE publication AIR6519 of the Department of Defense Unmanned Control Segment (UCS) Architecture. This document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: Use Case Trace (UCTRACE) Version 3.4(PR) approved for Distribution A public release 15.S-1859. This information is produced from a script run against the System Use Case Model contained in the UCS Architecture Model AS6518-MODEL.eap configuration item. The System Use Case Model includes, at its lowest level of elaboration, use cases Level 2/3 (L2/L3) that describe specific scenarios of message exchanges between Actors and internal system Participants via ServiceInterfaces. These message exchanges provide a way to create detailed traces that answer the question: “What UCS service interfaces must my components implement to satisfy functional requirements represented by a given Level 2/3 UCS use case?” The AIR6519-UCTRACE spreadsheet contains trace information derived directly from the message sequences in the L2/L3 use cases.
Datasets icon
Annotation icon

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

AS-4UCS Unmanned Systems Control Segment Architecture
  • Aerospace Standard
  • AIR6516
  • Current
Published 2016-12-20 by SAE International in United States
This User Guide describes the content of the Rational Software Architect (RSA) version of the UCS Architectural Model and how to use this model within the RSA modeling tool environment. The purpose of the RSA version of the UCS Architectural Interface ICD model is to provide a model for Rational Software Architect (RSA) users, derived from the Enterprise Architect (EA) ICD model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6516 RSA 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
Annotation icon