The problem
A practical problem to solve
Flight-test engineering relies on more than a processing platform: operators also need controlled file movement, lifecycle operations, system visibility and focused interfaces for recurring data tasks.
Engineering software · operational tooling
Engineering Applications & Automation
Professional projects · supporting applications
A small group of connected applications that supports flight-data transfer, file lifecycle tasks, storage monitoring and engineering workflows.
Design constraints
- Keep cloud access provision separate from application ownership.
- Make transfer and file-operation state visible to operators.
- Distinguish confirmed software ownership from interface-only contributions.
- Avoid implying that every tool has the same deployment status or maturity.
Solution
Designed around a useful decision
I independently designed and developed the Cloud Uploader application, including its queue, transfer logic, dashboard and operational controls, after the storage direction was agreed with colleagues. I also independently designed, developed and deployed the File Manager for integrity, housekeeping, compression and lifecycle operations. QNAP monitoring brings health and SMART status from four NAS systems into DataManager dashboard notifications. Across the FTDA workspace, I separately confirm sole development of graphical interfaces; that does not imply ownership of every backend or calculation.
Visual space
Conceptual grouping of operator applications. No internal network, storage topology or confidential system details are shown.
Workflow
Queue transfer
The uploader presents queued file work and operational transfer state.
Manage lifecycle
File Manager performs configured integrity, housekeeping, compression and lifecycle operations.
Monitor storage
QNAP health and SMART details are surfaced in DataManager for operator review.
Support engineering tasks
Other interfaces cover signal documentation, certification-point data, performance, weather, MFT requests, flight labeling, signal mapping, snippet import, plotting, rainflow input checks and selected data utilities.
Technologies used
Results / impact
Cloud Uploaderindependent software design and development
File Managerindependent design, development and deployment
Four NAS systemshealth and SMART monitoring scope
My contribution
- Designed and developed the Cloud Uploader queue, transfer logic, dashboard and operational controls; cloud direction and access provisioning were supplied by others.
- Independently designed, developed and deployed File Manager lifecycle automation.
- Initiated QNAP monitoring across four systems and integrated dashboard-visible notifications into DataManager.
- Confirm sole authorship of graphical interfaces across FTDA workspace applications; backend, scientific calculation and deployment scope vary by tool.
Lessons learned
Operational software includes visible state and practical controls, not only background processing.
Interface ownership and backend ownership should be described separately.
File lifecycle automation needs explicit verification and recovery boundaries.