Advanced Search
Search Results
10 total results found
Escopo
Objetivo Executar ensaio operacional no IEAv (15 a 17 de dezembro de 2025), com foco em validação de procedimentos de contingência, integração de restrições dinâmicas e avaliação da reação dos provedores diante de eventos simulados. Tópicos Principais Teste...
Chapter 1 — Introduction to BR-UTM
1.1 What Is BR-UTM? BR-UTM is the Brazilian UAS Traffic Management system, operated and overseen by DECEA (Departamento de Controle do Espaço Aéreo), the Brazilian Department of Airspace Control, under the Brazilian Air Force. Its purpose is to safely coordina...
Chapter 2 — Prerequisites and Core Concepts
Before diving into integration, it is essential to understand the foundational concepts and data structures that underpin the entire BR-UTM system. This chapter defines all key terms used throughout the integration guide. 2.1 DSS — Discovery and Synchronizati...
Chapter 3 — Onboarding Process
This chapter describes the end-to-end process for a new company to become an authorized USS in the BR-UTM ecosystem, from account creation to operating in production. 3.1 Overview The onboarding process has two phases: Development Phase — Create an account,...
Chapter 4 — Architecture and Authentication
This chapter describes the authentication and authorization model used across the entire BR-UTM ecosystem, including how your USS obtains tokens, uses them to call DECEA's APIs, validates tokens received from other USSs, and authenticates peer-to-peer calls. ...
Chapter 5 — The Full Flight Lifecycle
This chapter walks through the complete technical lifecycle of a drone flight in BR-UTM — from pre-flight planning to post-flight cleanup. Every API call, data structure, and decision point is described in sequence. 5.1 Lifecycle Overview A BR-UTM flight goes...
Chapter 6 — APIs Your USS Must Implement
This chapter describes all the HTTP endpoints that your USS must expose publicly. These are the endpoints that DECEA and other USSs will call against your server. They are divided into: Production endpoints — required for all live operations. Testing/Homolo...
Chapter 7 — Non-Functional Requirements
This chapter defines the non-functional requirements (NFRs) that your USS must satisfy to be approved for the BR-UTM ecosystem. These are enforced during homologation and are continuously expected in production. Failure to meet these requirements can result in...
Chapter 8 — Homologation
This chapter describes the homologation (validation) process that a company must complete before receiving a production API Key and being authorized to operate in the BR-UTM ecosystem. 8.1 What Is Homologation? Homologation is DECEA's process for validating t...
OpenAPI Specifications
utm.yaml remoteid.yaml flights.yaml injection.yaml versioning.yaml