CEN

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

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.

This standard specifies built-in safety measures aimed at preventing unexpected machine start-up (see 3.2) toallow safe human interventions in danger zones (see Annex A).This standard applies to unexpected start-up from all types of energy source, i.e.: Power supply, e.g. electrical, hydraulic, pneumatic.  Stored energy due to, e.g., gravity, compressed springs.  External influences, e.g. from wind;

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.

This document, as a basis for the other parts of the ISO 15118 series, specifies terms and definitions, general requirements and use cases for conductive and wireless HLC between the EVCC and the SECC. This document is applicable to HLC involved in conductive and wireless power transfer technologies in the context of manual or automatic connection devices. This document is also applicable to energy transfer either from EV supply equipment to charge the EV battery or from EV battery to EV supply equipment in order to supply energy to home, to loads or to the grid. This document provides a general overview and a common understanding of aspects influencing identification, association, charge or discharge control and optimisation, payment, load levelling, cybersecurity and privacy. It offers an interoperable EV-EV supply equipment interface to all e-mobility actors beyond SECC. The ISO 15118 series does not specify the vehicle internal communication between battery and other internal equipment (beside some dedicated message elements related to the energy transfer).

This Technical Report aims to help citizens to understand the relevance of using electronic signature within their day-to-day lives. It also explains the legal and the technical backgrounds of electronic signatures. This document gives guidance on the use of electronic signatures and addresses typical practical questions the citizen may have on how to proceed to electronically sign, where to find the suitable applications and material.

The present Technical Report provides guidance on the selection of standards and options for the signature/seal creation and other related devices (area 2) as identified in the framework for standardization of signatures: overview ETSI/TR 119 000 [16]. The present Technical Report describes the Business Scoping Parameters relevant to this area (see Clause 5) and how the relevant standards and options for this area can be identified given the Business Scoping Parameters (Clause 6). The target audience of this document includes: - business managers who potentially require support from electronic signatures/seals in their business and will find here an explanation of how electronic signatures/seals standards can be used to meet their business needs; - application architects who will find here material that will guide them throughout the process of designing a system that fully and properly satisfies all the business and legal/regulatory requirements specific to electronic signatures/seals, and will gain a better understanding on how to select the appropriate standards to be implemented and/or used; - developers of the systems who will find in this document an understanding of the reasons that lead the systems to be designed as they were, as well as a proper knowledge of the standards that exist in the field and that they need to know in detail for a proper development.