Toimialayhteisöt

 

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.

 

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

 

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.

 

This document establishes the core principles and specifications for enabling structured and semantically consistent information exchange between BIM and GIS. It provides a comprehensive framework for understanding, planning, and implementing information exchanges that span both the BIM domain and the GIS domain. This document provides a conceptual framework, built around eight perspectives on BIM-GIS information exchange: life cycle, process, product, data, exchange, actor, geospatial, and standards perspectives, how they shape, dictate, or constrain the structuring and execution of information exchanges, and the relationships between them and their application to specific use cases. It also addresses the following key elements: Requirements definition and hierarchy for BIM-GIS information exchanges Services enabling exchange and integration, transformation, query and analysis, and visualization and communication Functions supporting spatial registration and georeferencing, data harmonization, linking, analytical operations, and workflow management Resources including data and information types, formats, and their characteristics Repositories for centralized data management, translation and integration, and specialized storage It provides guidance on: Use case definition, services, and functions specification Application schema considerations addressing fundamental differences between BIM and GIS data structures Data resources management including objects, entities, and features Position and location management including georeferencing levels, metadata requirements, and implementation tasks Coordinate reference system selection and transformation parameters Georeferencing, including levels of georeferencing, metadata requirements and georeferencing tasks

 

This document provides guidelines for the data exchange between BIM and GIS through metadata. This document explains the role that metadata plays in facilitating data exchange within the framework of the standards referenced in ISO/DIS 23143-1, Clause 6.3 (Metadata resources). This document offers a perspective on leveraging metadata to ensure interoperability between BIM and GIS. It builds on the core principles established in ISO/DIS 23143-1 by presenting how metadata supports communication between the two domains, thereby facilitating seamless data exchange This document defines a framework for facilitating data exchange between Building Information Modelling (BIM) and Geographic Information Systems (GIS) through metadata-driven interoperability. It specifies methods for identifying and cross-mapping metadata elements in the GIS Metadata Schema (ISO 19115-1:2014 [2]), and for deriving BIM-side metadata from IDM Data Schema (ISO 29481-3:2022 [1]) to support semantic alignment and structured transformation between the two domains. ISO 29481-3:2022 [1] is used as a source to derive BIM-side metadata candidates for cross-mapping and is not treated as a metadata schema. The scope of this part includes: 1) Establishing metadata-based cross-mapping rules to support the semantic translation of information between BIM and GIS, including the use of BIM-side metadata candidates (derived from ISO 29481-3:2022 [1]) and GIS metadata elements (ISO 19115-1:2014 [2]); 2) Supporting bidirectional information requests and responses, where each domain (BIM or GIS) can serve as either information provider or consumer.

 

ISO 17208 -sarja kuvaa menettelyt, joilla mitataan tutkittavan aluksen säteilemää vedenalaista ääntä sekä lasketaan mittaustuloksista äänilähdettä kuvaavia suureita, kuten lähdetaso ja säteillyn melun taso.Standardeissa ISO 17208-1...3 oletetaan, että tutkittava alus osallistuu mittauksiin yhteistyössä suorittamalla useita ajoja määrättyä reittiä pitkin mittausjärjestelmän ohi ennalta määritellyllä nopeudella ja koneistokokoonpanolla. Ohi kulkevien alusten säteilemän äänen opportunistiset mittaukset eivät kuulu näiden kolmen standardin soveltamisalaan.ISO 17208 -standardisarjan osa 1[1] esittää menettelyn aluksen vedenalaisen äänen määrittämiseksi sen säteillyn melun tasona. Tämä lasketaan aluksen kaukokentässä, sivukulmassa mitatusta äänenpainetasosta (SPL), joka skaalataan lähimmän ohitusetäisyyden (CPA) mukaan ja raportoidaan desidekadikaistoin. Säteillyn melun tason käyttötarkoituksena on osoittaa sopimusvaatimusten tai kriteerien täyttyminen, mahdollistaa eri alusten vertailu, tukea alusten akustisen tunnuskuvan säännöllistä arviointia sekä palvella tutkimus- ja kehitystyötä.ISO 17208-2[1] määrittelee menetelmät, joilla standardin ISO 17208-1 mukaisesti saaduista säteillyn melun tason arvoista lasketaan määritellyllä nimellisellä lähdesyvyydellä sijaitsevan ekvivalentin monopoliäänilähteen lähdetaso. Lähdetason ja siihen liittyvän nimellisen lähdesyvyyden käyttötarkoituksena on mahdollistaa kaukokentän äänen etenemisen ennustaminen esimerkiksi ympäristövaikutustutkimuksia tai vedenalaisten melukarttojen laatimista varten.ISO 17208-1 ja ISO 17208-2[1] soveltuvat syvän veden mittauksiin, joissa veden syvyys on suurempi kuin arvoista 150 m ja 1,5 kertaa aluksen kokonaispituus suurempi. Osan 3 mukaisten mittausten sallitut veden syvyydet ja ympäristöolosuhteet on kuvattu kohdassa 4.5.Tässä asiakirjassa määritellään menettelyt tutkittavan aluksen säteilemän vedenalaisen äänen mittaamiseksi matalassa vedessä. Lisäksi siinä määritellään menetelmät, joilla äänenpainemittauksista lasketaan lähdetaso siihen liittyvine nimellisine lähdesyvyyksineen ottaen huomioon ne ilmiöt, jotka hallitsevat äänen etenemistä matalassa vedessä. Nämä laskentamenetelmät on kuvattu kohdassa 7. Kun lähdetaso on laskettu, siitä ja lähdesyvyydestä voidaan johtaa myös muita mittareita. Kohdassa 7.3 esitetään menettely sellaisen säteillyn melun tason laskemiseksi, joka olisi mitattu syvässä vedessä standardin ISO 17208-1 mukaisesti samalla aluksella ja samoissa käyttöolosuhteissa.

Tämä dokumentti on DRM-suojattu. DRM-suojattujen tiedostojen lukemiseen on välttämätöntä asentaa koneelle ilmainen FileOpen-liitännäinen (FileOpen plug-in). Jos sinulla ei ole oikeutta asentaa ohjelmia omalle päätelaitteellesi, ota yhteyttä oman organisaatiosi IT-tukeen. FileOpen liitännäisen saat ladattua osoitteessa http://plugin.fileopen.com/all.aspx. Onnistuneen asennuksen jälkeen avaa standardiehdotus Acrobat Readerilla, jotta lisäosa toimii oikein.