Informationsteknik, kontorsutrustning

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 the requirements and provides guidance for the definition, implementation, maintenance and improvement of a quality management system for organizations that provide AI systems. This document is intended to support the organization in meeting applicable regulatory requirements.

ISO 11616:2017 is intended to provide specific levels of information relevant to the identification of a Medicinal Product or group of Medicinal Products. It defines the data elements, structures and relationships between data elements that are required for the exchange of regulated information, in order to uniquely identify pharmaceutical products. This identification is to be applied throughout the product lifecycle to support pharmacovigilance, regulatory and other activities worldwide. In addition, ISO 11616:2017 is essential to ensure that pharmaceutical product information is assembled in a structured format with transmission between a diverse set of stakeholders for both regulatory and clinical (e.g. e-prescribing, clinical decision support) purposes. This ensures interoperability and compatibility for both the sender and the recipient. ISO 11616:2017 is not intended to be a scientific classification for pharmaceutical products. Rather, it is a formal association of particular data elements categorised in prescribed combinations and uniquely identified when levelling degrees of information are incomplete. This allows for Medicinal Products to be unequivocally identified on a global level. References to other normative IDMP and messaging standards for pharmaceutical product information are included in Clause 2, to be applied in the context of ISO 11616:2017. Medicinal products for veterinary use are out of scope of ISO 11616:2017.

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.

 ISO 14819-1 describes the ALERT-C protocol concept and message structure used to achieve densely coded messages to be carried in the RDS-TMC feature. This document specifies the ‘Events List’ to be used in coding those messages.

The present document is composed of the following data packages:

— journey and Interchange;

— vehicle Journey Assignment;

— journey Times;

— block and Vehicle Service;

— dated Journey;

— explicit Frame.

This document itself is composed of the following parts:

— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);

— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);

— Annex B presenting the model evolution (informative);

— Annex C, providing details of the significant technical changes between this document and EN 12896 1:2015 (informative)

This document incorporates the following main data packages:

— Network Description;

— Fixed Object;

— Tactical Planning Components;

— Explicit Frame.

It is composed of the following parts:

— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);

— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);

— Annex B presenting the model evolution (informative).

— Annex C, providing details of the significant technical changes between this document and EN 12896-2:2016 (informative). 

This document incorporates the following main data packages:

— Dated Production Components;

— Call;

— Dated Call;

— Production Plan;

— Detecting & Monitoring;

— Situation;

— Messaging;

— Control Action;

— Operational Event & Incident;

— Facility Monitoring & Availability;

— Occupancy.

It is composed of the following parts:

— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);

— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);

— Annex B presenting the model evolution (informative);

— Annex C detailing the mapping to DATEX-II and SIRI (informative).

— Annex D, providing details of the significant technical changes between this document and EN 12896-4:2019 (informative).

This document entitled “Public transport – Reference data model – Part 5: Fare Management” is 

composed of the following data packages: 

— Fare Structure; 

— Access Right Assignment; 

— Fare Pricing; 

— Sales Description; 

— Sales Transaction; 

— Fare Roles; 

— Validation and Control; 

— Explicit Frames for Fares. 

This document itself is composed of the following parts: 

— Main document representing the data model for the concepts shared by the different domains 

covered by Transmodel (normative); 

— Annex A, containing the data dictionary and attribute tables, i.e., the list of all the concepts presented 

in the main document together with the definitions (normative); 

— Annex B, presenting the model evolution (informative). 

— Annex C, providing details of the significant technical changes between this document and EN 12896

5:2019 (informative)

The document incorporates the following main data packages: 

— Trip Description; 

— Passenger Information Queries. 

It is composed of the following parts: 

— main document representing the data model for the concepts shared by the different fare domains 

covered by Transmodel (normative); 

— Annex A, containing the data dictionary and attribute tables, i.e. the list of all the concepts presented 

in the main document together with the definitions (normative); 

— Annex B presenting the model evolution (informative). 

— Annex C, providing details of the significant technical changes between this document and 

EN 12896-6:2019 (informative).

This document is composed of the following data packages: 

— Driver; 

— Driver Schedule; 

— Rostering; 

— Personnel Disposition; 

— Driver Control Action. 

This document itself is composed of the following parts: 

— main document representing the data model for the concepts shared by the different domains 

covered by Transmodel (normative); 

— Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts presented 

in the main document together with their definitions (normative); 

— Annex B presenting the model evolution (informative). 

— Annex C, providing details of the significant technical changes between this document and EN 12896

7:2019 (informative)

This document describes common capabilities, requirements and a supporting information model for logging of events in AI systems. This document is designed to be used with a risk management system.

This document specifies the requirements and provides guidance for establishing, implementing, maintaining and continually improving an AI management system within the context of an organization. This document is intended for use by an organization providing or using products or services that utilize AI systems. This document helps the organization develop or use AI systems responsibly in pursuing its objectives and meet applicable regulatory requirements, obligations related to interested parties and expectations from them. This document is applicable to any organization, regardless of size, type and nature, that provides or uses products or services that utilize AI systems.

This document provides guidance on human control and monitoring of AI systems, which is referred to as human oversight. This document extends ISO/IEC TS 8200. This document is applicable to all types of organizations. This document is applicable throughout the AI system life cycle.

This document incorporates data structures used by all other data domains of Transmodel. It is composed of the following data packages:

versions and validity; 

responsibility; 

generic framework; 

reusable components; 

explicit frames referring to generic data. 

The data structures represented in this part are either generic patterns that can be explicitly reused in 

other domains (e.g., a generic model for version frames, a generic grouping mechanism, etc.) or are 

referenced by different other parts (e.g., service calendar model). 

This document itself is composed of the following parts: 

main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);

Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts 

present in the main document, together with their definitions (normative);  

Annex B, indicating the data model evolutions (informative), 

Annex C, presenting the Transmodel development history (informative), 

Annex D, describing all conventions, methodology and notations for conceptual modelling (informative), 

Annex E, providing a clear overview to help readers understand the core principles, structure, and purpose of Transmodel (informative), 

Annex F, providing information on the Functional domains and Modes of operation (informative). 

Annex G, providing details of the significant technical changes between this document and EN 12896-1:2015 (informative). 

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.

ISO/IEC 29146:2024 defines and establishes a framework for access management (AM) and the secure management of the process to access information and Information and Communications Technologies (ICT) resources, associated with the accountability of a subject within some context. ISO/IEC 29146:2024 provides explanations about related architecture, components and management functions and concepts, terms and definitions applicable to distributed access management. The subjects involved in access management might be uniquely recognized to access information systems, as defined in ISO/IEC 24760.

This standards shall provide specifications applicable to vulnerability handling processes, covering all relevant product categories, to be put in place by manufacturers of the products with digital elements. Those processes shall at least allow to: (a) identify and document vulnerabilities and components contained in the product, including by drawing up a software bill of materials in a commonly used and machinereadable format covering at the very least the top-level dependencies of the product; (b) in relation to the risks posed to the products with digital elements, address and remediate vulnerabilities without delay, including by providing security updates; where technically feasible, new security updates shall be provided separately from functionality updates; (c) apply effective and regular tests and reviews of the security of the product with digital elements; (d) once a security update has been made available, share and publicly disclose information about fixed vulnerabilities, including a description of the vulnerabilities, information allowing users to identify the product with digital elements affected, the impacts of the vulnerabilities, their severity and clear and accessible information helping users to remediate the vulnerabilities; in duly justified cases, where manufacturers consider the security risks of publication to outweigh the security benefits, they may delay making public information regarding a fixed vulnerability until after users have been given the possibility to apply the relevant patch; (e) put in place and enforce a policy on coordinated vulnerability disclosure; (f) take measures to facilitate the sharing of information about potential vulnerabilities in their product with digital elements as well as in third party components contained in that product, including by providing a standardised contact address for the reporting of the vulnerabilities discovered in the product with digital elements; (g) provide for mechanisms to securely distribute updates for products with digital elements to ensure that vulnerabilities are fixed or mitigated in a timely manner, and, where applicable for security updates, in an automatic manner; (h) ensure that, where security updates are available to address identified security issues, they are disseminated without delay and, unless otherwise agreed between manufacturer and business user in relation to a tailor-made product with digital elements, free of charge, accompanied by advisory messages providing users with the relevant information, including on potential action to be taken.

This standard describes the requirements to be satisfied by domain-specific reference architectures that address entities of interest such as software, systems, enterprises, missions, systems of systems, families of systems, products (goods or services), product lines, service lines, technologies and business domains. The proposed standard will be universally applicable to — organizations seeking sustained success through the implementation of architecture practices, — organizations and interested parties seeking to improve communication through a common understanding of the vocabulary and concepts used in reference architectures, — organizations performing conformity assessments against the requirements of reference- architecture-related standards and specifications, — organizations that serve as certification authorities that will benefit from the use of reference architectures, — organizations that need to mandate use of reference architectures, — providers of reference architectures, guidelines, training, education, evaluation or recommendations in architecture practice, — developers of reference-architecture standards, reference models, and related tools/technologies, — users of reference architectures. The application areas of this standard include, but are not limited to, the following: artificial intelligence (AI), machine learning (ML), Internet of Things (IoT), cloud computing, big data, smart cities, smart manufacturing, cybersecurity, digital twin, telecommunications, aerospace, defense, banking, finance, insurance, energy, automotive, logistics, hospitality, healthcare, supply chain, transportation, manufacturing, agriculture, production, and infrastructure. The proposed deliverable is part of the ISO 42000 architecture standards (e.g., 42010, 42020, 42030).

This document provides trustworthiness requirements and guidance for data space participants in support of trusted data transactions. Specifically, it defines a set of foundational principles for trusted data transactions, and establishes general requirements and guidance that apply to all phases of a trusted data transaction, and specific requirements for each phase of a trusted data transaction. This document applies to all types of organizations participating in data spaces, regardless of their type or size.