Detailed Pricing

General

The pricing for FlightOps is determined by various factors that contribute to the overall capabilities of the system. These factors help tailor the price according to the specific requirements and level of usage. The basic pricing method encompasses the following elements:

  1. Number of sites and plan type: The price is influenced by the number of sites you want to manage using FlightOps and the specific plan type chosen for each site. Different plans may offer varying features and levels of support, which can affect the pricing.

  2. Number of drones in the account: The pricing also takes into account the number of drones you intend to connect and manage through FlightOps. The more drones you have in your account, the higher the pricing might be to accommodate the increased usage.

  3. Hosting options: FlightOps provides flexibility in hosting options, allowing you to choose between self-hosting or utilizing their cloud-based hosting services. The chosen hosting option can impact the pricing structure.

  4. Additional extensions and integrations: FlightOps offers additional extensions and integrations to enhance its functionality and integrate with other systems or software. The pricing may vary depending on the specific extensions and integrations you require.

  5. Service level: FlightOps may offer different service levels, such as basic support, premium support, or dedicated account management. The level of service you opt for can influence the pricing, as higher service levels often come with increased support and priority access.

In addition to these elements, FlightOps also offers discounts based on the duration of the contract. The longer the contract duration you commit to, the higher the discount you may be eligible for. This encourages longer-term commitments and provides cost savings for customers who choose to use FlightOps over an extended period.

Sites and plans

Each account has the ability to define multiple sites, with each site having specific parameters such as maximum surface area (perimeter) and maximum number of drones that can be operated within it. Accounts can choose from various site types and plans to suit their needs. Below is a description of the available site plans:

FlightOps Basic:

FlightOps Basic offers a cost-effective option for small-scale operations. It allows the operation of a single drone within a surface area of 5x5 km. This plan includes features such as dynamic viewpoint missions and manual piloting using a dedicated operator app.

FlightOps Advanced:

FlightOps Advanced is a fully functional option that provides broader capabilities. It covers a surface area of 20x20 km and allows the operation of up to 15 drones per site. Users with this plan have access to all FlightOps apps, including C2 (Command and Control), Joystick, Dispatch, Pilot, and Video Matrix. This plan is suitable for more extensive operations.

FlightOps XL:

FlightOps XL is designed for large-scale operations. It covers a surface area of 100x100 km and allows the operation of up to 75 drones per site. Users with this plan have access to all FlightOps apps and mission types, offering maximum flexibility and scalability.

Plan
Functionality
Integrations
No of drones
Area

Basic

Dynamic VP / Manual

All

One drone

5X5 km

Advances

All missions / apps

All

Up to 15

25X25 km

XL

All missions / apps

All

Up to 75

100X100 km

Plans selection and payment

Account holders can select any combination of plans that best suits their operational requirements, whether a small-scale operation with a single drone or a large-scale operation involving multiple drones over extensive areas.

Number of Drones

The total number of drones operated in Account One is a factor that impacts the overall cost. While there is no limitation on the number of drones that can be linked to the account, it is important to note that individual sites within the account have specific limits on the number of drones they can accommodate based on their respective types. Therefore, the number of drones linked to a single site is subject to the limitations imposed by its site type. drones can be transferred between sites.

Extensions

Extensions are optional capabilities that can be added to the FlightOps solution, providing additional functionalities. These extensions can include features like drone docking stations or integrations with external systems. The cost of extensions is determined by the number of integrations associated with the account. Each integration is identified by an access token provided to the account.

Drone Dock:

Drone docks are a specific type of extension that is priced separately from other extension types. These docking stations enable automated landing, charging, and maintenance for drones, providing enhanced operational efficiency and convenience. The cost for drone docks is calculated based on the number of docks required.

External Systems:

External systems refer to integrations with third-party systems, such as UTM (Unmanned Traffic Management) systems, e-commerce platforms, or data sources. These integrations allow seamless data exchange, communication, and coordination between FlightOps and these external systems. The pricing for integrating with external systems is determined based on the number of the API access tokens issued for the account.

Hosting Options

The FlightOps system provides two options for hosting: self-hosting on the customer's cloud infrastructure or utilizing the FlightOps cloud service. Opting for FlightOps hosting incurs additional costs for both sites and drones.

It's important to note that once a hosting type is selected for the account, it cannot be divided between the two options. In other words, all sites and drones within the account must follow the same hosting configuration.

If there is a need to change the hosting type during ongoing operations, a Non-Recurring Engineering (NRE) cost will be involved. This cost covers the transfer of data and configurations from one hosting environment to another, ensuring a smooth transition while minimizing disruption.

Service Plans

FlightOps offers three support plans: "None," "Basic," and "Premium." Each plan provides varying levels of support based on response time and the classification of service request types allowed.

"None" Plan:

The "None" plan includes limited support services. All service requests submitted under this plan will be handled as "normal" service requests, with an additional up to 5 workdays added to the Service Level Agreement (SLA) response time. The specific classification of service request types covered under the "None" plan will be defined in the support documentation provided by FlightOps.

"Basic" Plan:

The "Basic" plan offers support services with a defined response time for service requests. The response time may vary depending on the severity or priority of the request. The classification of service request types allowed under this plan will be clearly outlined in the support documentation provided by FlightOps.

"Premium" Plan:

The "Premium" plan provides comprehensive support services with a shorter response time for service requests. This plan includes priority handling for a broader range of service request types, ensuring prompt assistance and resolution. The specific classification of service request types covered under the "Premium" plan will be clearly defined in the support documentation provided by FlightOps.

SLA description

Classification
Programs
SR definition
Target Response Time
Target Restoration Time

Critical

Premium Only

An SR will be Classified as a critical incident if the performance issue reported causes the Cloud Services to be functionally inoperable (entire system is down) and prevents them from being used in Production Mode.

3 hour or less, 7x24 Critical incidents must be logged by phone or text messaging to FlightOps directly

8 hours, 7x24

Serious

Premium, Basic

An SR will be Classified as a serious incident if the performance issue reported significantly degrades the performance of the Cloud Services or materially restricts your use of the Cloud Services in a Production Mode (system is operational, but performance may be impacted).

The Serious Classification does not include questions on end use and configuration of the Cloud Service.

5 hours, 5x8, Email

12 business hours, 5x8 (For "Basic" Add 1 workdays)

Normal

None, Premium, Basic

An SR will be Classified as a normal request if the performance issue reported is a question regarding: (i) end use; (ii) configuration of the Cloud Services; or (iii) a minor defect in the Cloud Service that does not materially restrict your use of the Cloud Service in a Production Mode.

As a rule, SRs reported via email and/or are for non-production systems are Classified as Normal.

8 business hours, 5x8, Email

72 business hours, 5x8 (For "none" add 5 work days, For "Basic" Add 2 workdays)

Contract Duration

The duration of the contract for the account directly impacts the discount percentage applicable to the entire account.

The discount percentage offered for the entire account is determined based on the length of the contract. Longer contract durations may qualify for higher discount percentages, while shorter contract durations may have comparatively lower discount percentages applied.

Payments

Annual payments

The Site License Costs are paid annually in advance and are non-refundable. The first annual payment shall be relative to the number of months remaining in the calendar year, calculated from the purchase date.

Monthly Payments

The Drone License Costs and the extensions License Costs shall be paid in advance for the complete month at the first day of the month. The first monthly payment shall be relative to the number of days remaining in the calendar month, calculated from the purchase date.

NRE payments

If Non-Recurring Engineering (NRE) payments are required for the account due to changes in hosting configurations or other modifications, the specific payment terms will be outlined in the commercial agreement. The NRE payments will be based on the agreed-upon terms and conditions negotiated between the parties involved.

Last updated