Home' RTCA Documents for Review : C2 Link Systems MASPS_Draft Contents 13
© 2018 RTCA, Inc.
Approach and Methodology
This document was developed using a process that is top-down in nature with an initial
focus on the operational perspective. Subsequently, the work involved systems expertise,
as requirements for a C2 Link System were developed to meet the operational and
functional needs specified in the OSED. The work was iterative in nature as each phase of
the process fed back into the previous work, which permitted the work to mature and be
refined to ensure completeness and consistency.
Document Development Process
With the CONOPS developed (see APPENDIX A), a set of UAS scenarios was described
that represent important user missions and that would place high demands on the
performance of the C2 Link System. The development of those scenarios is described in
Appendices B and C.
Using those scenarios, specific use cases (portions of the scenarios) were analyzed in
greater detail to assess the information exchanges carried over the C2 Link System that
were required during those demanding situations. The various services and environmental
conditions associated with those information exchanges were identified. The OSED
includes a description of the process that led to deriving the operational and functional
requirements for a C2 Link System. These developments are described within APPENDIX
During the development of the safety and performance requirements (see Appendices D
and E), comments were fed back into the development of the OSED as to where additions
or modifications were needed for clarification.
As the process moved from a more operational perspective to a system-oriented one, key
operational and analytical experts were involved throughout, to ensure overall consistency
and coherence of the work and results.
The MASPS uses the concept of Required Link Performance (RLP) to describe a collection
of C2 Link System performance requirements that form part of the set of C2 Link System
requirements included in Section 3.6. It is similar in concept to other performance-based
metrics such as Required Communication Performance (RCP), Required Navigational
Performance (RNP) and Required Surveillance Performance (RSP).
The RLP is the operational framework to express the C2 Link System performance
necessary for a UAS operational capability within a defined airspace. An RLP is
determined according to safety analysis and operational needs and is specified for the UAS
operational capability for a given region. The RLP is independent of the technology used
for the C2 Link System and is applicable to the logical connection, however, realized for
the exchange of information between the CS and the UA.
The RLP describes the Availability, Continuity and Integrity that the C2 Link System is
required to achieve in a given Transaction Expiration Time (TET) so as to support all
remote pilot activities associated with managing the flight of the UA.
The Required Link Technical Performance (RLTP) is identical in concept to RLP but
excludes any human-related performance or activity times.
Concept of Operations (CONOPS) and Scenarios
The development of the CONOPS and scenarios followed a standard System Engineering
(SE) process to include working closely with the “main user” of the results, i.e., the OSED.
Links Archive DO-XYZ_ED-ABC_FRAC_SC236_MASPS Navigation Previous Page Next Page