TOICA improved on existing capabilities and created new emergent methods and tools, answering specific business needs (the use cases), and testing them in near programme-like conditions (the plateaus).
is a collaborative design environment enabling architects, experts and suppliers to share crucial information, such as details of the requirements and constraints, or of the characteristics of individual components. It also allows users to view representations of the thermal architecture of the future plane. They can exchange models, assess the evolving design, and jointly consider any trade-offs that may be necessary to optimise the aircraft.To build the system, TOICA partners Dassault Systemes, MSC.Software and Siemens Industry Software used their existing software tools for some of the required functionalities and developed additional capabilities to enhance the features and interoperability of their products. The Architect Cockpit specifications are available as a public deliverable.
is a system of integrated methods and principles for architects to manipulate agilely the functions, behaviours, requirements and physical allocations to systematically discover, explore and articulate new architectures that create opportunities for assessing competitive product architectures and designs.
represents organisationally sets of coupled models used for multi-level and/or multi-disciplinary analyses and is aimed at securing fast and reliable configuration and computation of the integrated model. These simulation data describe the thermal aircraft behaviour and are delivered to architects within the Architect Cockpit for the selection of the best concept.
tools accessible directly from the Architect Cockpit give architects the opportunity to evaluate new functional architecture candidates against a Value Creation Strategy (VCS). A VCS includes initially a set of rank-weighted needs that have to be satisfied, or in later iterations sets of rank-weighted objectives with corresponding measurement criteria, as well as a set of value drivers.
is a capability that addresses the creation of models along two major streams:
Such a capability empowers the Architect Cockpit platform with the easy assembly of inputs along the setup of a trade study, where variants in architecture are in a way also treated as models (objects of trades). This latter transition from architecture representations to various granularities of simulation models is the border where the Pyramid of Models and Flexible Model Generation meet.
have been analysed and tested, such as using fuel as a heat sink. Different installation scenarios of a mixed cooling architecture combining air ventilation and heat pipes coupled to a mini-VCS (Vapour Cycle air conditioning System) were evaluated as part of a thermal management of an avionic bay study.
are the methods and tools used by Aircraft Program Architects & Chief Engineers to generate and manage the lifecycle of the distributed product dataset. The capabilities can be split into three different levels: The Business view, the Logical (organizational) view, and the (Information) Technology view. Tools exploiting the BDA Business Object Model and associated web services were updated and exploited at plateaus.
The specifications of BDA architecture based on a SysML model and the BDA data exchange (DEX), which describes the BDA services as a part of the standardisation activities MoSSEC (Modelling and Simulation in a collaborative Systems Engineering Context), are available as public deliverables.
Modelling and simulation technical data and collaboration context data are used to justify change decisions and to validate the product throughout the product lifecycle. There are already mature standards for exchanging modelling and simulation technical data (e.g. other STEP AP standards), but these either do not include traceability to the systems engineering and product/simulation lifecycle context, or are inefficient for data sharing. Such context information can be summarized as “who”, “what”, “where”, “when”, “how”, “why”, and the goal of the MoSSEC AP is to provide a standard for sharing this information. The MoSSEC AP will be agnostic of the type of modelling and simulation, and it is the intention that modelling and simulation technical data will continue to be exchanged using technical standards in use today (e.g. AP209, AP210, AP242, FMI). See also www.mossec.org.
is a way to deal with the uncertainty of variables that are used in decision-making problems in which observations and models represent the knowledge base.
A model is said to be multi-physics when more than one domain of physics is solved at a time. For instance a thermo-mechanical model is multi-physics. A system representation is often multi-physics as it allows for the modelling of a mechatronics system.
A model organization is said to be multi-level when a layered structure can be extracted to ease the understanding of a given assembly of models. Coupling of multi-physics and multi-level aims at providing the engineer with predictive answers on the behaviour of a given complex subject (system, part, etc.).