Sociologi. Service. Företagsorganisation och företagsledning. Administration. Transport Administration

This Technical Specification specifies the TPEG application Traffic Flow and Prediction (TFP). It has been specifically designed to provide information to a variety of receivers using different channels, including in the first instance Digital Broadcasting and Internet technologies. Traffic flow and prediction messages are intended for in-car applications and may be as well presented directly to the user by textual, voiced and graphically output devices.

TFP is status oriented, i.e. the transmitted information updates continuously the receiver's knowledge for a dedicated road network. In particular the traffic states are delivered any time and for all road sections of the network, even when there are no abnormal traffic situations.

Generally, TFP focuses on the following requirements:

— provide dynamic navigation systems with up-to-date traffic state information,

— ensure travel safety for the driver,

— enable the calculation of alternative routes,

— avoid delays (e.g. traffic jams),

— lower traffic load on over-saturated parts of the network,

— keep driver informed about current and upcoming traffic,

— compact and efficient coding of the traffic information.

TPEG applications are modelled in UML to provide an application description that is independent of a physical format representation. By separating semantics from application description, applications can easily be developed at a functional level. Different physical format representations can be generated following a well defined set of rules on how to convert UML classes to different physical formats.

This Technical Specification specifies the rules for converting UML models of TPEG application to the TPEG binary format. It contains the binary format definition of the abstract data types defined in ISO/TS 21219-2. Rules for converting compound data types are also defined.

This Technical Specification specifies the rules for converting TPEG application UML models to the tpegML format description. It contains the XML format definition of the abstract data types defined in ISO/TS 21219-2. Rules for converting compound data types are also defined.

This Technical Specification establishes a method of conveying data for a wide range of applications that require the efficient transmission of point to multi-point data over potentially unreliable broadcast channels. It is also suitable for point-to-point and multicast applications and may easily be encapsulated in Internet Protocol.

This Technical Specification describes the basic capabilities of the generation 2 TPEG (TPEG2) for providing a multiplex of TPEG Services and applications. Together with the definitions of the general TPEG UML modelling rules and the particular physical TPEG representations for TPEG- binary streams (TISA: TPEG UML Conversion Rules) and tpegML files (TISA Specification: TPEG UML Conversion Rules), it replaces the former documents TPEG-INV and TPEG-SSF.

This Technical Specification adds a basic toolkit definition to the ISO 21219 series specifying the Message Management Container (MMC), which is used by all TPEG applications to provide information about the handling of messages on the TPEG client side. The MMC holds administrative information allowing a decoder to handle the message appropriately. This information is not aimed at the end user. The MMC is a toolkit and not a stand-alone application but is included by TPEG applications.

This Technical Specification specifies rules for the creation and extending of TPEG application UML models. The rules are intended to ensure that TPEG application UML models can be interpreted unambiguously for conversion to physical format representations. TPEG application UML models that are defined according to these rules may be used for automatic generation of TPEG standards and for automatic generation of TPEG application physical format descriptions.

This Technical Specification also specifies the preferred structure of TPEG application specifications.

The TPEG abstract data types and the set of TPEG tables of common use are specified in the annexes.

This document provides guidance to organizations on implementing ISO 44001 (see Figure 3) in order to achieve successful collaborative business relationships, as well as helping organizations use and implement the framework specification effectively. This document will explain what is intended by each requirement of ISO 44001, why each is important, and recommend approaches to be taken for practical implementation. How to meet the requirements is individually evaluated and applied in the context of each organization.

This document is applicable to any organization.

This document provides practical guidance and examples for establishing, implementing, maintaining

and improving an energy management system (EnMS) in accordance with the systematic approach of

ISO 50001:2018. The guidance in this Document is applicable to any organization.

This document does not provide guidance on how to develop an integrated management system.

While the guidance in this document is consistent with the ISO 50001:2018 EnMS model, it does not

provide interpretations of the requirements of ISO 50001:2018.