Distributed Command and Control Infrastructure for the operation of all types of unmanned vehicles. Neptus supports the different phases of a typical mission life cycle: planning, simulation, execution and post-mission analysis.
Neptus can be adapted by operators to fit mission-specific requirements and extended by developers through a comprehensive plug-in framework.


  • Planning

    Neptus supports planning for different vehicle types. This is done by having a profile of each vehicle's sensors and maneuvering specifications. Different types of geographical data can be used in the planning phase, including S57 charts, tiled raster images from various sources and user-defined features. Plans can be simulated and validated before execution according to vehicle capabilities (battery endurance, maneuver support, sensors, etc).

  • Execution

    During the execution phase, Neptus can be used to visualize incoming real-time data from multiple vehicles, to teleoperate individual vehicles and to give maneuver commands to multiple vehicles. In order to support limited communications, the expected behavior of vehicles disconnected is simulated so that the user gets a comprehensive, quick glimpse of the state of the entire network

  • Review and Analysis

    The review and analysis phase takes place on site or after the mission (or plan) is concluded. In this phase, the collected data is processed and analyzed to compile the mission results or evaluate individual plan execution in order to adjust and re-plan to achieve another desired outcome.

  • Description

    Neptus is the C2 (Command and Control) software used to command and monitor our unmanned systems. It is written in Java and it currently runs in Linux and Microsoft Windows operating systems.

    The main Neptus communication interface is IMC, making it interoperable with any other IMC-based peer. Neptus has been used to command all our systems which correspond to very heterogeneous classes of autonomous vehicles and sensors. Despite the heterogeneity of the controlled systems, Neptus provides a coherent visual interface to command all these assets. The main purpose is for an operator to take advantage of what these assets have to offer in terms of sensor and actuator capabilities without having to dwell into specific C2 software and details.

    Neptus is a framework that was created from scratch having in mind its adaptability and flexibility to encom-pass needs from diverse vehicles, scenarios and operator experiences. As a result, it provides the rapid creation of derived tools and can be customized according to operator and mission needs.

    A plug-in can be developed independently of the main Neptus source and added as a compiled jar file. This way Neptus can be extended by a third party with new compo-nents with the added possibility of not sharing source code among developers (which can sometimes be a requirement for ITAR-constrained code, for instance).