Informationsteknik, kontorsutrustning

This document specifies requirements on the structure and expression of architecture descriptions (ADs) for various entities, including software, systems, enterprises, systems of systems, families of systems, products (goods or services), product lines, service lines, technology, and business domains. In this document, the term entity of interest refers to the entity whose architecture is under consideration in the preparation of an architecture description (AD).
This document distinguishes the architecture of an entity of interest from an AD expressing that architecture. ADs, not architectures, are the subject of this document. Whereas an AD is a tangible work product, an architecture is intangible and abstract that can be understood through its concepts, properties and principles.
This document specifies requirements on use of the architectural concepts and their relationships captured in an AD and does not specify requirements for any entity of interest or its environment.
This document specifies requirements on architecture description frameworks (ADFs), architecture description languages (ADLs), architecture viewpoints and model kinds in order to usefully support the development and use of ADs. This document also provides motivations for use of architecture-related terms and concepts in other documents such as guides and standards.
This document specifies conformance to the requirements on ADs, ADFs, ADLs, viewpoints, and model kinds.
This document does not explicitly address completeness or correctness of an AD. Nevertheless, completeness and correctness of an AD can be partially checked, for example, through the consistency of the AD elements established, whether relationships are transitive, and whether AD elements are shown in the respective views. Consistency rules can also be defined with respect to showing the same particular AD element has correspondences with an AD.
This document does not specify the processes, architecting methods, models, notations, techniques or tools by which an AD is created, utilized or managed.
NOTE ISO/IEC IEEE 42020 [17] specifies a set of processes for architecting which can be employed in support of creating one or more ADs. The architecture elaboration process in that standard is especially relevant for creation of ADs.
This document does not specify any format or media for recording ADs. The intent of this document is to enable a range of consistent and coherent approaches to AD including document-centric and model-based techniques.

The scope of this standard addresses five issues:

1.1 Application

This document defines a Ship Software Logging System (SSLS) for logging and retrieving software version information and current operational status to enable software maintenance for ship operational technology equipment and associated integrated systems, including but not limited to:

— Control and alarm systems;

— Fire and water mist systems;

— Navigation and communication systems;

— Steering control systems;

— Propulsion systems;

— Power generation systems;

— Performance monitoring systems;

— Auxiliary systems.

1.2 Cyber Risk Management

This document stipulates cyber risk management be incorporated into design and use of SSLS.

1.3 Technology Design: Ship Software Logging System (SSLS)

This document sets requirements for the design and usability of Ship Software Logging System (SSLS) software that:

— Records software versions for equipment with updateable software (hereinafter "equipment")

— Sets an initial log entry when equipment is first installed or detected by SSLS

— Includes a repository of electronic service reports associated with log entries

— Automatically logs reports sent by equipment

1.4 Technology Design: Networks and Hosts

This document specifies that equipment messages pass from equipment to SSLS automatically when possible.

1.5 Technology Design: Equipment

This document specifies that equipment sends standard version messages with software version information on appropriate time intervals

This international standard specifies performance requirements and test procedures for systems capable of warning the subject vehicle driver of a potential crossing-path collision with other vehicles at intersecting road segments. The Vehicle to Vehicle Intersection Collision Warning Systems (VVICW) rely on vehicle-to-vehicle (V2V) communications and relative positioning between the subject vehicle and crossing-path vehicles (remote vehicles). V2V data such as position, speed and heading are used to evaluate if an intersection collision is imminent between the subject and remote vehicles. The performance requirements specify the warning criteria for these systems. In addition, VVICW operate in specified subject and remote vehicle speed ranges, road intersection geometries and target vehicle types. Moreover, the requirements for the V2V data will be specified. The scope of this international standard includes operations on intersecting road segments (physically intersecting roads), and motor vehicles including cars, trucks, buses, and motorcycles. Responsibility for the safe operation of the vehicle remains with the driver.

This document specifies communication requirements in support of the "Smart Digital Tachograph" (SDT) as identified by Regulation of the European Union.
The specifications cover:
• the "Physical Layer" at 5,8 GHz for "SDT Communications" (SDTC);
• the "Data Link Layer" (DLL) of SDTC;
• the "Application Layer" of SDTC;
• SDTC profiles which provide coherent sets of communication tools for applications based on SDTC.
This document provides further information beneficial for the design and development of SDTC equipment.

This document specifies the representation of latitude and longitude and optionally height or depth compatible with previous editions of ISO 6709.
This document also supports the representations of other coordinate types and time that may be associated with those coordinates as defined through one or more coordinate reference systems (CRS).
This document describes a text string of coordinates, suitable for electronic data exchange, for one point including reference system identification to ensure that the coordinates unambiguously represent the position of that point. Files containing multiple points with a single common reference system identification are out of scope. This document also describes a simpler text string structure for coordinate representation of a point location that is more suitable for human readability.

This document specifies a communication protocol for networked control systems. The protocol provides peer-to-peer communication for networked control using web-services. This document describes services in layer 1 and layer 2.
The layer 1 (physical layer) specification describes the MAC sub-layer interface to the physical layer. The layer 2 (data link layer), as described in EN 14908-1, is integrated in UDP/IP communication using IPv4 and IPv6 protocols.

This document specifies an adaptation layer for the control network protocol (CNP), as described in EN 14908-1 to utilize wireless communication network. This document defines the services of the wireless communication provided to CNP layer for delivering data and commands towards and from sensors, actuators, etc. which are wirelessly connected as part of the EN 14908-1 network.
In addition, this document defines the requirements for the radio communication applicable for CNP layer operation.
For the radio communication different frequency bands can be utilized. Annex A defines requirement for operation in different frequency bands.

This document provides the principles and requirements to enable environmental and technical data provided in environmental product declarations (EPDs) for construction products and services, construction elements and integrated technical systems to be used in building information modelling (BIM) to assist in the assessment of the environmental performance of the construction works over its life cycle.
The mechanism used in this document to enable this is a data template created following ISO 23386 and ISO 23387 and the resulting data sheet.
This includes both mandatory and optional data from different types of EPD, such as generic, specific, average and representative, and other relevant information necessary for use of EPDs at the construction works level within a BIM environment.
This document gives requirements on structuring EPD information using a data template, to make EPD data machine-interpretable, and enable their integration into information-driven design, construction and operational processes.
This document is also appropriate to structure generic life cycle assessment (LCA) data for use within a BIM environment, as these data are required in the absence of suitable EPD data to enable assessment of the environmental performance at the construction works level.
The requirements in this document are further supplemented by technical information about construction products and services, construction elements and integrated technical systems. This document recommends the use of the same principles for structuring information (data template concepts) and the use of existing technical information created by other domain experts.
EXAMPLE In Europe, Construction Products Regulation (CPR) experts are responsible for structuring technical information based on European Harmonised Standards. This information might already exist in a data
dictionary, and EPD/LCA experts are advised to use it for the technical description of products in EPD
This document is intended to help in the understanding the different template concepts and their relation to EPD information and to enable users to create new concepts according to their specific needs.
NOTE For example, experts developing sub-category PCR according to ISO 21930 or complementary PCR (c-PCR) according to EN 15804 could create a data template for additional specific requirements in the sub-category PCR or c-PCR for the relevant product group.
The assessment of environmental performance at the construction works level is not covered by this document.