ÖNORM EN 9300-500

1.1 In Scope The EN 9300-5xx series specifies the methods for long term archiving and retrieval of MBSE data represented as digital models. The characterization of models that are considered in scope of this document and the MBSE process use cases include: - product or system design requirements models; - functional architecture models; - logical architecture models (system structure, arrangement, connectivity, software allocations and controls, and part relationships); - numerically-based system analysis and simulation models, generally regulated 1D control loop models featuring system components and transport elements (tubing, piping, signalling, software); - verification and validation of requirements; - protocol dependent signal or communication networks; - multi-model linking and system parametric models; - system trade study models; - the solution architecture models and data that are needed to implement the system and generate system engineering data for downstream designs. 1.2 Out of Scope The EN 9300-5xx series does not address the original product model design process, or a specific configuration management process for the LOTAR archive. It does not address models depicting part specific technical data (physical materials or detail part standards). It is assumed that these archiving processes are within the scope of other parts of the EN 9300 series such as the 1xx series for CAD, the 2xx series for Product Data Management (PDM) data, or by applying existing alternative industry standards, or existing company business procedures. Typical models and capabilities considered out of scope of this document include: - physical spatial models or composite structures (as described by other LOTAR Parts); - Finite Element and CFD models (as described by other LOTAR Parts); - Product Data Management models (as described by other LOTAR Parts); - electrical circuit boards, or physical wiring parts or systems (described by other LOTAR Parts or standards); - the software development process and software models that are outside of the context of software parts, behaviours, or functions that represent software code within a model; - how to preserve property and access rights, or government acquisition-regulatory controls; - new standards, or major revisions to existing MBSE standards that were not available or applicable prior to the publication of this document.