ASTM F3548-21 PDF

SIGNIFICANCE AND USE 7.1 This specification is intended to be used by USS developers, CAAs, and others to assess USS conformance with this UTM specification. SCOPE 1.1 This specification is intended to be a global specification providing components that may be used to satisfy requirements expected to be common to many UTM-related regulations. This specification is not intended to comprehensively address all aspects of any particular UTM-related regulation or concept of operations. Similarly, because varying terminology for the same concept is frequently used across different regulations, readers should not expect an exact terminology consistency with any particular UTM-related regulation. 1.2 This version of the specification is focused on strategic aspects of UAS operations, including strategic conflict detection, aggregate conformance of operations to their operational intents, constraint awareness, and situational awareness in the event of nonconforming or contingent operations. The intention is that this specification will evolve to address increasingly complex strategic aspects of UAS operations and potentially certain tactical aspects of UAS operations. 1.3 This specification addresses the performance and interoperability requirements, including associated application programming interfaces (APIs), for a set of UTM roles performed by UAS Service Suppliers (USSs) in support of UAS operations.2 Roles are groupings of one or more related UTM services. A competent authority may choose to use the roles defined in this specification in establishing the granularity of authorizations granted to a USS. The roles defined in this specification are: (1) Strategic Coordination, comprising the Strategic Conflict Detection and Aggregate Operational Intent Conformance Monitoring services; (2) Conformance Monitoring for Situational Awareness (CMSA); (3) Constraint Management, comprising the Constraint Management service; and (4) Constraint Processing, comprising the Constraint Processing service. 1.4 Section 4, Conceptual Overview, provides a description of each of the services and roles and includes further discussion on their scope. 1.5 A regulator may choose to require that a USS support a minimum or prescribed set of roles and services and may adopt terminology other than USS for a software system that provides something other than that minimum or prescribed set of roles and services. However, for purposes of this specification, a USS is a system that provides one or more of the UTM services defined in this specification. 1.6 A USS is not required by this specification to perform all roles or implement all defined services, providing business case flexibility for implementers. A typical USS that supports operators in the planning and execution of UAS operations may implement the Strategic Coordination, Constraint Processing, and CMSA roles. (Note that a USS providing CMSA for a UAS operation is required to also provide Strategic Coordination for the operation.) However, other implementations more limited in scope are possible. For example, a USS may implement only the Constraint Management role and be intended for use only by authorized constraint providers; or, a USS may implement only the Constraint Processing role to provide general airspace awareness to users independent of planning UAS flights. USSs may also provide additional, value-added capabilities and still be compliant with this specification as long as the value-added capabilities do not conflict with the services defined in this specification, and the implementation of services defined in this specification conforms to the applicable requirements. 1.7 A USS may also support other UTM roles such as Remote ID and airspace access (for example, the FAA’s LAANC), specified in other documents. 1.8 This specification addresses aspects common to all roles and services, such as Discovery and Synchronization Services (DSS), security, aud...