Toimialayhteisöt

 

1.1 Scope of prEN 1991-1-6 (1) prEN 1991-1-6 provides guidance and general rules on the determination of actions relevant for the design of buildings and civil engineering works, including geotechnical structures, for their execution stage. NOTE Actions for design during execution include those that only arise from execution activities and act during execution, termed construction actions (for example personnel and hand tools, auxiliary structures, equipment and elements used during execution), and others that are present during the service life of the completed structure (for example self-weight, wind, etc.) but which can act differently and/or have different values during execution. (2) prEN 1991-1-6 provides guidance and general rules for the determination of actions for the design of auxiliary structures, elements and equipment used during execution in case they are designed to the Eurocodes and not to other European Standards. NOTE Other European Standards (e.g. EN 12810, EN 12811, EN 12812) provide specific rules for certain types of auxiliary structures, equipment and elements used during execution. (3) prEN 1991-1-6 gives rules for buildings and bridges during execution to supplement the provisions in EN 1990. NOTE For combination rules for execution, see EN 1990. 1.2 Assumptions (1) The general assumptions given in EN 1990 apply. (2) The application of this document follows the limit state principle and is based on the partial factor method, unless explicitly prescribed differently. (3) The verification of buildings and civil engineering structures in transient design situations is undertaken in accordance with the Eurocodes, accounting for the interaction with any auxiliary structures, elements and/or equipment. (4) When using European product standards covering auxiliary structures, equipment and elements used during execution, it is assumed that the design basis, design requirements and, if provided, the safety and operational design limits specified in these product standards are taken into account. (5) Adequate planning, documentation, communication, control and supervision are provided during execution, involving all relevant parties. NOTE Execution of a structure can involve interaction between several parties from diverse engineering fields, responsible for the design, fabrication, transportation and execution of different subsystems used during the execution of a structure.

 

1.1 Scope of EN 1991-3 (1) EN 1991-3 defines actions imposed by cranes and other machines including dynamic effects, if relevant, for the structural design of crane or machine supporting structures. (2) EN 1991-3 provides guidance on crane classification in terms of dynamic factors and fatigue actions. (3) EN 1991-3 applies to supporting structures of — bridge cranes, gantry cranes and wall cranes travelling on fixed runways; — fixed machines that cause a harmonic dynamic loading on fixed supporting structures. (4) The principles provided in EN 1991-3 can be applied also to determine actions on supporting structures of cranes other than those referred to in (3). (5) EN 1991-3 does not provide partial factors for actions. NOTE For partial factors for actions, see EN 1990-1:2023+A1:2026, Clause A.5. (6) EN 1991-3 does not provide actions or provisions for the design of cranes and machines. 1.2 Assumptions (1) The general assumptions of EN 1990-1 apply. (2) The design of structures supporting cranes or machines is undertaken using information on actions provided by the manufacturer of the crane or machine.

 

1.1 Scope of EN 1991 1 8 (1) EN 1991 1 8 gives principles and rules to determine the values of wave and current actions on structures and civil engineering works in the coastal zone, i.e. works connected to, or in close vicinity to the shore. NOTE 1 Provisions in EN 1991 1 8 are limited to hydrodynamic actions that can be directly quantified in terms of wave and/or current induced pressures and associated forces and moments on structures or structural parts. NOTE 2 As opposed to offshore conditions, waves or currents in the coastal zone are generally affected by the presence of the seabed or shore. NOTE 3 The coastal zone is typically defined as the area between the shoreline and the deep-water limit. (2) EN 1991 1 8 describes the principles for defining the hydrodynamic conditions to be used for design, including sea water levels. (3) EN 1991 1 8 addresses specifically actions from currents and waves on the following structure types: — cylindrical structures; — subsea pipelines; — suspended decks; — vertical face structures; — permanently moored floating structures. NOTE 1 Additional guidance can be needed for: — moored structures in the coastal zone for renewable energy production or related to oil and gas production or processing; — moored structures spanning areas with variable wave and current states (e.g. floating aquaculture farms or floating bridges). NOTE 2 For hydraulic pressures caused by quasi-static water levels, and ground water, see EN 1997 (all parts). (4) Actions addressed in EN 1991 1 8 do not cover: — hydraulic resonance in sheltered areas or basins (phenomena also known as harbour resonance); — translation waves, e.g. tsunamis; — waves and currents induced by maritime operations, i.e. vessel wake, berthing and mooring; — hydrodynamic actions induced by earthquakes; — ice-induced pressures and forces; — coastal structures where flood risk and/or erosion or sediment management is the dominant function. 1.2 Assumptions (1) The assumptions given in EN 1990 apply to this document. (2) In addition, it is assumed that actions from waves and currents on coastal structures are determined by personnel appropriately qualified and experienced in the following fields: a) physical coastal environment including physics of waves and currents, statistical properties and propagation of such; b) marine hydrodynamics, wave and current interaction with structures in general and wave and current actions on structures in the coastal zone including i) fixed structures, and ii) floating structures; c) advanced methods including probabilistic methodology and physical model testing.

 

1.1 Scope of EN 1991-4 (1) This document provides rules for calculating actions for the structural design of silos and tanks. NOTE 1 Silos are used for the storage of particulate solids. Tanks are used for the storage of liquids. NOTE 2 For limitations on rules for silos given in this document, see 1.3. NOTE 3 For limitations on rules for tanks given in this document, see 1.4. (2) This document includes some provisions for actions on silo and tank structures that are not only associated with the stored particulate solids or liquids (e.g. the effects of thermal differentials) but substantially affected by them. NOTE Liquid loads on tanks are very precisely defined. Many loads on silos are not known with great precision. This document provides guidance for many practical situations for which very limited certain knowledge is available, and the information is derived from the limited experimental and analytical information available, coupled with conclusions drawn from failure investigations. The information is not based on a sound statistical treatment of experimental data. (3) This document is intended for use with concrete, steel, aluminium, timber and FRP storage structures. NOTE FRP is the standard acronym for fibre reinforced polymer materials. (4) This document is also applicable for the structural assessment of existing silos and tanks, unless otherwise specified by the relevant authority or, if not specified, agreed between the relevant parties for the specific project. NOTE 1 Changes in filling or discharge arrangements, changes in the wall friction of inner surfaces, or in the use of the silo, including storage of different particulate solids, can be reasons for assessing existing silos. NOTE 2 Differentiation of the liquid stored can be a reason for assessing existing tanks. 1.2 Assumptions (1) The assumptions of EN 1990-1 apply. (2) This document is intended to be used in conjunction with EN 1990 1, with the other parts of EN 1991, EN 1992, EN 1993, EN 1995, EN 1997, EN 1998 and EN 1999 where relevant to the design of silos and tanks. 1.3 Limitations on silos 1.3.1 Geometrical limitations (1) The following geometrical limitations apply to the design rules for silos and silo batteries (see 3.2.59 and 3.2.60) covered by this document: - the silo planform cross-section shapes are limited to those shown in Figure 1.1c. NOTE 1 Further information concerning planform cross-section geometries is given in Clause 7. NOTE 2 For the determination of the effective diameter dc of the silo see Figure 1.1c; - the following dimensional limitations on the aspect ratio for free-standing single cell silos hc/dc, the overall height hb and the effective diameter dc apply (see Figure 1.1): hc/dc < 10 (1.1) hb < 100 m (1.2) dc < 60 m (1.3) NOTE 3 See Figure 1.1 for hc, dc and hb. - the structural transition lies in a single horizontal plane (see Figure 1.1a). [Figure 1.1 - Silo forms showing dimensions and pressure notation] (2) Only hoppers that are conical (i.e. axisymmetric), rectangular pyramidal with a/b = 1,5, wedge-shaped (i.e. with two vertical end walls on opposite sides) or oblique are covered by this document. Other hopper shapes and hoppers with internal structures require special considerations. (3) Silos with an oblique conical hopper used to achieve an eccentric outlet are covered by this document. (4) Silos with an oblique hopper are covered, but generally silos with a systematically non-symmetric geometry are not specifically covered by this document. These situations include a chisel hopper (i.e. a wedge hopper beneath a circular cylinder) and hoppers with an elongated outlet other than wedge shaped. 1.3.2 Limitations on the stored particulate solids (1) The following limitations on the stored particulate solids apply to the design rules for silos contained in this document: ...

 

This standard specifies the technical requirements for the control of environmental parameters in the whole process of spacecraft system level assembly, integration, and test. This standard is applicable to spacecraft system level assembly, integration, and test processes. This standard can serve as a reference for spacecrafts (e.g. commercial satellites) with more relaxed environmental requirements.

 

This document specifies a method for the determination of total organic carbon (TOC) in water samples containing suspended solids (SS) in the range of 10 mg/l to 500 mg/l. The method includes the determination of particulate organic carbon using combined ultrasonic and alkaline extraction (CUAL) pretreatment and quantification by the difference between total carbon (TC) and total inorganic carbon (TIC). Typical matrices include wastewater, stormwater, leachates, and surface water.

 

This document specifies test methods for the determination of strength, durability and stability of the structure of all types of seating without specific regard to end use, materials, design/construction or manufacturing process. This document does not apply to children’s highchairs, table mounted chairs and bath seats. Test methods for the assessment of ageing, degradation, ergonomics and electrical functions are not included. The test methods are not intended to assess the durability of upholstery materials.

 

This document specifies the communication interface between motion sensor and recording equipment. This includes mechanical, electrical and logical requirements.

 

This document specifies the reference software for carriage of haptics data as specified in ISO/IEC 23090-32. The information provided describes the reference software modules and the features that it supports. It also provides a description of how the reference software can be utilized. Finally, it also provides a description of conformance test vectors.

 

Warning The use of this International Standard may involve hazardous materials, operations and equipment. This International Standard does not purport to address all of the safety problems associated with its use. It is the responsibility of the user of this International Standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use. This International Standard gives specifications and operating instructions for glass capillary viscometers widely used for the determination of kinematic viscosity of petroleum products by the procedure described in ISO 3104. The calibration of these viscometers is also described. The types of viscometers described are modified Ostwald viscometers (Annex A), suspended-level viscometers (Annex B) and reverse-flow viscometers (Annex C). Other viscometers of the glass capillary type which are capable of measuring kinematic viscosity within the limits of precision given in ISO 3104 may be used.

 

Furthermore, this document, as amended by the corresponding amendment for Gaussian splat support, also specifies the use of the visual volumetric video-based coding mechanism for 3D scenes represented using Gaussian splat. In such representations, each point of the point cloud corresponds to a Gaussian primitive in 3D space and is described by a set of parameters, including at least its 3D position and additional attributes such as covariance, opacity and appearance coefficients. These parameters are mapped to geometry and attribute components within the V-PCC framework and coded using the same video-based mechanism. This enables efficient compression of Gaussian-splat-based scene representations and provides a coding solution suitable for Gaussian splat coding applications. 

 

The Kernel Modeling Language (KerML) is an application-independent modeling language with a well-grounded formal semantics for modeling existing or planned systems. The language includes general syntactic constructs for structuring models, such as relationships, annotations and namespaces; core semantic constructs that have semantics based on classification; and additional constructs for commonly needed modeling capabilities, such as associations and behaviors.

 

System models are expressed in KerML using a textual concrete syntax. This can be parsed to an abstract syntax representation, which is then given a semantic interpretation for the system being modeled. The semantics for the KerML core constructs is grounded in formal mathematical logic, providing a consistent basis for mathematical reasoning about KerML models. However, beyond this, the semantics of KerML constructs are specified by the relationship of user model elements to the KerML Semantic Library.

 

The Semantic Library models, also expressed in KerML, provide an ontological model of the meaning of KerML models. Indeed, all KerML models can be semantically expressed using solely core modeling constructs referencing the appropriate semantic concepts defined in the Semantic Library. KerML semantic constructs beyond the core are essentially just syntactic conveniences for reusing specific library concepts: structures for modeling objects, behaviors for modeling performances, associations for modeling links, etc.

 

Indeed, the full KerML language can be considered to be simply a syntactic extension of the core, which is semantically extended using library models. By intent, this approach can also be used to build on KerML to create more specific modeling languages. Application specific modeling languages can be built on KerML by extending the KerML abstract syntax, specializing its semantics, with concrete syntaxes similar to or entirely different from KerML's.

 

To support this, the KerML Semantic Library also includes additional library models beyond those directly providing semantics for KerML syntactic constructs, capturing typical semantic patterns (such as asynchronous transfers and state-based behavior) that can be reused by languages built on KerML. Specialized modeling languages can provide additional syntax for these libraries, tailored to their applications, with semantics based largely or entirely on the KerML libraries.

 

In this way, KerML can provide the kernel for a family of syntactically diverse but semantically integrated modeling languages.

 

The purpose of this standard is to specify the Systems Modeling Application Programming Interface (API) and Services that provide standard services to access, navigate, and operate on KerML-based models [KerML], and, in particular, SysML models [SysML]. The standard services facilitate interoperability both across SysML modeling environments and between SysML modeling environments and other engineering tools and enterprise services.

 

The Systems Modeling API and Services specifies the types and details of the requests that can be made and responses that can be received by software applications that are consuming the services to software applications that are providing the services.

 

The Systems Modeling API and Services specification includes the Platform Independent Model (PIM) - see Clause 7- and two Platform Specific Models (PSMs) - see Clause 8 : REST/HTTP PSM and OSLC PSM.

 

The purpose of this standard is to specify the Systems Modeling Language™ (SysML), to guide the implementation of conformant modeling tools, and to provide the basis for the development of material and other resources to train users in the application of SysML.

 

SysML is a general-purpose modeling language for modeling systems that is intended to facilitate a model-based systems engineering (MBSE) approach to engineer systems. It provides the capability to create and visualize models that represent many different aspects of a system. This includes representing the requirements, structure, and behavior of the system, and the specification of analysis cases and verification cases used to analyze and verify the system. The language is intended to support multiple systems engineering methods and practices. The specific methods and practices may impose additional constraints on how the language is used.

 

SysML is defined as an extension of the Kernel Modeling Language (KerML), which provides a common, domain independent language for building semantically rich and interoperable modeling languages. SysML also provides a capability to provide further language extensions. It is anticipated that SysML will be customized using this language extension mechanism to model more specialized domain-specific applications, such as automotive, aerospace, healthcare, and information systems, as well as discipline specific extensions such as safety and reliability.

 

Note. Definitions of system and systems engineering can be found in ISO/IEC 15288 Systems and Software Engineering – System Life Cycle Process.

 

This specification describes a transformation for a semantic translation from SysML v1 [SysMLv1] to SysML v2 [SysMLv2] in a precise way. (In this document, "SysML v1" refers to SysML v1.7, the last version of SysML prior to v2.0, and "SysML v2" refers to SysML v2.0, or whatever version corresponds to the current version of this specification.)

 

The main intent is to provide the rules on which automated conversions of SysML v1 models to the SysML v2 standard can be developed. In addition, this annex can be considered an educational document that provides useful information for people who would like to compare using SysML v2 and using SysML v1.

 

More sophisticated applications of this transformation can also be envisaged. For instance, a SysML v1 conformant tool could use this transformation to implement a limited subset of the SysML v2 API that will provide "SysMLv2-like" read-only access to its SysMLv1 models for external applications.

 

The Structured Patterns Metamodel Standard (SPMS) specification defines a common standard for the definition and description of patterns as used in architecting, designing, and implementing software systems, working with software faults or security issues, and any situation where a pattern is appropriately applied.

 

SPMS has three main goals:

1) Sharing of pattern definitions in repositories or catalogs, including human-oriented specifications and machine oriented formalisms for automated tool use.

2) Sharing of pattern instances – indicators of the existence of a pattern within a model – regardless of how that pattern was determined, with traceability back to the methodology, and traceability to the model artifacts that prove its existence. if applicable. These instances may come from manual assertion, or from the results of an automated tool.

3) A visual representation for pattern instances that augments existing modeling representations and supports both automated production of graphical diagrams, and informal “line and box” style human-generated sketching.

 

The first goal is supported by the Definitions package, which defines a metamodel for defining and storing pattern specifications, suitable for use in tooling and repositories.

 

The second goal is supported by the Observations package, which defines a metamodel for pattern instances. The classes defined here offer support for both human-oriented use cases (consulting, investigation, education) and machine oriented use cases (automated analysis tools, automated results analysis, etc.).

 

Both goals are further supported by the Relationships package, which augments the Definitions package with metadata appropriate for a repository or catalog of patterns. This metadata offers a set of semantic relationships between pattern definitions and instances, enhancing searchability and other use cases appropriate to the domain. Again, both human oriented and machine-oriented use cases are supported in this package.

 

The Formalisms package supports the first goal more thoroughly for automated tool use cases and research purposes. It provides a mechanism for linking to a variety of formal metamodels such as Object Constraint Language (OCL), Knowledge Domain Metamodel (KDM), Abstract Syntax Tree Metamodel (ASTM), or Pattern Hierarchical Object Relation Metamodel Language (PHORML), depending on the needs of the modeler and community.

 

The third goal is supported by the Pattern Instance Notation (PIN) metamodel, which defines a common metamodel for the graphical depiction of pattern instances. It relies on the abstractions defined in SPMS. PIN and the corresponding elements in SPMS are equivalent in their expressive power, and have a one-to-one coherence of features.

 

PIN was developed hand in hand with the Patterns package of SPMS and provides a simple and human-oriented approach for quickly depicting instances of patterns, how they work in concert, and how they are expressed in an implementation or further design document. Most notably, PIN can be used entirely by itself to illustrate pattern interactions independent of an implementation, or used as an annotation with the variety of other graphical notations, such as UML diagrams. 

 

This document specifies methodologies for measuring the performance of AI models for classification, regression, clustering and recommendation tasks.

 

This document specifies the test method and performance metrics to evaluate the behaviour of a vehicle equipped with rear cross traffic alerting system during several collision scenarios. These collisions occur during straight-line reverse manoeuvres when the vehicle under test (VUT) approaches other vehicles or traffic participants. This document is applicable to M1 category vehicles. NOTE Depending on accidentology, only a part of the scenarios can be used for an evaluation of performance.

 

This document presents a brief summary of the fundamental requirements and methods for data collection concerning large-scale outdoor fires at the levels of national policy, administrative regulations, and technical standards, covering Wildland-Urban Interface (WUI) fires, urban fires (including post-earthquake urban fires), and fires in informal settlements. Standards and studies around the world are to be consolidated into a standardized approach and an international ISO standard. This document establishes the standardized methodology for post-fire data collection to evaluate fire spread path, damage extent, and damage mechanisms following a large outdoor fire event. These also include data collection on human losses and property loss values. The standard does not address large-scale industrial fires. Applicable fire types include: a) Wildland-Urban Interface (WUI) fires b) Urban fires, including post-earthquake urban fires c) Informal settlement fires d) Other large outdoor fires This document defines the subject of data collection, essential data elements, collection procedures, and quality control. It does not prescribe methods for fire prevention, suppression operations, or recovery procedures themselves.

 

This document specifies ergonomic, technical and safety requirements for wall-mounted and free-standing writing boards, white projecting boards, interactive systems and interactive screens for use in rooms for educational and training purposes, e.g. classrooms, lecture theatres for schools, universities, etc. This document applies is applicable to units after installation. Safety depending on the structure of the building is not included, e.g. the strength of wall-mounted boards includes only the board and its parts. The wall and the wall attachment are not included. This document does not apply to technical aspects of connected hardware, such as computers, speakers, video cameras. Requirements concerning electrical safety are not included. Annex A (normative) Assessment scale for the ability to write – Five levels chalk scale Annex B (normative) Test methods and requirements for white projecting boards Annex C (informative) Additional test methods and requirements for white projecting boards Annex D (normative) Test methods and requirements for interactive systems Annex E (informative) Additional test methods and requirements for interactive systems Annex F (normative) Test methods and requirements for interactive screens Annex G (informative) Additional test methods and requirements for interactive screens Annex H (normative) Surface flatness test Annex I (informative) Vibration test