Our unique Digital Mission Engineering Platform has through-life traceability and connectivity helping organisations accelerate and de-risk technical projects and maintain the systems they deliver.

To design intentional change to a system and to build, operate, maintain, and dispose of it, we must first develop a deep and accurate understanding of that system.

 

At the scale of the integrated systems of systems that our customers are designing, that deep, accurate understanding must also be shared between many parties.

 

A shared understanding takes the form of an accessible description.  To design intentional change to a system, we must understand and, therefore, describe:

• The actual and expected behaviour of the system and the changes in state that behaviour imposes on the system's environment and within the system, as well as the compositional and structural information describing the relevant actors/agents/performers, enablers and resources involved in that behaviour.  More specifically, we must be able to describe:

  • The sequences of actions, interactions and exchanges occurring under specific conditions and in the presence of events in the environment that result in the transformation of state;

  • The actors/agents/performers that act, interact and exchange in the execution and support of that behaviour and the enablers of those actions, interactions and exchanges;

  • Information about the resources (including Information and Data) that are produced, consumed, transformed, observed, interrogated, and exchanged by that behaviour - and the relationships between those resources.

 

This must be understood at least at the operational level (the level at which that system of interest is to be used/employed to some effect).

 

To support and sustain such a system in operational use, we must be able to describe behaviour, composition and structure recursively to the level of detail that we are responsible for maintaining.

 

To manage and assure the design of intentional change into a system, we must describe that system to a level of fidelity where we can understand the following:

• Requirements and constraints on the behaviour, composition or structure of the system.

• The qualification requirements and evidence used to claim that the system will/does behave as expected with no unintended consequences.

 

Traditionally, these descriptions exist in disparate and distributed documents and drawings.  Even in the limited cases where such information can be understood - the tax on human short-term memory of making sense of this information is generally too great a burden to enable understanding - the information within these sources is often inconsistent, incomplete and ambiguous providing dubious guidance to design. Kompozition integrates and provides access to this information, accelerating and de-risking design.