Toimialayhteisöt

 

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 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 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.

 

The scope of this project is to provide guidelines for information exchange between BIM and GIS. As part of a series of proposed international standards for BIM-GIS information exchange, Part 01: core principles and specifications will provide guidance on how to use existing standards adequately so that each domain can provide and request information properly. This work needs to be sufficiently broad by integrating ISO Standards and the latest developments from OGC and buildingSMART. The work will also cover the core principles of working with BIM and GIS, namely ensuring the Georeferencing of BIM models.

 

The scope of this project is to provide guidelines for information exchange between BIM and GIS. As part of a series of proposed international standards for BIM-GIS information exchange, Part 02: Facilitating data exchange through metadata will aim to solve metadata issues to support bidirectional GIS/BIM information exchange and suggest technical requirements based on use case scenarios. Metadata give great opportunities to find, evaluate and manage relevant information for the bidirectional information exchange. To ensure the interoperability between GIS and BIM information models, it is critical for one domain experts to understand the metadata generated from the other domain and vice versa. The work will review existing methodologies and research with regard to bidirectional GIS/BIM information exchange, especially in terms of metadata and item registration. It will provide a use case scenario to give a certain context of bidirectional exchange of metadata. The use case will also provide the context within which the interaction that needs to be taken place between GIS and BIM model experts. With the use of the use case scenario, the process of properly generating metadata for each domain to ensure the bidirectional exchange can be identified. It will then list the technical requirements to support the process and provide a guideline to follow.

 

The general scope of the core product category rules (PCR) is given in EN 15804:2012+A2:2019, Clause 1. This PCR is primarily intended for the creation of cradle-to-gate EPDs or the declaration of performance in relation to the environmental sustainability of cement, building lime and other hydraulic binders. In particular, “cement” refers to — common cements according to EN 197 1 [1], — very low heat special cements according to EN 14216 [6], — calcium aluminate cement according to EN 14647 [7], — supersulfated cement according to EN 15743 [9]; “building lime” refers to — building lime according to EN 459 1 [3]; “other hydraulic binders” refers to — masonry cement according to EN 413 1 [2], — hydraulic road binders according to EN 13282 [5], — hydraulic binder for non-structural applications according to EN 15368 [8]. In other respects, the scope is as in EN 15804:2012+A2:2019.

 

This document specifies conditions for the determination of 90Sr and 89Sr activity concentration in samples of environmental water using liquid scintillation counting (LSC) or proportional counting (PC). The method is applicable to test samples of drinking water, rainwater, surface and ground water, marine water, as well as cooling water, industrial water, domestic, and industrial wastewater after proper sampling and handling, and test sample preparation. Filtration of the test sample and a chemical separation are required to separate and purify strontium from a test portion of the sample. The detection limit depends on the sample volume, the instrument used, the sample count time, the background count rate, the detection efficiency and the chemical yield. The method described in this document, using currently available LSC counters, has a detection limit of approximately 10 mBq l-1 and 2 mBq l-1 for 89Sr and 90Sr, respectively, which is lower than the WHO criteria for safe consumption of drinking water (100 Bq·l-1 for 89Sr and 10 Bq·l-1 for 90Sr)[3]. These values can be achieved with a counting time of 1 000 min for a sample volume of 2 l. The methods described in this document are applicable in the event of an emergency situation. When fallout occurs following a nuclear accident, the contribution of 89Sr to the total amount of radioactive strontium is not negligible. This document provides test methods to determine the activity concentration of 90Sr in presence of 89Sr. The analysis of 90Sr and 89Sr adsorbed to suspended matter is not covered by this method. It is the user’s responsibility to ensure the validity of this test method selected for the water samples tested.

 

This document specifies an inspection procedure to be used by the purchaser where no prior agreement exists. It also specifies a reference acceptance procedure for acceptance or rejection of an inspection lot, when no agreement can be reached between the purchaser and the supplier, or where conformance to specification is disputed. It applies to inspection lots of bolts, screws, studs, nuts, pins, washers, rivets and other related fasteners. This document applies to fasteners not intended for high volume machine assembly, special-purpose applications or specially engineered applications requiring more advanced in-process control and lot traceability. For in-process control or final inspection by the manufacture and sorting, see ISO 16426.