A Concept of Operations (CONOPS) describes the operational strategy required to meet a set of performance objectives. The CONOPS communicates the overall vision for the operational system to all stakeholders and provides the steering for future systems and procedures development.

AVISU has a proven capability to marry the need for a transparent and stable development process with the open creative environment needed for true innovation to occur.

CONOPS - A total vision

AVISU has a proven capability to marry the need for a transparent and stable development process with the open creative environment needed for true innovation to occur.

To ensure an end to end concept, a total environment view must be taken. A concept developed for part of the business will be a flawed approach as the silo focus will inevitably miss internal or external stakeholders and interface issues will not only reduce efficiency of the solution but increase success of the outcome.

AVISU has trusted and lengthy experience in all the ATM domains necessary for a holistic view towards a common vision.

CONOPS - An integrated process

Concept development is a set of activities that are carried out early in the system lifecycle to collect and prioritise operational needs and develop alternative concepts to meet the needs and select one as the basis for subsequent system or capability development and implementation.

This process covers:

Holistic View of the Environment

The CONOPS should include the full range of factors that are needed to support the operations (i.e., foreseen operational paradigms, organizational structure, training, leadership, personnel, facilities, and resources). A CONOPS should contain a high level user’s view of the system that highlights the top-level functional threads in the system. Crucially a CONOPS should define critical, top-level, stakeholder requirements or objectives and operational and user’s needs stated either qualitatively or quantitatively where possible.

Operational Requirements

Description of the Operating environment, present and future throughout forecast lifecycle – internal and external factors. User-Oriented description of the new/modified system, as proposed, in response to current and future needs. Details operational scenarios for various already identified modes of operation, present and future. Needs are categorized as essential needs (not prioritized), and desirable needs and optional needs (each prioritized)

High Level Conceptual definition

An Initial Solution design is commenced based on the developing CONOPS. This work package ensures that the concept is in line with targeted performance objectives and meet initial safety and technical feasibility analysis. This work package is expanded in phase 3 to a more detailed breakdown of each of these critical delivery areas.

Operational Benefits Validation

Provide Real or Fast Time Simulations to highlight the operational benefits.

Concept Design, Safety and Performance

Oversees the integration of the Solution design safety analysis with the customer Safety experts and SMS. Performance characteristics - Ensures the solution design will meet the target performance objectives of the project in terms of efficiency, environment, business continuity etc

System Development

Solution design - This is a key activity that transforms the CONOPS and initial solution design into a validated detailed functional design that can be met by the final system and procedures.

A validated CONOPS

This process ensures that a structured approach to orchestrate the complete development of a system from a need, through operations to retirement. The application of defining systems conceptually, transform user needs into system requirements and develop and assess architectures is necessary to provide an assurance of the international standards and technology used in defining the system building blocks.

ISO/IEC/IEEE 15288 is an international system engineering standard covering processes and lifecycle stages.

The left side of the V represents concept development and the decomposition of requirements into function and physical entities that can be architected, designed and developed. The right-hand side of the V represents integration and their ultimate transition into the field where they are operated and maintained. Note that design and development continues through the lifecycle of the system.

Concept Validation

There are various methodologies established to validate operational concepts and their technical enablers (such as MAEVA and E-OCVM). Taking an immature concept into an iterative validation process with ever increasing complexity and ever increasing integration of technical, human, procedures and environmental aspects is a difficult, time consuming and difficult task.

Understanding and being aware of existing validation programs, projects and tasks around the globe is vital to ensure requirements that feed certification material are acceptable to the industry, minimise costs and maximise the applicability of the concepts to as many implementers as possible.

AVISU has managed and been involved in the validation of both local as well as internationally focussed concepts. AVISU is able to provide a sound understanding of acceptable validation techniques to combine both a project management as well as subject matter expert role into validation processes. This brings a strong element of realism into the development and application of such techniques and fast-time and real-time simulations, collision risk and other aircraft interaction or network based modelling.

Bridgepark, Beauly
Inverness-Shire, IV4 7AN
United Kingdom

Telephone: +44 146 387 2892

E-mail: contact@avisu.co.uk

At AVISU we are constantly looking for both employees and associated partners to support the ever increasing demands on our expertise. We require people that are self motivated and operationally experienced and the willingness to travel worldwide and occasionally work for extended periods overseas.