• Amendment
    16 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    10 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines a technology independent model for a set of abstract services that is
located above the application layer of the OSI model, and that is used for exchanging
transaction messages based on the transaction models defined in IEC 62264-5. The model,
which is called the Messaging Service Model (MSM), is intended for interoperability between
manufacturing operations domain applications and applications in other domains.
NOTE It is recognized that other sets of services not defined in accordance with this document are possible for the
exchange of MOM information and are not deemed invalid as a result of this document.

  • Standard
    53 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    53 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document:
— Specifies clinical information models (CIMs) as health and care concepts that can be used to define
and to structure information for various purposes in health care, also enabling information reuse;
— Describes requirements for CIMs content, structure and context and specification of their
data elements, data element relationships, meta-data and versioning, and provides guidance and
examples;
— Specifies key characteristics of CIMs used in conceptual and logical analysis for use cases such
as (reference) architectures, information layers, EHR and PHR systems, interoperability, systems
integration in the health domain, and secondary use of data including for public health reporting;
— Defines a Quality Management System (QMS) for a systematic and effective governance, quality
management, and measurement of CIMs through their lifecycle of development, testing, distribution,
application and maintenance;
— Provides principles for the transformation and application of clinical information models through
the wide variation of health information technology.
This document excludes:
— Requirements on the content or application of any particular clinical information model or clinical
information modelling methodology;
— Specific applications of clinical information models such as for dynamic modelling of workflow;
— Specifications for modelling entire domains or aggregates of many CIMs such as complete assessment
documents or discharge summaries. It does not specify CIMs compositions;
— Specification of how to involve specific clinicians, how to carry out governance including information
governance, or how to ensure patient safety.

  • Standard
    88 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    85 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The EN 16157 series specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
The EN 16157 series is applicable to:
-   traffic and travel information which is of relevance to road networks (non-urban and urban),
-   public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service),
-   traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This series establishes specifications for data exchange between any two instances of the following actors:
-   Traffic Information Centres (TICs),
-   Traffic Control Centres (TCCs),
—   Service Providers (SPs).
Use of this series can be applicable for use by other actors.
This series covers, at least, the following types of informational content:
-   road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment,
-   operator initiated actions,
-   road traffic measurement data, status data, and travel time data,
-   travel information relevant to road users, including weather and environmental information,
-   road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies details of infrastructure for vehicle energy supply. The provided data model is separated into two publications for static and dynamic information. The static information regarding the infrastructure is not subject to frequent changes, whereas the dynamic part offers the ability to provide highly up-to-date information. The static part covers all relevant information on vehicle energy infrastructure, e.g. sites, stations and refill points for electric vehicles as well as petrol, gasoline or gas-based refuelling for vehicles. In terms of dynamic information, the availability of the infrastructure, possible faults and a price indication are covered.

  • Technical specification
    79 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines and specifies component facets supporting the exchange and shared usage of
data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the data content, structure and
relationships necessary and the communications specifications, in such a way that they are independent
from any defined technical platform.
This document establishes specifications for data exchange between any two instances of the following
actors:
— Traffic information centres (TICs);
— Traffic control centres/Traffic management centres (TCCs/TMCs);
— Service providers (SPs).
This document can also be applied for use by other actors, e.g. car park operators.
This document includes the following types of information:
— use cases and associated requirements, and features relative to different exchange situations;
— different functional exchange profiles;
— abstract elements for protocols;
— data model for exchange (informational structures, relationships, roles, attributes and associated
data types required).
In order to set up a new technical exchange framework, it is necessary to associate one functional
exchange profile with a technical platform providing an interoperability domain where plug-and-play
interoperability at a technical level can be expected. The definition of such interoperability domains
is out of scope of this document but can be found in other International Standards or Technical
Specifications (e.g. the ISO 14827 series).
This document is restricted to data exchange. Definition of payload content models is out of the scope
of this document.

  • Technical specification
    151 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Technical Report refers to EN 15232-1, Energy performance of buildings - Part 1: Impact of Building Automation, Controls and Building Management - Modules M10-4,5,6,7,8,9,10.
It contains information to support the correct understanding, use and national adaption of standard EN 15232-1.
This technical report does not contain any normative provision.

  • Technical report
    53 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    50 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This European Standard specifies:
-   a structured list of control, building automation and technical building management functions which contribute to the energy performance of buildings; functions have been categorized and structured according to building disciplines and so called Building automation and control (BAC);
-   a method to define minimum requirements or any specification regarding the control, building automation and technical building management functions contributing to energy efficiency of a building to be implemented in building of different complexities;
-   a factor based method to get a first estimation of the effect of these functions on typical buildings types and use profiles;
-   detailed methods to assess the effect of these functions on a given building.
Table 1 shows the relative position of this standard within the set of EPB standards in the context of the modular structure as set out in EN ISO 52000 1.
NOTE 1   In CEN ISO/TR 52000 2 the same table can be found, with, for each module, the numbers of the relevant EPB standards and accompanying technical reports that are published or in preparation.
NOTE 2   The modules represent EPB standards, although one EPB standard may cover more than one module and one module may be covered by more than one EPB standard, for instance a simplified and a detailed method respectively.

  • Standard
    103 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    94 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies technical characteristics and methods of measurements for Transport and Traffic
Telematics (TTT) systems intended to be operated as Road Side Units (RSU) with the following characteristics:
• with a Radio Frequency (RF) connection and specified antenna or with an integral antenna;
• used for data transmission only;
• operating in the 5 795 MHz to 5 815 MHz frequency band (see also table 1).
NOTE: The relationship between the present document and essential requirements of article 3.2 of Directive
2014/53/EU [i.3] is given in annex A.

  • Standard
    46 pages
    English language
    sale 15% off
  • Standard
    46 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    46 pages
    English language
    sale 15% off
  • Draft
    46 pages
    English language
    sale 10% off
    e-Library read for
    1 day

1.1 Purpose
This document defines the LIFE CYCLE requirements for development and maintenance of HEALTH SOFTWARE needed to support conformity to IEC 62443-4-1 - taking the specific needs for HEALTH SOFTWARE into account. The set of PROCESSES, ACTIVITIES, and TASKS described in this document establishes a common framework for secure HEALTH SOFTWARE LIFE CYCLE PROCESSES.
[Fig. 1]
The purpose is to increase the information SECURITY of HEALTH SOFTWARE by establishing certain ACTIVITIES and TASKS in the HEALTH SOFTWARE LIFE CYCLE PROCESSES and also by increasing the SECURITY of SOFTWARE LIFE CYCLE PROCESSES themselves.
It is important to maintain an appropriate balance of the key properties SAFETY, effectiveness and SECURITY as discussed in IEC 81001-1.
This document excludes specification of ACCOMPANYING DOCUMENTATION contents.
1.2 Field of application
This document applies to the development and maintenance of HEALTH SOFTWARE by a MANUFACTURER, but recognizes the critical importance of bi-lateral communication with organizations (e.g. HDOs) who have SECURITY responsibilities for the HEALTH SOFTWARE and the systems it is incorporated into, once the software has been developed and released. The IEC/ISO 81001-5 series of standards (for which this is part 1, is therefore being designed to include future parts addressing SECURITY that apply to the implementation, operations and use phases of the LIFE CYCLE for organizations such as HDOs.
Medical device software is a subset of HEALTH SOFTWARE. Therefore, this document applies to:
− Software as part of a medical device;
− Software as part of hardware specifically intended for health use;
− Software as a medical device (SaMD); and
− Software-only PRODUCT for other health use.
Note: In this document, the scope of software considered part of the LIFE CYCLE ACTIVITIES for secure HEALTH SOFTWARE is larger and includes more software (drivers, platforms, operating systems) than for SAFETY, because for SECURITY the focus will be on any use including foreseeable unauthorized access rather than just the INTENDED USE.
[Fig. 2]
1.3 Conformance
HEALTH SOFTWARE conformance with this document is defined as implementing all of the PROCESSES, ACTIVITIES, and TASKS identified in the normative parts of this document - with the exception of Annex F.
Conformance of TRANSITIONAL HEALTH SOFTWARE with Annex F of this document is defined as only implementing the PROCESSES, ACTIVITIES, and TASKS identified in Annex F of this document.
Conformance is determined by inspection and establishing traceability of the PROCESSES, ACTIVITIES and TASKS required.
The quality management system may be implemented according to ISO 13485 or other equivalent quality management system standards.
IEC 62304 specifies ACTIVITIES, based on the software SAFETY classification. The required ACTIVITIES are indicated in the normative text of IEC 62304 as "[Class A, B, C]", "[Class B, C]" or "[Class C]", indicating that they are required selectively depending on the classification of the software to which they apply. The requirements in this document have a special focus on information SECURITY and therefore do not follow the concept of SAFETY classes. For conformity to this document the selection of ACTIVITIES is independent of SAFETY classes.
Implementing the PROCESSES, ACTIVITIES and TASKS specified in this document is sufficient to implement the PROCESS requirements of IEC 62443-4-1. MANUFACTURERS may implement the specifications for Annex E in order to achieve full conformity to IEC 62443-4-1.
This document requires establishing one or more PROCESSES that comprise of identified ACTIVITIES. The LIFE CYCLE PROCESSES shall implement these ACTIVITIES. None of the requirements in this document requires to implement these ACTIVITIES as one single PROCESS or as separate PROCESSES. The ACTIVITIES specified in this document will typically be part of an existing LIFE CYCLE PROCESS.

  • Standard
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day

XFS4IoT has been identified as a successor to XFS 3.x to meet the following requirements:
1.   Replace the XFS and J/XFS standards in the marketplace.
2.   Target industries – Retail Banking.
3.   Operating System Agnostic and Technology and Language Adaptable.
4.   Multi-Vendor – Able to run common core high level functionality on multiple vendors hardware, while providing access to finer level device API granularity.
5.   Flexibility – enabling new hardware topologies, device types and functionality to be rapidly adapted.
6.   Support end to end application level security.
7.   Should not prevent the use of a low resource computing environment.
8.   Provide a good developer experience by providing a well-documented API that is easy to learn, is quick to market and reduces risk by exposing an unambiguous interface.
9.   Leverage existing standards.
Within the overall requirements specified in the Charter, the opportunity has been taken to solve some of the issues with the 3.x interface while retaining all the same functionality:
1.   Binary data structures makes adding new functionality difficult due to compatibility issues, leading to multiple redundant versions of the same command appearing in many of the existing device classes. To resolve this, a flexible text based approach has been adopted including the wide use of default parameters.
2.   Compound devices have been difficult for applications to implement, particularly cash recycling. Addition of other shared functionality such as end to end security would make the use of compound devices more prevalent. Compound devices are removed in XFS4IoT, a single Service can support as many interfaces as required to support its requirements.
Migration from and to 3.x is a major consideration to support adoption of XFS4IoT. While a lot of duplication has been removed (for example the Card Reader interface has fewer commands and events defined than the equivalent 3.x IDC specification), all the same IDC commands and events can be implemented. In some cases, this is achieved by having shared common commands such as Common.Status which replaces all the 3.x WFS_INF_XXX_STATUS commands.

  • Standardization document
    752 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IT NC submits to CLC TC79 the request for an amendment work of the EN 62820-1-1:2016, within CLC/TC 79/WG 15

  • Amendment
    7 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    6 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO/IEC 30162:2022 specifies network models for IIoT connectivity and general compatibility requirements for devices and networks within IIoT systems in terms of:
a) data transmission protocols interaction;
b) distributed data interoperability & management;
c) connectivity framework;
d) connectivity transport;
e) connectivity network;
f) best practices and guidance to use in IIoT area.

  • Standard
    44 pages
    English language
    sale 15% off

This document provides a guidance on how to develop an Information Delivery Manual (IDM) in compliance with EN ISO 29481-1 hereafter referred to as the "IDM standard". This document explains the core components and development process of the IDM methodology in non-technical terms. This guidance aims to help users and software vendors understand and utilise the IDM standard in defining information requirements and deliverables.
The technical implementation of IDM in a data model, Model View Definition 1) (MVD), is excluded from this guideline’s scope. IDM standard introduces the MVD concept but does not specify it in detail.
This guidance also utilises some transaction framework concepts introduced in EN ISO 29481-2. The technical XML- and XSD-schema definitions supporting the software solutions are excluded from this guidance.
1) An MVD defines a data model or a subset of an existing data model that is necessary to support one or many specific data exchange requirements. MVDs are used in software development and should have a machine-readable representation. An MVD that is dedicated to a single IDM can be used to filter information in software tools to a specific exchange requirement. [SOURCE: EN ISO 29481-1:2017, 5.6.4].
1.1   Background
This guideline primary reference is the IDM standard part 1 (EN ISO 29481-1:2017) (hereafter referred to as IDM standard). This guideline helps in understanding and using the IDM standard to describe information delivery. The guidance also uses some concepts described in part 2 of the IDM standard series (EN ISO 29481-2:2016). Considerable efforts have been made to align this guidance with the terminology and concepts introduced in EN ISO 19650-1 and EN ISO 19650-2.
Information Delivery Manual specification (hereafter referred to as the IDM specification) provides help in getting the full benefit from building information modelling (BIM). When the required information is available in the BIM to support a construction process or use case, and the quality of information is satisfactory, the process itself is much improved. The IDM standard provides a method to create the specification.
A complete IDM specification should support two perspectives: user requirements and technical solutions. User requirements describe the needed information delivery and the overall process in which information exchange occurs. The technical solution defines an exchange requirement model using a harmonised data schema.
EN ISO 29481-1 provides a methodology and a harmonised format to specify information requirements. It offers a framework and method to determine the needed information delivery with process maps and exchange requirements.
EN ISO 29481-2 specifies an interaction framework and format to describe "coordination acts" between actors or parties within an appointment. It facilitates interoperability between software applications used in the construction process to promote digital collaboration between actors in the building construction process. Also, it provides a basis for accurate, reliable, repeatable, and high-quality information exchange.
1.2   Users of this guidance document
This guidance document is intended for clients, architects, engineers, contractors, surveyors, authorities, and other parties who need to specify or implement information delivery. Originally, the IDM standard was focused on defining BIM deliverables, but the possible application of the standard is much broader. It can be used to specify any requirement for information delivery.
Although software developers and technology adapters are not the primary audiences of this guidance document, it may help them better understand existing IDMs and develop their own IDMs.
1.3   Relation to EN ISO 19650
The IDM standard is a process-oriented methodology used to describe the information exchange requirements for a particular purpose which may complement the information-management approach outlined in the EN ISO 19650 series...

  • Technical report
    19 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of IEC 61375 applies to all equipment and devices implemented according to
IEC 61375-2-3:2015, IEC 61375-2-5:2014 and IEC 61375-3-4:2014, i.e. it covers the
procedures to be applied to such equipment and devices when the conformance should be
proven.
The applicability of this document to a TCN implementation allows for individual conformance
checking of the implementation itself, and is a pre-requisite for further interoperability checking
between different TCN implementations.

  • Standard
    361 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies requirements and recommendations for the planning, design, development and provision of communication services related to passenger transport so that this information can be accessed, understood and used by the widest range of users, including persons with disabilities and older persons.
These requirements and recommendations enable an organization to extend its range of users by identifying diverse characteristics, capabilities, and preferences.
The requirements set out in this standard are applicable to but not limited to passenger transport service providers including air-, bus, rail-, and waterborne passenger transport services.

  • Standard
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    54 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document is applicable to all construction products and services related to buildings and construction works. It specifies and describes the communication format for the information defined in EN 15804 for business-to-business communication to ensure a common understanding through consistent communication of information.
NOTE   This document does not deal with business to consumer communication and is not intended for that purpose. Business to consumer communication format is planned to be the subject of a future document.

  • Standard
    35 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies:
— personalization interface;
— physical systems: on-board equipment (OBE), personalization equipment (PE) and integrated
circuit(s) cards (ICCs);
— electronic fee collection (EFC) personalization functions between the PE and the OBE in accordance
with ISO/TS 21719-1 when using an ICC;
— data and security elements that are transferred between the PE and the OBE using the ICC.
It is outside the scope of this document to define:
— conformance procedures and test specifications;
— setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third
party, etc.);
— legal issues;
— the exact commands and security functionality within ISO/IEC 7816-4 used by the PE and the OBE,
respectively, to interface an ICC.
NOTE Some of the issues that are outside the scope of this document are the subject of separate standards
prepared by CEN/TC 278 and ISO/TC 204

  • Technical specification
    25 pages
    English language
    sale 10% off
    e-Library read for
    1 day

Service Interface for Real Time Information (SIRI) is a specification for an interface that allows systems running computer applications to exchange information about the planned, current or projected performance of the public transport operations.
The scope of this WI is to update CEN/TS 15531-4:2015 which allows pairs of server computers to exchange structured real-time information about schedules, vehicles, and connections, together with general informational messages related to the operation of the services. The information can be used for many different purposes, for example:
• To provide real time-departure from stop information for display on stops, internet and mobile delivery systems;
• To provide real-time progress information about individual vehicles;
• To manage the movement of buses roaming between areas covered by different servers;
• To manage the synchronisation of guaranteed connections between fetcher and feeder services;
• To exchange planned and real-time timetable updates;
• To distribute status messages about the operation of the services;
• To provide performance information to operational history and other management systems.
Implementations SIRI have revealed a number of improvements and some minor enhancements necessary for a successful and uniform usage of the specification in the future.
The main elements out of this work item will be:
o Prepare an updated edition of the TS as a document
o Update the common XSD of SIRI parts 1-5
The new work item will consider the projects of
o PT companies and IT-suppliers especially in Switzerland, Germany, France, Netherlands and Sweden
o Railway traffic
o accessibility in public transport

  • Technical specification
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard specifies the requirements and recommendations for the attributes of Automated Infrastructure Management (AIM) systems.

  • Amendment
    9 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    6 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the HBES Information Model and a corresponding data exchange format for the Home and Building HBES Open Communication System.

  • Standard
    86 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This technical specification provides guidance on
• capturing of facial images to be used as reference images in identity or similar documents,
• capturing of fingerprint images to be used as reference images in identity or similar documents,
• data quality maintenance for biometric reference data,
• data authenticity maintenance for biometric reference data.
The TS addresses the following aspects which are specific for biometric reference data capturing:
• biometric data quality and interoperability ensurance,
• data authenticity ensurance,
• morphing and other presentation attack detection,
• accessibility and usability,
• privacy and data protection,
• optimal process design.
The following aspects are out of scope:
• IT security,
• data capturing for verification purposes, e.g., in ABC gates.
• self-taken images, although a section on this has been included

  • Technical specification
    73 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the structure of an ontology for a fine-grained description of the expressive power of corpus query languages (CQLs) in terms of search needs. The ontology consists of three interrelated taxonomies of concepts: the CQLF metamodel (a formalization of ISOÂ 24623-1); the expressive power taxonomy, which describes different facets of the expressive power of CQLs; and a taxonomy of CQLs.
This document specifies:
a) the taxonomy of the CQLF metamodel;
b) the topmost layer of the expressive power taxonomy (whose concepts are called “functionalities”);
c) the structure of the layers of the expressive power taxonomy and the relationships between them, in the form of subsumption assertions;
d) the formalization of the linkage between the CQL taxonomy and the expressive power taxonomy, in the form of positive and negative conformance statements.
This document does not define the entire contents of the ontology (see Clause 4).

  • Standard
    23 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    18 pages
    English language
    sale 15% off
  • Draft
    24 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides requirements and recommendations for representing subject fields and concept relations in TBX-compliant terminological document instances. Examples in this document utilize the DCA style of TBX markup.

  • Technical specification
    20 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    15 pages
    English language
    sale 15% off

This document defines the LIFE CYCLE requirements for development and maintenance of HEALTH SOFTWARE needed to support conformance to IEC 62443-4-1 – taking the specific needs for HEALTH SOFTWARE into account. The set of PROCESSES, ACTIVITIES, and TASKS described in this document establishes a common framework for secure HEALTH SOFTWARE LIFE CYCLE PROCESSES. The purpose is to increase the CYBERSECURITY of HEALTH SOFTWARE by establishing certain ACTIVITIES and TASKS in the HEALTH SOFTWARE LIFE CYCLE PROCESSES and also by increasing the SECURITY of SOFTWARE LIFE CYCLE PROCESSES themselves. It is important to maintain an appropriate balance of the key properties SAFETY, effectiveness and SECURITY as discussed in ISO 81001-1. This document excludes specification of ACCOMPANYING DOCUMENTATION contents.

  • Draft
    52 pages
    English language
    sale 15% off

This document specifies the transactions between libraries or libraries and other agencies to handle requests for library items and the following exchange of messages.

  • Draft
    46 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document describes the identification scheme used by the Biometric Registration Authority (BRA) in preparing, maintaining and publishing registers of identifiers for biometric organizations and biometric objects, and provides a description of BRA responsibilities and services. Procedural requirements and recommendations are not within the scope of this document and are maintained separately on the ISO/IEC JTCÂ 1/SCÂ 37 website.

  • Draft
    6 pages
    English language
    sale 15% off

This document specifies data exchange and communications for meters in a generic way.
This document establishes a protocol specification for the Application Layer for meters and establishes several protocols for meter communications which can be applied depending on the application being fulfilled.
This document also specifies the overall structure of the OBject Identification System (OBIS) and the mapping of all commonly used data items in metering equipment to their identification codes.”
NOTE   Electricity meters are not covered by this document, as the standardization of remote readout of electricity meters is a task for CENELEC/IEC.

  • Standard
    129 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    130 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies Advanced Function Presentation (AFP) interchange as a container for document objects by defining the AFP file format Mixed Object Document Content Architecture (MO:DCA)[1]. It includes a means of identifying support for specifically including single and multi-page Portable Document Format (PDF) document objects as a container function set. It also includes a mechanism for pairing and managing resources associated with PDF. NOTE      For an example of how PDF external file references map into AFP secondary resources, see Annex A. The use of AFP is applicable to AFP and PDF workflows where the final production is managed within an Intelligent Printer Data Stream (IPDS) environment.  [1] The Architecture references shown (MO:DCA as an example) are copyright of the AFP Consortium. This information is given for the convenience of users of this document and does not constitute an endorsement by ISO of this product.

  • Standard
    31 pages
    English language
    sale 15% off
  • Draft
    31 pages
    English language
    sale 15% off

This document specifies performance requirements and test procedures for systems capable of warning the subject vehicle driver of a potential crossing-path collision with other vehicles at intersecting road segments. Vehicle-to-vehicle intersection collision warning systems (VVICW) rely on vehicle-to-vehicle (V2V) communications and relative positioning between the subject vehicle and crossing-path vehicles (remote vehicles). V2V data, such as position, speed and heading are used to evaluate if an intersection collision is imminent between the subject and remote vehicles. The performance requirements laid out in this document specify the warning criteria for these systems. In addition, VVICW operate in specified subject and remote vehicle speed ranges, road intersection geometries and target vehicle types. Moreover, the requirements for the V2V data will be specified. The scope of this document includes operations on intersecting road segments (physically intersecting roads), and motor vehicles including cars, trucks, buses and motorcycles. Responsibility for the safe operation of the vehicle remains with the driver.

  • Standard
    18 pages
    English language
    sale 15% off

This document provides general sharing economy principles. It is intended to be used by all types and sizes of organization (e.g. commercial enterprises, government agencies, not-for-profit organizations).

  • Standard
    5 pages
    English language
    sale 15% off
  • Draft
    5 pages
    English language
    sale 15% off

This document specifies general requirements for ORGANIZATIONS in the application of RISK
MANAGEMENT before, during and after the connection of a HEALTH IT SYSTEM within a HEALTH IT
INFRASTRUCTURE, by addressing the KEY PROPERTIES of SAFETY, EFFECTIVENESS and SECURITY
whilst engaging appropriate stakeholders.

  • Standard
    39 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies a reference dictionary for cutting items, together with their descriptive properties and domains of values. This document specifies a reference dictionary containing: —   definitions and identifications of the classes of cutting items and their features, with an associated classification scheme; —   definitions and identifications of the data element types that represent the properties of cutting items and their features; —   definitions and identifications of domains of values for describing the above-mentioned data element types. The following are within the scope of this document: —   standard data that represent the various classes of cutting items and cutting item features; —   standard data that represent the various properties of cutting items and cutting item features; —   standard data that represent domains of values used for properties of cutting items and cutting item features; —   definitions of reference systems for cutting items and their properties; —   one implementation method by which the standard data defined in this document can be exchanged. NOTE 1   The implementation method by which the standard data defined in this document can be exchanged is specified in ISO 10303-21. The following are outside the scope of this document: —   applications where these standard data can be stored or referenced; —   implementation methods other than the one defined in this document by which the standard data can be exchanged and referenced; —   information model for cutting tools; —   definitions of classes and properties for tool items; —   definitions of classes and properties for adaptive items; —   definitions of classes and properties for assembly items and auxiliary items. NOTE 2   The information model for cutting tools is defined in ISO 13399-1. NOTE 3   The definitions of classes and properties for tool items, adaptive items, assembly items, and auxiliary items are provided in ISO/TS 13399-3, ISO/TS 13399-4, and ISO/TS 13399-5, respectively.

  • Technical specification
    201 pages
    English language
    sale 15% off
  • Technical specification
    203 pages
    French language
    sale 15% off

This document specifies a reference dictionary for adaptive items, together with their descriptive properties and domains of values. This document specifies a reference dictionary containing: —   definitions and identifications of the classes of adaptive items, with an associated classification scheme; —   definitions and identifications of the data element types that represents the properties of adaptive items; —   definitions and identifications of domains of values for describing the above-mentioned data element types. The following are within the scope of this document: —   standard data that represent the various classes of adaptive items; —   standard data that represent the various properties of adaptive items; —   standard data that represent domains of values used for properties of adaptive items; —   one implementation method by which the standard data defined in this document can be exchanged. NOTE 1   The implementation method by which the standard data defined in this document can be exchanged is specified in ISO 10303-21. The following are outside the scope of this document: —   specialized or expert knowledge in the design and use of cutting tools; —   rules to determine what information should be communicated; —   applications where these standard data can be stored or referenced; —   implementation methods other than the one defined in this document by which the standard data can be exchanged and referenced; —   information model for cutting tools; —   definitions of classes and properties for cutting items; —   definitions of classes and properties for tool items; —   definitions of classes and properties for assembly items; —   definitions of classes and properties for connection systems; —   definitions of classes and properties for reference systems. NOTE 2   The information model for cutting tools is defined in ISO 13399-1. NOTE 3       The definitions of classes and properties for cutting items, tool items, and assembly items are provided in ISO/TS 13399-2, ISO/TS 13399-3, and ISO/TS 13399-5. NOTE 4       The definitions of classes and properties for connection systems and reference systems are provided in ISO/TS 13399-50.

  • Technical specification
    199 pages
    English language
    sale 15% off
  • Technical specification
    200 pages
    French language
    sale 15% off

This document specifies a reference dictionary for tool items, together with their descriptive properties and domains of values. This document specifies a reference dictionary containing: —   definitions and identifications of the classes of tool items and their features, with an associated classification scheme; —   definitions and identifications of the data element types that represents the properties of tool items and their features; —   definitions and identifications of domains of values for describing the above-mentioned data element types. The following are within the scope of this document: —   standard data that represent the various classes of tool items and tool item features; —   standard data that represent the various properties of tool items and tool item features; —   standard data that represent domains of values used for properties of tool items and tool item features; —   definition of cutting operations; —   definitions of reference systems for tool items and their properties; —   one implementation method by which the standard data defined in this document can be exchanged. NOTE 1   The implementation method by which the standard data defined in this document can be exchanged is specified in ISO 10303-21. The following are outside the scope of this document: —   specialized or expert knowledge in the design and use of cutting tools; —   rules to determine what information should be communicated; —   applications where these standard data can be stored or referenced; —   implementation methods other than the one defined in this document by which the standard data can be exchanged and referenced; —   information model for cutting tools; —   definitions of classes and properties for cutting items; —   definitions of classes and properties for adaptive items; —   definitions of classes and properties for assembly items; —   definitions of classes and properties for connection systems; —   definitions of classes and properties for reference systems. NOTE 2   The information model for cutting tools is defined in ISO 13399-1. NOTE 3   The definitions of classes and properties for cutting items, adaptive items, and assembly items are provided in ISO/TS 13399-2, ISO/TS 13399-4, and ISO/TS 13399-5, respectively. NOTE 4   The definitions of classes and properties for connection systems and reference systems are provided in ISO/TS 13399-50.

  • Technical specification
    461 pages
    English language
    sale 15% off
  • Technical specification
    465 pages
    French language
    sale 15% off

This document defines the configuration rules required for a hierarchical structure, directory naming rules, and content identifiers for files and documents containing healthcare information. Content can be expressed as ISO/HL7 27931:2009 (also known as HL7 Ver2.5) as the data format to store clinical data such as prescriptions, lab results, and disease classifications, but can also include other types of file-type such as XML, CDA, DOC/DOCX, PDF, XLS/XLSX, JPEG, MP4, etc. This document does not address the security and privacy attributes of the healthcare information being stored; these are considered implementation-specific.

  • Technical specification
    13 pages
    English language
    sale 15% off

This document defines physical characteristics and test methods for cards with devices, including but not limited to, power supplying devices, displays, sensors, microphones, loudspeakers, buttons or keypads. This document also covers aspects of coexistence of technologies of devices on the card and other machine-readable card technologies. Additional requirements related to biometric capture devices are defined in ISO/IEC 17839-2. Such requirements can be applied in addition to the ones defined in this document. ISO/IEC 17839-2 defines a type S2 card; the physical dimensions of the type S2 card are specified in Annex A.

  • Standard
    25 pages
    English language
    sale 15% off
  • Draft
    25 pages
    English language
    sale 15% off

This document provides information and requirements for identifying cost-effective technologies and related standards required to deploy, manage and operate sustainable “green” ITS technologies in surface transportations with eco-mobility. These ITS technologies can increase operational efficiencies and unlock enhanced transportation safety and eco-mobility applications. The ISO 20529 series builds on the existing standards and best practices of transport operation and management systems, as well as ITS applications, and aims to accommodate the specific needs of eco-mobility. G-ITS standards are expected to focus on the use of data exchange interface standards to enable the deployment of cloud-based multi-modal mobility solutions using wireless networks and nomadic devices. These forward-looking solutions are “infrastructure light” and can thus impact developing regions with little or no legacy transportation infrastructure. This document is intended to provide mobility information according to user preference on demand, utilizing a variety of existing apps on nomadic devices related to various means of transport. An integrated mobility information platform is defined in this document as a service methodology to be integrated with a variety of mobile apps with respect to different modes of transport. The framework described in this document includes: —   Identification of implementation aspects of related standards by means of use case. —   Identification of the multi-modal transport information necessary to support G-ITS. —   Eco-friendly route guidance according to user preference. —   Smart modal choice service based on carbon footprint, fuel efficiency and carbon-free zones for G-ITS.

  • Standard
    64 pages
    English language
    sale 15% off
  • Draft
    64 pages
    English language
    sale 15% off

This document defines the syntax and semantics in the field of electronic fee collection (EFC). The data types and assignment of vales are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824 1. In particular, this document defines:
— ASN.1 (data) types within the fields of EFC and road user charging;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.

  • Technical specification
    54 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the requirements for medication safety alert systems and the topics which are
relevant to alert system vendors. This document applies to clinical decision support systems (CDSSs)
whether or not these are medical devices.
This document addresses:
— requirements for terminology used in medication safety alerts;
— requirements for choosing a knowledge base for medication safety alert systems;
— requirements for the proper functionality of CDSSs as related to medication safety alert systems;
— requirements for medication safety alert display;
— requirements for quality measurements to improve the effectiveness of medication safety alerts.
The following are out of the scope of this document:
— the development of content (rule-based knowledge base) for CDSS;
— the development of algorithms for generating medication safety alerts in CDSS;
— the development of alert processors for medication safety alerts in CDSS.

  • Technical specification
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies a common framework for audit trails for electronic health records (EHR), in
terms of audit trigger events and audit data, to keep the complete set of personal health information
auditable across information systems and domains.
It is applicable to systems processing personal health information that create a secure audit record
each time a user reads, creates, updates, or archives personal health information via the system.
NOTE Such audit records at a minimum uniquely identify the user, uniquely identify the subject of care,
identify the function performed by the user (record creation, read, update, etc.), and record the date and time at
which the function was performed.
This document covers only actions performed on the EHR, which are governed by the access policy
for the domain where the electronic health record resides. It does not deal with any personal health
information from the electronic health record, other than identifiers, the audit record only containing
links to EHR segments as defined by the governing access policy.
It does not cover the specification and use of audit logs for system management and system
security purposes, such as the detection of performance problems, application flaw, or support for
a reconstruction of data, which are dealt with by general computer security standards such as ISO/
IEC 15408 (all parts)[9].
Annex A gives examples of audit scenarios. Annex B gives an overview of audit log services

  • Standard
    56 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    50 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document establishes a learner information model specific to mobile learning to enable learning, education and training environments to reflect the specific needs of mobile participants. It gives guidance on the use of a learner information model for mobile technology in learning, education and training (mobile learning). This document can be used as a reference by software developers, implementers, instructional designers, teachers, trainers, automated systems and learning management systems.

  • Standard
    18 pages
    English language
    sale 15% off

This document provides requirements and recommendations for representing subject fields and concept relations in TBX-compliant terminological document instances. Examples in this document utilize the DCA style of TBX markup.

  • Technical specification
    20 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    15 pages
    English language
    sale 15% off

This document specifies a taxonomy and an ontology for blockchain and distributed ledger technologies (DLT). The taxonomy includes a taxonomy of concepts, a taxonomy of DLT systems and a taxonomy of application domains, purposes and economy activity sections for use cases. The ontology includes classes and attributes as well as relations between concepts. The audience includes but is not limited to academics, architects, customers, users, tool developers, regulators, auditors and standards development organizations.

  • Technical specification
    28 pages
    English language
    sale 15% off
  • Draft
    24 pages
    English language
    sale 15% off

This document specifies data interchange formats for signature/sign behavioural data captured in the form of a multi-dimensional time series using devices such as digitizing tablets or advanced pen systems. The data interchange formats are generic, in that they can be applied and used in a wide range of application areas where handwritten signs or signatures are involved. No application-specific requirements or features are addressed in this document. This document contains: —   a description of what data can be captured; —   three binary data formats for containing the data: a full format for general use, a compression format capable of holding the same amount of information as the full format but in compressed form, and a compact format for use with smart cards and other tokens that does not require compression/ decompression but conveys less information than the full format; —   an XML schema definition; and —   examples of data record contents and best practices in capture. Specifying which of the format types and which options defined in this document are to be applied in a particular application is out of scope; this needs to be defined in application-specific requirements specifications or application profiles. It is advisable that cryptographic techniques be used to protect the authenticity, integrity, and confidentiality of stored and transmitted biometric data; yet such provisions are beyond the scope of this document. This document also specifies elements of conformance testing methodology, test assertions and test procedures as applicable to this document. It establishes test assertions on the structure and internal consistency of the signature/sign time series data formats defined in this document (type A level 1 and 2 as defined in ISO/IEC 19794-1) and semantic test assertions (type A level 3 as defined in ISO/IEC 19794-1). The conformance testing methodology specified in this document does not establish: —   tests of other characteristics of biometric products or other types of testing of biometric products (e.g. acceptance, performance, robustness, security); or —   tests of conformance of systems that do not produce data records claimed to conform to the requirements of this document.

  • Standard
    84 pages
    English language
    sale 15% off
  • Draft
    84 pages
    English language
    sale 15% off

This document specifies reliability assessment criteria for high-throughput gene-expression data. It is applicable to assessing the accuracy, reproducibility, and comparability of gene-expression data that are generated from microarray, next-generation sequencing, and other forms of high-throughput technologies. This document identifies the quality-related data for the process of the next-generation sequencing of RNA (RNA-seq). The sequencing platform covered by this document is limited to short-read sequencers. The use of RNA-seq for mutation detection and virus identification is outside of the scope of this document. This document is applicable to human health associated species such as human, cell lines, and preclinical animals. Other biological species are outside the scope of this document. From a biological point of view, expression profiles of all genetic sequences including genes, transcripts, isoforms, exons, and junctions are within the scope of this document

  • Technical specification
    11 pages
    English language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off

This document provides an overview and general principles of a digital twin framework for manufacturing including: —   terms and definitions; —   requirements of the digital twin framework for manufacturing.

  • Standard
    12 pages
    English language
    sale 15% off
  • Draft
    12 pages
    English language
    sale 15% off

This Handbook provides guidance on the application of the dependability and safety requirements relevant to software defined in EN 16602-80 (equivalent of ECSS-Q-ST-80).
This Handbook provides support for the selection and application of software dependability and safety methods and techniques that can be used in the development of software-intensive space systems.
This Handbook covers all of the different kinds of software for which EN 16602-80 (equivalent of ECSS-Q-ST-80) is applicable. Although the overall software dependability and safety workflow description is mainly targeted to the development of spacecraft, the described approach can be adapted to projects of different nature (e.g. launchers, ground systems).
The methods and techniques described in the scope of this Handbook are limited to assessment aspects, not including development and implementation techniques for dependability and safety (e.g. fault tolerance techniques, or development methods like coding standards, etc.).
Although dependability is a composite term, including reliability, availability and maintainability, this Handbook addresses in particular the reliability aspects. Software maintainability and availability are not covered in depth by this handbook, because the relevant methods and techniques are still undergoing improvement. Nevertheless, whenever a link can be made to either of these two characteristics, it is explicitly mentioned in the corresponding section.

  • Technical report
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This handbook defines methods for process assessment and improvement that may be used to meet the requirements on
process assessment and improvement of the EN16602-80 (equivalent to ECSS-Q-ST-80C) subclause 5.7. These methods constitute a clear and proven w ay of implementing those requirements. Alternative methods can be used provided that they meet the detailed instructions provided in this handbook for recognition of software process assessment schemes and results and process improvement.
This handbook provides a detailed method for the implementation of the requirements of the EN16602-80 for software process assessment and improvement. It also establishes detailed instructions for alternative methods intended to meet the same EN16602-80 requirements.
The process assessment and improvement scheme presented in this handbook is based on and conformant to the ISO/IEC 15504 International Standard. In designing this process assessment and improvement scheme the ISO/IEC 15504 exemplar process assessment model w as adopted and extended to address specific requirements.
The methods provided in this handbook can support organizations in meeting their business goals and in this context they can be tailored to suit their specific needs and requirements. How ever w hen used to claim compliance with relevant requirements in EN16602-80 only the steps and activities explicitly marked as recommended in this handbook may be omitted or modified.

  • Technical report
    122 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    122 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This handbook provides recommendations, methods and procedures that can be used for the selection and reuse of existing software in space software systems.
This handbook is applicable to all types of software of a space system, including the space segment, the launch service segment and the ground segment software (including EGSEs) whenever existing software is intended to be reused within them.
This handbook covers the following topics:
• Software reuse approach including guidelines to build the Software Reuse File
• Techniques to support completion of existing software qualification to allow its reuse in a particular project
• Tool qualification
• Risk management aspects of reusing existing software Existing software can be of any type: Purchased (or COTS), Legacy-Software, open-source software, customer-furnished items (CFI's), etc.
NOTE Special emphasis is put on guidance for the reuse of COTS software often available as-is and for which no code and documentation are often available.
Legal and contractual aspects of reuse are in principle out of scope; how ever guidelines to help in determine the
reusability of existing software from a contractual point of view is provided in [ESA/REG/002].
Any organization with the business objective of systematic reuse may need to implement the organizational reuse processes presented in [ISO12207]. These processes w ill support the identification of reusable software products and components within selected reuse domains, their classification, storage and systematic reuse within the projects of that organization, etc. But these processes are out of scope of this handbook as the handbook is centred on the specific project activities to reuse an existing software product, not part of those organizational reuse processes more oriented to ‘design for reuse’ processes.
In addition, this handbook provides guidelines to be used for the selection and analysis of tools for the development, verification and validation of the operational software.

  • Technical report
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day