The problem
A practical problem to solve
Engineers repeated several steps to catalogue engine-data files, check their context, convert them for analysis and review results. The workflow needed clearer validation and a shared operational view.
Engineering software · data validation
EDR Data Center
Professional project · engineering application
A self-initiated application that brings recurring engine-data cataloguing, review, validation and conversion workflows into one operator-facing dashboard.
Design constraints
- Keep source files and flight context traceable.
- Let operators review proposed work before writing outputs.
- Support controlled conversion and re-export only where the workflow has the required safeguards.
- Make job state and review history visible to colleagues.
Key features
Catalogue and match
Organise source files and relate them to flight and engine context.
Validate and preview
Review source data and proposed actions before conversion or adoption.
Convert and trace
Produce TDMS outputs with manifests, job status and activity history.
Review with operators
Provide per-flight review views and guided help for engineering colleagues.
Solution
Designed around a useful decision
The dashboard connects source cataloguing and validation with conversion, adoption of existing outputs, per-flight review and job tracking. Preview and confirmation steps make operator decisions visible. Controlled re-export and replacement behavior is limited to supported workflows; safeguards are not identical for every aircraft or source profile.
Visual space
Conceptual workflow: engine-data sources pass through cataloguing, validation and operator review before supported conversion to analysis-ready outputs.
Workflow
Catalogue
Scan configured source locations and build a view of available engine-data files.
Match and validate
Relate files to flight context, inspect data quality and surface issues for review.
Preview
Show proposed conversion or adoption actions before writing outputs.
Convert or adopt
Create supported TDMS outputs or register an existing output with traceable context.
Review
Use flight-level views, manifests and activity history to inspect the resulting workflow.
Technologies used
Results / impact
Consolidatedrecurring engineering workflows
Traceablejobs and source context
In usecolleague onboarding and support
My contribution
- Identified the recurring workflow need and initiated the application.
- Designed the application architecture and developed processing, validation and dashboard workflows.
- Introduced colleagues to the tool through demonstrations, onboarding and interactive help.
- Used AI-assisted coding during development while retaining engineering responsibility for design and validation.
Lessons learned
A preview step gives operators a clear decision before data is written.
Traceability links derived outputs back to source files and review actions.
A replacement workflow should expose exactly which profiles have adequate safeguards.