D4 + D5 software workflow
D4 software scope closed. D5 demonstrated headlessly for single-bank P1, under SOFTWARE TEST ONLY conditions.
All projects
Aircraft ECS Sizing & Trade Study Tool
From a thermal requirement to an informed system choice.
Stable release · ready for validationECS sizing & trade studies
From thermal requirements to the comparison of complete ECS configurations.
The engineering question
How can thermal loads, airflows and equipment performance be assessed together while keeping design assumptions and operating margins clear?
The workflow
The process starts with operating conditions, then examines the required thermal loads and airflows. Equipment options are compared before the overall system balance and margins are reviewed.
The tool is designed to connect requirements, equipment selection and system-level checks in one traceable process. Software verification is reported with its limitations and does not replace qualification with suitable engineering data.
The evidence boundary
Software checks are kept separate from engineering validation. The results shown in demonstrations cannot be used as acceptance evidence for equipment, aircraft or complete systems.
Experience & development approach
A development project rooted in engineering practice.
I am developing this tool to connect the stages of an ECS sizing study within a traceable workflow. The project draws on my background in aircraft environmental control and thermal systems, with attention to the assumptions that link requirements, calculations and equipment choices.
The working approach is to define the operating case, examine the loads and available equipment, and review the resulting system balance and margins. Development and software verification are tracked separately from engineering validation on real data; the roadmap below makes that distinction explicit.
Development roadmap
From software workflow
to an integrated interface.
Status snapshot 1 November 2026 · V0.9.21
The development plan separates completed software checks from current work and the next steps. Software testing does not replace engineering validation of the system.
Stable release · single-bank — SOFTWARE TEST ONLY
stable-8919ef46-r1.1
Release stable-8919ef46-r1.1 is available as the basis for engineering validation. Completed checks cover software behaviour only in the single-bank configuration — SOFTWARE TEST ONLY.
D6 · accepted software workflow
Component selection, results review, applying changes and saving and reopening the project have been verified.
Engineering validation
The next phase starts with synthetic-data checks, followed by validation using suitable real-world data. Engineering validation remains open.
The development path
Foundations
Requirements, architecture and component libraries.
Scope & next checks
Established software foundations; equipment data quality and engineering validation remain separate.
Consolidated
Automated sizing · D4
Calculation workflow and candidate assessment.
Scope & next checks
Completion refers to the agreed software scope, not continuous-domain or hardware validation.
Software scope completed
Apply & accounting · D5
Headless workflow: single-bank P1.
Scope & next checks
SOFTWARE TEST ONLY. Completion does not establish a fully integrated desktop workflow or equipment acceptance.
Defined test scope completed
R1.1 · SOFTWARE TEST ONLY
User interface integration · D6The complete interface workflow has been verified for the single-bank test case.
Accepted within software scope
Reporting & trade studies
PDF reporting checked within the software scope. Alternative ranking is not yet demonstrated.
Partial
Engineering validation
One validation stage: synthetic data first, then real-world data.
Scope & next checks
Synthetic-data checks will assess model consistency, assumptions and behaviour, including guided use of the tool. Validation with real-world data will require reliable sources and defined acceptance criteria. Neither activity is reported as complete.
Upcoming
Latest progress
Chart display and messages for unavailable data or resources have been checked.
The configuration and source associations are preserved. A new evaluation is required after reopening to obtain current results.
PDF reporting has been checked within the software scope. The graphical aircraft catalog remains planned, not yet implemented and unscheduled.
Original plan and test results
21 October 2026 – 6 February 2027
Original planning windows and newly scheduled activities. The dashed line shows the current date and updates automatically; bars do not show completion percentages.
PROJECT STATUS · 1 NOVEMBER 2026
Stable release · ready for validation.
Component selection, results review, applying changes and saving and reopening the project have been verified.
single-bank — SOFTWARE TEST ONLY. Software verification does not establish engineering validation.
Planned periodsUpdate · 1 NovemberChecks completedIn progressFor review
← Scroll the chart to view the original dates →
Activity / window
Check results
21/1028/1004/1111/1118/1125/1102/1209/1216/1223/1230/1206/0113/0120/0127/0103/02
D4/D5 test results
Original window: 21 OctoberVerified (P1)
D4/D5 software checks completed for the P1 test case.
Technical details
D5 was verified for one equipment bank. These checks establish software behaviour within the declared test scope, not aircraft-system validation.
Calculation and GUI review
Original window: 22–26 OctoberVerified (P1)
Calculation, candidate selection and review verified.
Technical details
The accepted software workflow includes candidate selection and review. Current session results remain distinct from imported project inputs.
Scope and plan review
Original window: 27 OctoberScope confirmed
Software acceptance recorded; engineering validation remains open.
Technical details
The Rev07 update records scoped software completion. Historical forecast dates are retained. The aircraft-family catalog is planned, not implemented, with no dates or estimates.
Release consolidation
Original window: 28 OctoberVerified (R1.1)
Stable Windows release checked and available for the next phase.
Technical details
The release summary records Windows interface checks, targeted regressions, backup and restore checks. These results apply to stable-8919ef46-r1.1 within the declared software scope.
D6 workflow checks
Original window: 29 October–2 NovemberVerified (single-bank)
Native Apply and save/reopen verified within the test scope.
Technical details
The accepted case covers a confirmed Apply, saving to a new file and reopening through the production loader. Source associations persist; current source payloads and review authority are not restored by reopening.
Planning review
Original window: 3 NovemberPlanned
Original planning-review window.
Technical details
The original 3 November review window is retained for reference. The new validation activities are shown below.
Software validation with synthetic data
1 Nov – 26 Dec 2026 · 8 calendar weeksPlanned
Further development and model checks using synthetic cases.
Technical details
A planned period of 56 consecutive days, including weekends and holidays. Previously completed software checks remain separate from this new activity.
Engineering validation with real-world data
27 Dec 2026 – 6 Feb 2027 · 6 calendar weeksPlanned
Comparison with real-world data against acceptance criteria.
Technical details
A planned period of 42 consecutive days after the synthetic-data phase. Suitable real-world data and defined acceptance criteria are required.
D4/D5 test results
Original window: 21 October
Verified (P1)D4/D5 software checks completed for the P1 test case.
Technical details
D5 was verified for one equipment bank. These checks establish software behaviour within the declared test scope, not aircraft-system validation.
Calculation and GUI review
Original window: 22–26 October
Verified (P1)Calculation, candidate selection and review verified.
Technical details
The accepted software workflow includes candidate selection and review. Current session results remain distinct from imported project inputs.
Scope and plan review
Original window: 27 October
Scope confirmedSoftware acceptance recorded; engineering validation remains open.
Technical details
The Rev07 update records scoped software completion. Historical forecast dates are retained. The aircraft-family catalog is planned, not implemented, with no dates or estimates.
Release consolidation
Original window: 28 October
Verified (R1.1)Stable Windows release checked and available for the next phase.
Technical details
The release summary records Windows interface checks, targeted regressions, backup and restore checks. These results apply to stable-8919ef46-r1.1 within the declared software scope.
D6 workflow checks
Original window: 29 October–2 November
Verified (single-bank)Native Apply and save/reopen verified within the test scope.
Technical details
The accepted case covers a confirmed Apply, saving to a new file and reopening through the production loader. Source associations persist; current source payloads and review authority are not restored by reopening.
Planning review
Original window: 3 November
PlannedOriginal planning-review window.
Technical details
The original 3 November review window is retained for reference. The new validation activities are shown below.
Software validation with synthetic data
1 Nov – 26 Dec 2026 · 8 calendar weeks
PlannedFurther development and model checks using synthetic cases.
Technical details
A planned period of 56 consecutive days, including weekends and holidays. Previously completed software checks remain separate from this new activity.
Engineering validation with real-world data
27 Dec 2026 – 6 Feb 2027 · 6 calendar weeks
PlannedComparison with real-world data against acceptance criteria.
Technical details
A planned period of 42 consecutive days after the synthetic-data phase. Suitable real-world data and defined acceptance criteria are required.
Plan updated on 1 November 2026: 8 calendar weeks for software validation with synthetic data, followed by 6 weeks for engineering validation with real-world data. These are planned dates, not evidence of completed work.
single-bank — SOFTWARE TEST ONLY. Software checks do not establish engineering validation or certification.
ECS software gallery
Explore the interface.
Actual R1.1 software screens with synthetic inputs after reopening the project. No new calculation: dashes indicate unavailable results, not zero. single-bank — SOFTWARE TEST ONLY.
Project overview
Project inputs and available indicators after reopening.
Inside the tool
Purpose & capabilities
A structured environment for exploring environmental control system sizing, equipment candidates and design trade-offs.
Define the design problem
Organise aircraft conditions and cabin and cockpit thermal loads into a consistent sizing workflow.
Explore equipment candidates
Work with compressor, fan and heat exchanger information. Compare eligible candidates and record selection rationale.
Understand the system
Review architecture, cooling capacity, electrical demand and available margins together.
Keep decisions traceable
Connect equipment selection and system accounting to their engineering context as the design evolves.
DESIGN POINT / DEMONSTRATIONVCS
Thermal load10.7 kW
Required11.3 kW
Available11.7 kW
Illustrative presentation with synthetic values. Not a software screenshot or validated sizing result.
Discuss an engineering project
Contact Francesco to discuss the workflow, its scope or a potential technical collaboration.
Get in touch →