Allmänt. Terminologi. Standardisering. Dokumentation

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.

This document defines basic concepts and terminologies related to enhanced oil recovery (EOR) methods, including thermal recovery, gas drive, chemical flooding, and microbial enhanced oil recovery.

It does not include definitions or terms specific to:

a) oil reservoir engineering,production engineering, and surface engineering

b) other technical fields

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.

This document specifies business requirements for processes intended to preserve digital data. NOTE Data are stored and maintained for the purpose of retrievability and usability during the required archiving period. In addition, for the purpose of some business requirements, data are authentically preserved and accessed. This document is intended to allow for different implementations based on a company’s specific business environment. This document is not intended to incorporate company specific requirements and does not dictate specific organizational structures within a company. This document does not specify a design or an implementation of an archive system. Actual implementations can distribute responsibilities or break out functionality differently. This document assumes that all requirements for configuration management of the product data are in place and therefore are not specifically described in this document.

This document establishes general principles of presentation to be applied to construction drawings for general arrangement and assembly, mainly within the field of building and architectural drawings.

1.1 In scope This document defines a Recommended Practice for Product Structure validation. The objective is to validate the product structure of data ingested, extracted or re-used by the archive. This document defines a method to uniquely identify each node in the product structure and to uniquely define the structure of each assembly node. 1.2 Out of scope This document will not provide validation properties for documents; CAD or other.

This document specifies the terminology, classification and the methods that are used for the grading and description of single unmounted polished diamonds over 0,25 carat (ct). This document applies to natural, unmounted, polished diamonds. It is not to be used for fancy coloured diamonds, synthetic diamonds, treated diamonds (other than is allowed for in 7.4), nor for assembled stones

This is a New Work ballot to re-activate a cancelled project. This document specifies principles, requirements, recommendations and other provisions for preparing and presenting instructions for the assembly of self-assembly products intended for a non-skilled target audience assembling a product without help from a trainer or supervisor. This document is applicable to instructions for: — supporting the assembly of a product that is supplied as a kit of components designed to be assembled into a specific item, which can have alternative assembly configurations (often described as “flatpack products”); — installing products supplied with components (e.g. screws) intended for attachment to existing products (e.g. a vehicle) or fixtures (e.g. a wall); — erecting or configuring products that incorporate structural elements requiring folding, locking or tensioning (e.g. child pushchairs, camping equipment); — supporting the assembly of a specific product intended to be assembled by a non-skilled assembler for their own use or for use by another individual (e.g. assembly of a toy by a parent for subsequent use by a child). This document does not apply to: — components or constructional material supplied in combinations and numbers specified by the customer; — multiple identical kits supplied in batches for professional assembly and commercial sale as an assembled product; — products intended for professional assembly only by someone skilled or trained in assembling such products or by a skilled person whose relevant technical education, training or experience enables them to perceive risks and avoid hazards in the assembly and use of a category of products (e.g. electrician, vehicle mechanic). This document is applicable to all parties involved in the preparation of instructions for self-assembly, including: — product suppliers; — hardware and software product and information designers; — technical communicators and technical illustrators; — testers and evaluators; — managers; — safety authorities. This document is supplementary to IEC/IEEE 82079-1, which specifies provisions applicable to the preparation of all information for use of products – including self-assembly and all other phases (such as operation, maintenance and disposal).

This document specifies requirements to be met by a management system for records (MSR) in order to support an organization in the achievement of its mandate, mission, strategy and goals. It addresses the development and implementation of a records policy and objectives and gives information on measuring and monitoring performance.

An MSR can be established by an organization or across organizations that share business activities. Throughout this document, the term "organization" is not limited to one organization but also includes other organizational structures.

This document is applicable to any organization that wishes to:

— establish, implement, maintain and improve an MSR to support its business;

— ensure itself of conformity with its stated records policy;

— demonstrate conformity with this document by

undertaking a self-assessment and self-declaration, or

seeking confirmation of its self-declaration by a party external to the organization, or

seeking certification of its MSR by an external party.

ISO/IEC 22123-1:2023 defines terms used in the field of cloud computing.