What did the mission analysis tool actually do?

It loaded recorded mission data, applied the operator's configuration, ran analysis on the mission and replayed it, through four modules in a Windows desktop application.

Why is a drone tool listed under industrial systems?

Because the pattern is the same: capture a data record, apply configuration and rules, analyse and replay. That is the core of supervisory, historian and telemetry systems.

Are there performance results?

No. The tool was delivered and accepted, but usage and performance were not instrumented, so this case study reports scope, stack and timeline only.

Industrial, IoT & Operational SystemsUAV operations client · 6 weeks (June – July 2019)

Mission Data Analysis & Replay Desktop Tool for UAV Operations UAV operations client

An organisation operating unmanned aerial missions that needed a post-flight tool to load, analyse and replay recorded mission data on standard Windows workstations. The client is not named.

Duration: 6 weeks (June – July 2019)

Platform: Windows desktop application (WPF, C#)

Channels: Mission data analysis and replay system

Build Something Similar What we built

Scope, visualised

What was built and delivered

Modules delivered4

Investigation to release6 wks

Delivery phases with UAT4

Capture

Monitor

Alert

Act

Report

Overview

The client supplied a functional specification for a post-simulation tool. Technovier scoped it into four modules and delivered a WPF desktop application in C#: Open/Load Mission, Configuration, Analyze Mission and Replay Mission, plus an About screen. The engagement ran through system investigation, design and development, integration testing and user acceptance before release.

Windows Presentation Foundation (WPF), C#, .NET

Problem, Constraints, Baseline, Approach, Results

Problem

Recorded mission data had no purpose-built tool for review: operators could not load a mission, apply their configuration and replay it in one place.

Constraints

Every function had to match the client's specification document; the tool had to run offline on standard Windows workstations.

Baseline

No existing application; mission review depended on raw files and manual inspection.

Approach

Four modules built as a WPF/C# desktop application with a front end and back end, delivered through a four-phase plan: investigation and analysis, design and development, testing, and user acceptance.

Results

Delivered and released in July 2019 after integration testing and user acceptance. Usage or performance metrics were not instrumented, so none are claimed here.

Delivery phases with UAT

Modules delivered

6 wks

Investigation to release

Delivery phases with UAT

Modules delivered

6 wks

Investigation to release

Delivery phases with UAT

Key metrics shown: 4 Modules delivered; 6 wks Investigation to release; 4 Delivery phases with UAT.

Why it matters for operational systems

Load, configure, analyse, replay is the same data-to-decision pattern behind a SCADA historian or a telemetry dashboard: capture the record, apply rules, inspect it, replay it. This project applied it to mission data.

• Replay as a first-class function: Replaying a recorded mission with the operator's configuration is the same capability as trend-and-replay in supervisory systems.

• Configuration separated from data: The Configuration module kept operator settings apart from the mission record, so the same data could be analysed under different setups.

Conclusion

A specification-driven desktop tool for mission data, delivered in six weeks with acceptance testing. It is the earliest of Technovier's operational-data builds and the pattern it used still shapes our industrial and SCADA work.

Related systems