Toimialayhteisöt

 

This document defines events and associated information elements that are used for tracking and tracing of all types of cargo in the maritime domain. This does not include passengers or crew. The document also defines information exchanges and information elements based on the ISO 28005 framework. The document is an elaboration of the UNECE “Business Requirements Specification for Integrated Track and Trace for Multi-Modal Transportation” with its inherent assumptions, which are: All transportation is related to a trade transaction between a seller and a buyer of goods that results in one or more shipments. Therefore, all tracking and tracing and events described in this document ultimately also “link” with these shipments. There is no present need for additional data identifiers to facilitate multi-modal tracking and tracing of trade shipments or the linked transportation in scope for this document. See below this bullet list. Identifiers for trade items, cargo, their packaging or container, or means of transport will support multi-modal tracking and tracing, if the identifiers are globally unique. Linkages can be made between the different identifiers using various existing technologies. The model supports tracking and tracing using various existing technologies by using the most relevant waypoints for the transport journey (as agreed among stakeholders). Standardized exchange processes may be used, without the need to create new class diagrams or new message structures. The operational scope covers the voyage of the ship, via the terminal, up to and including the gate-in event or gate-out event in the terminal. Gate-in and gate-out events include transfers between the maritime terminal and hinterland modes of transport such as road vehicles, feeder ships, inland waterway barges or rail wagons. The document aims to cover all kinds of cargoes carried on maritime ships. Cargo moves through ports in two main directions: Coming in from sea to be transported to destinations in the hinterland of the port. Coming in from the hinterland to be transported to overseas destinations on maritime ships. For the purposes of this document, we will ignore the transshipment scenario where the cargo comes in on maritime ships and also leaves on maritime ships from and to destinations that are not considered part of the hinterland of the port. The supply chain events that occur outside the boundaries of gate in and gate out mentioned above are not in scope for this document. It is recognised that the transport-related operations covered in the scope of this document are an integral part of the end-to-end supply chain between seller and buyer. Therefore, the requirements outlined in this document will follow standards and "best practices" already in use in the supply chain. This is also driven by the fact that there are critical hand-overs between the wider supply chain and the operations in scope for this document at the gate in and gate out processes that require unambiguous exchange of information related to the critical events in those processes.

 

This document provides guidance for data collection and validation for the calculation of the carbon footprint for lithium products. This document encourages disclosure of the databases, software, yields, distribution methods and data quality rating used in the calculation of greenhouse gas (GHG) emissions when producing lithium products from various lithium resources and produced by various processes, including its distribution, in order to verify the calculated values of GHG emissions. This document is not intended for the disclosure of GHG emissions for individual stages of the product manufacturing process.

 

RISC-V (pronounced “risk-five”) is a new instruction-set architecture (ISA) that was originally designed to support computer architecture research and education, but which we now hope will also become a standard free and open architecture for industry implementations. Our goals in defining RISC-V include:

 

• Acompletely open ISA that is freely available to academia and industry. • Areal ISA suitable for direct native hardware implementation, not just simulation or binary translation.

• An ISA that avoids “over-architecting” for a particular microarchitecture style (e.g., mi crocoded, in-order, decoupled, out-of-order) or implementation technology (e.g., full-custom, ASIC, FPGA), but which allows efficient implementation in any of these.

• An ISA separated into a small base integer ISA, usable by itself as a base for customized accelerators or for educational purposes, and optional standard extensions, to support general purpose software development.

• Support for the revised 2008 IEEE-754 floating-point standard [5]. • An ISA supporting extensive ISA extensions and specialized variants. • Both 32-bit and 64-bit address space variants for applications, operating system kernels, and hardware implementations.

• An ISA with support for highly-parallel multicore or manycore implementations, including heterogeneous multiprocessors.

• Optional variable-length instructions to both expand available instruction encoding space and to support an optional dense instruction encoding for improved performance, static code size, and energy efficiency.

• An ISA that simplifies experiments with new privileged architecture designs.

 

The RISC-V ISA is defined avoiding implementation details as much as possible (although com mentary is included on implementation-driven decisions) and should be read as the software-visible interface to a wide variety of implementations rather than as the design of a particular hardware artifact. The RISC-V manual is structured in two volumes. This volume covers the design of the base unprivileged instructions, including optional unprivileged ISA extensions. Unprivileged instructions are those that are generally usable in all privilege modes in all privileged architectures, though behavior might vary depending on privilege mode and privilege architecture. The second volume provides the design of the first (“classic”) privileged architecture. The manuals use IEC 80000-13:2008 conventions, with a byte of 8 bits.

 

 

This document describes the RISC-V privileged architecture, which covers all aspects of RISC V systems beyond the unprivileged ISA, including privileged instructions as well as additional functionality required for running operating systems and attaching external devices.

 

ISO 21439:2009 määrittelee menetelmät vedessä tai kudoksessa esiintyvien absorboituneen annoksen jakaumien määrittämiseksi ennen silmäkasvainten hoitoon tarkoitetun beetasäteilyn sekä suonensisäisen brakyterapian käyttöä. Standardissa esitetään suosituksia beetasäteilylähteiden kalibrointiin, dosimetrisiin mittauksiin, annoslaskentaan, dosimetriseen laadunvarmistukseen sekä beetasäteilyyn perustuvan brakyterapian hoitosuunnitteluun. Lisäksi annetaan ohjeita veteen absorboituneen annoksen epävarmuuden arviointiin. ISO 21439:2009 soveltuu "suljettuihin" radioaktiivisiin lähteisiin, kuten tasomaisiin ja koveriin pintalähteisiin, yksittäisistä siemenlähteistä muodostuviin lähdeketjuihin, viivalähteisiin sekä kuori- ja tilavuuslähteisiin, joissa ainoastaan emittoituvalla beetasäteilyllä on hoidollista merkitystä.Standardissa kuvattujen kliinisen dosimetrian menettelyjen standardointi muodostaa perustan beetasäteilyyn perustuvan brakyterapian luotettavalle käytölle. Standardissa esitetyt erityiset dosimetriset menetelmät soveltuvat silmäsairauksien parantavaan hoitoon tarkoitettuihin lähteisiin, suonensisäiseen brakyterapiaan, verisuonen uudelleenahtauman ehkäisyyn sekä muihin beetasäteilyä hyödyntäviin kliinisiin sovelluksiin.ISO 21439:2009 on tarkoitettu organisaatioille, jotka haluavat ottaa käyttöön dosimetrian vertailumenetelmiä ja pyrkivät täyttämään kliiniset vaatimukset siten, että potilaalle annettavan säteilyannoksen epävarmuus pysyy riittävän pienenä. Standardi ei kuitenkaan sulje pois mahdollisuutta käyttää muitakin menetelmiä, joilla voidaan saavuttaa sama tai jopa pienempi mittausepävarmuus.

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.