CEN

The purpose is to define the tests to be performed in order to evaluate the performances of road applications’ GNSS-based positioning terminal (GBPT). To fully define the tests, this task will address the test strategy, the facilities to be used, the test scenarios (e.g. environments and characteristics, which shall allow the comparison of different tests), and the test procedures. The defined tests and process will be validated by performing various in-field tests. The defined tests focus essentially on accuracy, integrity and availability as required in the statement of work included in the invitation to tender. This document will benefit to: - The consolidation of EN 16803-1: "Definitions and system engineering procedures for the establishment and assessment of performances" - The elaboration of EN 16803-2: "Assessment of basic performances of GNSS-based positioning terminals" - The elaboration of EN 16803-3: "Assessment of security performances of GNSS based positioning terminals".

This document specifies a set of representational primitives and semantic relations needed for an unambiguous representation of explicit time-related expressions in health informatics. This document does not introduce or force a specific ontology of time, nor does it force the use of a fixed representation scheme for such an ontology. Rather this document provides a set of principles for syntactic and semantic representation that allow the comparability of specific ontologies on time and the exchange of time-related information that is expressed explicitly. This document applies to both the representation of actual phenomena occurring in the real world (e.g. registrations in medical records) and to the description of concepts (e.g. medical knowledge bases). This document is applicable to a) developers of medical information systems where there might be a need for explicit time-related concepts for internal organization (e.g. temporal databases, temporal reasoning systems), b) information modellers or knowledge engineers building models for the systems mentioned in a), c) experts involved in the development of semantic standards on precise subdomains in health care where time-related information needs to be covered, (e.g. in the study of pathochronology, i.e. the discipline dealing with the time course of specific diseases), and d) developers of interchange formats for messages in which time-related information is embedded. This document is not intended to be used directly for — representing what is true in time, — reasoning about time, or — representation of metrological time.

Prepare a standard for the lower layers for uni and bi-directional meters data exchange by radio frequency communication. (see resolutions 2& 3/1999).

Produce and maintain standards for meter data exchange protocols, for use over short range wireless networks with meshing functionality. Note: Work will be based on existing ZigBee specifications.

To define an ISO/OSI application layer for communication systems for and remote reading of all meters within the scope of TC 294 to fullfill the user requirements as defined by WG 1 (as one part of the standards). To define and maintain a glossary of terms (as one part of the standards).

Maintain EN 1434-3, preparing a draft revision, taking into account: - to improve the reference to the ISO/OSI physical- and linklayer; - to enable CEN/TC 294 DLMS-Protocol to be used on the physical- and linklayer of EN 1434-3; - to ensure consistency with the work done on other WGs of CEN/TC 294; - to prepare the draft for enquiry as soon as possible (see resolution 3/1998)

This document gives guidelines for a uniform framework, transversal with respect to the different robot categories and limited to those robots and robotic applications characterized by human-robot collaboration, for the development and/or use of testing procedures, applicable to different robot categories and use scenarios. This document is informative and is not aimed at substituting or simplifying verification and/or validation procedures required by standards. The objectives of this document are the following: — define an approach for the development and use of procedures for testing safety in human-robot collaboration at a system level, based on safety-relevant human-robot collaboration skills and limited to the mechanical hazards; — define a comprehensive list of application-driven, technology-invariant safety-relevant human-robot collaboration skills valid across different domains; — provide a template for system-level validation protocols; — by way of example, present two system-level validation protocols, applicable to multiple domains. This document does not apply to the following devices, systems and applications: autonomous vehicles for the transportation of persons, drones, rescue robots (including ground, marine and aerial vehicles), surgical robots in relation to the body of the patient, passive wearable devices, external limb prostheses. NOTE 1 This document aims at providing harmonization in the compilation of structured testing procedures, to supplement safety validation of specific robot applications, building, where possible, on test methods provided in the relevant standards. It does not propose any safety requirement, nor is it intended to provide alternatives for or simplification of the relevant standards for each robot category. Users of this document are expected to be proficient in directives, regulations and standards applicable for the specific robot system and application. An overview of robot categorization is provided in A.1. NOTE 2 This document does not address “functional safety” (e.g. the performance level of safety-related parts of control systems), nor criteria for its validation and verification.

Defines electrical and related mechanical safety requirements for design and construction of the electrical installation in battery powered industrial trucks hereinafter referred to as trucks, with nominal voltages of the truck system up to 240 V.

This document specifies the electrical requirements for the design and construction of the electrical installation in self-propelled industrial trucks that are within the scope of ISO 5053-1, except variable reach trucks as defined in ISO 5053-1:2015, 3.21 and 3.22, straddle carriers as defined in ISO 5053-1:2015, 3.18 and 3.19, and specific functions, parts and/or systems utilized for the automatic operation of driverless industrial trucks as defined in ISO 5053-1:2015, 3.32.

Pertains to all trucks and their systems except: a) trucks solely guided by mechanical means (rails, guides, etc); b) trucks operating in areas open to persons unaware of the hazards.

ISO 15118-2:2014 specifies the communication between battery electric vehicles (BEV) or plug-in hybrid electric vehicles (PHEV) and the Electric Vehicle Supply Equipment. The application layer message set defined in ISO 15118-2:2014 is designed to support the energy transfer from an EVSE to an EV. ISO 15118-1 contains additional use case elements describing the bidirectional energy transfer. The implementation of these use cases requires enhancements of the application layer message set defined herein. The purpose of ISO 15118-2:2014 is to detail the communication between an EV (BEV or a PHEV) and an EVSE. Aspects are specified to detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication between EVCC and SECC. ISO 15118-2:2014 defines messages, data model, XML/EXI based data representation format, usage of V2GTP, TLS, TCP and IPv6. In addition, it describes how data link layer services can be accessed from a layer 3 perspective. The Data Link Layer and Physical Layer functionality is described in ISO 15118-3.