System architecture
System Architecture
High-level relationship between propulsion, energy, control, safety, structures, and software.
Available within programme documentationDocumentation
The engineering record of the AICA programme.
AICA documentation records the assumptions, architecture decisions, research questions, development methods, and validation activities that shape the programme.
Documents evolve as engineering evidence matures. Conceptual material, simulation results, subsystem validation, and future prototype testing should remain clearly distinguishable.
Documentation status
Active · Continuously evolving
Document library
Navigate the programme documentation.
Programme overview
Programme Overview
Mission, programme structure, engineering philosophy, and development approach.
Open documentation →Research
Research Programme
Research areas, current engineering questions, methodology, and validation strategy.
Open documentation →Development roadmap
Development Roadmap
Programme phases from long-term concept research through simulation, subsystem development, integration, demonstrator development, and future validation.
Open documentation →Engineering journal
Engineering Journal
Design notes, programme updates, technical observations, and development milestones.
Open documentation →Technical notes
Technical Notes
Focused engineering records covering specific assumptions, methods, analyses, and design decisions.
In developmentDocument structure
Different documents carry different levels of engineering authority.
Class 01
Concept documents
Capture ideas, assumptions, candidate architectures, and early engineering reasoning.
Status meaning
Exploratory · Subject to change
- —concept studies
- —architecture sketches
- —feasibility notes
- —research questions
Class 02
Analysis documents
Record analytical work, simulation methods, modelling assumptions, and comparative engineering studies.
Status meaning
Model-supported · Not yet physical validation
- —CFD studies
- —FEA studies
- —energy models
- —control simulation
- —trade studies
Class 03
Future programme stageValidation documents
Record results from physical subsystem testing and experimental engineering work.
Status meaning
Experiment-supported
- —bench tests
- —component validation
- —thermal tests
- —structural tests
- —hardware-in-the-loop results
Class 04
Future programme stageVehicle test documents
Record integrated prototype and future vehicle testing.
Status meaning
Measured vehicle evidence
- —ground tests
- —integrated system tests
- —flight-test reports
- —measured vehicle performance
Evidence status
Read every claim in the context of its evidence.
01
Concept
Early engineering hypothesis or architecture direction.
02
Simulated
Supported by analytical or numerical modelling.
03
Bench validated
Supported by physical subsystem or component testing.
04
Prototype validated
Supported by integrated prototype testing.
05
Measured
Observed directly during representative physical testing.
Important: A document's status indicates the maturity of its supporting evidence, not the importance of the work.
Performance targets must not be presented as measured vehicle capabilities before appropriate physical validation.
Documentation principles
Documentation is part of the engineering process.
01
Traceability
Important assumptions and design decisions should have a documented engineering basis.
02
Versioning
Engineering understanding evolves. Documents should reflect meaningful revisions rather than silently rewriting programme history.
03
Limitations
Known uncertainties, assumptions, model limitations, and validation gaps should be stated where relevant.
04
Evidence before claims
Published performance statements should reflect the maturity of the evidence supporting them.
Programme history
A long-term engineering programme.
Concept & Research
2014 — Present
The AICA concept and underlying engineering research began in 2014. The programme has developed through long-term conceptual work, architecture exploration, calculations, system studies, and progressively more structured engineering documentation.
2014
Concept & Research begins
Present
Structured engineering programme, simulation, system architecture, documentation, and preparation for progressive validation
Future
Subsystem testing · integration · demonstrator · physical vehicle validation
Engineering records
Recent programme documentation.
Record 01
Concept Evolution
View in Engineering Journal →
Record 02
Engineering Architecture
View in Engineering Journal →
Record 03
Energy System Development
View in Engineering Journal →
These records form part of the living engineering journal. Individual record pages are not currently published.
Continue exploring
Explore the engineering programme.
Research defines the questions. Documentation records the reasoning. Validation determines what the platform can ultimately achieve.