35.240.99 - IT applications in other fields
ICS 35.240.99 Details
IT applications in other fields
Weitere IT-Anwendungen
Applications des TI dans les autres secteurs
Uporabniške rešitve IT na drugih področjih
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.99 - IT applications in other fields
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document defines the CCSDS and International Organization for Standardization (ISO) Reference Model for an Open Archival Information System (OAIS). An OAIS is an Archive system consisting of hardware, software, information, and policy-based processes and procedures put in place and operated by an organization and its staff. The organization has accepted the responsibility to preserve information and make it available for a Designated Community. The organization may be part of a larger organization. The system meets a set of mandatory responsibilities that allow an OAIS Archive to be distinguished from other uses of the term ‘archive’. The set of mandatory responsibilities an OAIS Archive must perform are defined in REF _Ref511638039 \r \h 3.2 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003500310031003600330038003000330039000000 . The term ‘Open’ in OAIS is used to imply that this Recommended Practice, as well as future related Recommended Practices and standards, are developed in open forums, and it does not imply that access to the Archive is unrestricted. The information being maintained has been deemed to need Long Term Preservation, even if the OAIS itself is not permanent. Long Term is long enough to be concerned with the impacts of changing technologies, as well as support for new media and data formats, or with a changing Knowledge Base of the Designated Community or changes within the Designated Community or its definition. Long Term may extend indefinitely. In this Reference Model there is a particular focus on digital information, both as the primary forms of information held and as supporting information for both digitally and physically preserved materials. Therefore, the model accommodates information that is inherently non-digital (e.g., a physical sample), but the modelling and preservation of such information is not addressed in detail. This Reference Model:
– provides a framework for the understanding and increased awareness of archival concepts needed for Long Term digital information preservation and access;
– provides the concepts needed by non-archival organizations to be effective participants in the preservation process;
– provides a framework, including terminology and concepts, for describing and comparing architectures and operations of existing and future Archives;
– provides a framework for describing and comparing different Long Term Preservation strategies and techniques;
– provides a basis for comparing the data models of digital information preserved by Archives and for discussing how the data models and the underlying information may change over time;
– provides a framework that may be expanded by other efforts to cover Long Term Preservation of information that is NOT in digital form (e.g., physical media and physical samples);
– expands consensus on the elements and processes for Long Term digital information preservation and access, and promotes a larger market which vendors can support;
– guides the identification and production of OAIS-related standards.
The reference model addresses a full range of archival information preservation functions including ingest, archival storage, data management, access, and dissemination. It also addresses the migration of digital information to new media and forms, the information models used to represent the information, the role of software in information preservation, and the exchange of digital information among Archives. It identifies both internal and external interfaces to the Archive functions, and it identifies a number of high-level services at these interfaces. It provides various illustrative examples and some ‘best practice’ recommendations. It defines a minimal set of responsibilities for an Archive to be called an OAIS, and it also defines a maximal Archive to provide a broad set of useful terms and concepts.
- Standard151 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard139 pagesEnglish languagesale 15% off
This document specifies a common data exchange format (i.e. format of the messages and the dictionary of all the items that compose the message) between the prescribers and the laboratories in the animal health sector.
This document is intended for prescribers (purchasers) and service providers in charge of collecting samples and conducting analyses (including laboratories) who are interested in computerizing and standardizing their data exchanges, particularly in the animal health sector.
This document excludes the code lists that are required for unambiguous data exchange.
- Standard53 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a common data exchange format (i.e. format of the messages and the dictionary of all the items that compose the message) between the prescribers and the laboratories in the animal health sector.
This document is intended for prescribers (purchasers) and service providers in charge of collecting samples and conducting analyses (including laboratories) who are interested in computerizing and standardizing their data exchanges, particularly in the animal health sector.
This document excludes the code lists that are required for unambiguous data exchange.
- Standard53 pagesEnglish languagesale 10% offe-Library read for1 day
The main objective of this WI is to define a SIRI Passenger Real-Time Information European profile:
• To identify a minimum subset of SIRI with codification rules and constraints for a European level plug and play exchange of real-time passenger information data between organisations at a European level
• To reflect already existing NeTEx profiles defined at national level (Norway, France, Sweden, etc.).
• To maintain a relevant real-time information dataset, as small and simple as possible, to ensure interoperability is maximised while at the same time enabling exchange of supplementary national real-time data that will not interfere with the core international dataset
• To complement the EPIP (NeTEx European Passenger Information Profile) with real-time passenger information
• To establish quality assessment procedures for implementing validation and quality assessment tools - including compliance checking rules - necessary to fulfil the requirement of the Commission
This profile will complement the NeTEx Passenger information profile and NeTEx Accessibility profile (under drafting) in order to get a set of consistent European profiles fulfilling the requirements of the Priority Action "A" of the ITS Directive.
- Technical specification208 pagesEnglish languagesale 10% offe-Library read for1 day
The main objective of this WI is to define a SIRI Passenger Real-Time Information European profile:
• To identify a minimum subset of SIRI with codification rules and constraints for a European level plug and play exchange of real-time passenger information data between organisations at a European level
• To reflect already existing NeTEx profiles defined at national level (Norway, France, Sweden, etc.).
• To maintain a relevant real-time information dataset, as small and simple as possible, to ensure interoperability is maximised while at the same time enabling exchange of supplementary national real-time data that will not interfere with the core international dataset
• To complement the EPIP (NeTEx European Passenger Information Profile) with real-time passenger information
• To establish quality assessment procedures for implementing validation and quality assessment tools - including compliance checking rules - necessary to fulfil the requirement of the Commission
This profile will complement the NeTEx Passenger information profile and NeTEx Accessibility profile (under drafting) in order to get a set of consistent European profiles fulfilling the requirements of the Priority Action "A" of the ITS Directive.
- Technical specification208 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides the icons to specify the function and to indicate status of the serviced offices and their services. The icons are used as the user interfaces for searching, booking, and advertising applications for serviced offices. This document specifies basic icons that define the functions of all serviced offices, and also specifies additional and miscellaneous icons that indicate other services. The functions specified by the icons include facilities, equipment and services for fulfilling various user needs such as working style, tools, amenities, language and accessibility needs, including older persons, etc.
- Standard15 pagesEnglish languagesale 15% off
This document specifies an event exchange format that defines the encoding of individual events in the interoperability domain. This event format is used to encode events for exchange across the “event bus” within the interoperability domain.
- Standard39 pagesEnglish languagesale 15% off
This document specifies a lexicon of objects for the interoperability domain (ID). This document specifies ID base objects and their associated properties and input/output event types (i.e. in the form of a list of ID sensor, actuator, and control objects), and object state actions, which can be used to define interoperable application models.
- Standard229 pagesEnglish languagesale 15% off
This document specifies messaging among user, interface and service objects in the HES gateway to enable interworking among home cluster systems and interoperability among the applications supported by these cluster systems, as well as a common user interface to these cluster-system applications. This common user interface provides input and output methods for user information exchange to access, monitor and control applications running on home cluster systems. This document specifies messaging among the required service and interface modules from the interoperability standard necessary for interworking and incorporation of these modules in the HES gateway (ISO/IEC 15045 series).
- Standard22 pagesEnglish languagesale 15% off
This International Standard specifies the minimum requirements for billing of all consumption-based utility
network services to domestic customers. It covers the processes required to produce the bill and to deal with
issues that arise after the bill has been sent, as well as the content of the billing document or statement. This
International Standard is applicable to utility network services that are unmetered, metered at the point of
delivery or metered remotely (e.g. on the supplier's own premises), and it covers any unmetered or unmeasured
charges appearing on the same bill as metered or measured charges, as well as flat rate charges.
NOTE 1 Utility network services include electricity supply, water, sanitation, gas supply, district heating and
communications.
NOTE 2 The requirements given in this International Standard are also applicable to other consumers who are legally
entitled to use the service provided by the supplier, except where in order to comply with privacy or data protection
requirements, it is necessary for the supplier to obtain the authority of the registered customer before dealing with another
consumer on billing matters.
This International Standard does not cover pricing, except for a requirement to provide information to
customers. It is only applicable to billing for consumption-based utility network services and it applies to all bills
or statements for utility network services where there is an ongoing account relationship between the customer
and the supplier, regardless of the payment method used.
NOTE 3 This includes bills for metered consumption, bills where a formula is used to estimate consumption (e.g. water
bills based on the number of persons per household or the size of the house), or where a flat rate fee is charged regardless
of consumption (e.g. telephony or internet bills where the tariff allows unlimited usage). It also applies to prepayment
customers, where a bill or account from the supplier is necessary to enable the customer to reconcile the amount paid
in advance with the cost of consumption, or where the customer expects to receive a bill based on point of sale or other
advertising (e.g. mobile telephony and energy metering) where codes, keys, electronic dongles or electronic cards are
used to load and reload the service and to indicate what was purchased.
NOTE 4 Services that are not billed [e.g. mobile telephony paid for by pre-purchased SIM (Subscriber Identity Module)
cards that are unmetered] and services that are funded directly by the taxpayer without bills being issued are not covered
by this International Standard.
NOTE 5 Many of the key principles in this International Standard also apply to all forms of billing, and suppliers are
therefore encouraged to adopt the relevant requirements in this International Standard for billing of other services.
- Standard27 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard21 pagesEnglish languagesale 15% off
This document specifies technical exchange formats for audit data collection, customs and indirect tax extension, in Extensible Markup Language (XML), JavaScript Object Notation (JSON) and flat file (CSV) as output file formats for the functional content defined in ISO 5401. This document also contains the following schema files and mapping tables related to ISO 5401: — XML schema files; — JSON schema files; — CSV mapping tables, included as separate sheets in an Excel file. To keep the three exchange formats (XML, JSON, CSV) consistent, this document also specifies how to use the technical solution in the CSV format.
- Technical specification29 pagesEnglish languagesale 15% off
This document specifies technical exchange formats for audit data collection, government regulated financial reports and payroll extension, in Extensible Markup Language (XML), JavaScript Object Notation (JSON) and flat file (CSV) as output file formats for the functional content defined in ISO 5405. This document also contains the following schema files and mapping tables related to ISO 5405: — XML schema files; — JSON schema files; — CSV mapping tables, included as separate sheets in an Excel file. To keep the three exchange formats (XML, JSON, CSV) consistent, this document also specifies how to use the technical solution in the CSV format.
- Technical specification30 pagesEnglish languagesale 15% off
This document uses a set of models that describe the flows of different types of data between distributed ledger technologies (DLT) and related systems, as well as between different DLT nodes. It provides a descriptive analysis of data flows in the development of use cases, as well as the basis for understanding the characteristics of DLT data flows, to support DLT application design and system analysis. The models referenced are in accordance with ISO 23257 and the use case analysis approach provided in ISO/TR 3242.
- Technical report49 pagesEnglish languagesale 15% off
This document defines fundamental terminology for blockchain and distributed ledger technologies.
- Standard22 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines fundamental terminology for blockchain and distributed ledger technologies.
- Standard22 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies application services for communication systems for meters, sensors, and actuators, used to provide metering services.
This document specifies application protocols, especially the M-Bus application protocol.
This document is intended to be used with the lower layer specifications determined in the relevant parts of the EN 13757 series.
- Standard120 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies application services for communication systems for meters, sensors, and actuators, used to provide metering services.
This document specifies application protocols, especially the M-Bus application protocol.
This document is intended to be used with the lower layer specifications determined in the relevant parts of the EN 13757 series.
- Standard120 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-10:2025 defines MPP (Magnetic Power Profile), an extension to Qi v1.3 BPP (Baseline Power Profile). Manufacturers can use this specification to implement PTx and/or PRx that are interoperable.
- Draft164 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-11:2025 describes Magnetic power profile (MPP) which is a protocol extension that provides additional messages, new power states/modes, new power transfer contract elements, and aims to provide the following functionalities: • Operating Frequency Negotiation • Cloaking (Power Pause) • Generic Information Exchange • Simultaneous Data Stream Transactions • Fast PTx to PRx communication • Maximum Power and Power Control Profiles Determination • Extended Power Negotiation • Extended PTx/PRx Identification and Capabilities • Extended Control Error Packets and Received Power Packets • Power Transmitter Battery Level Reporting • Ecosystem Scalability MPP extension allows devices to operate under Restricted mode (no PTx communication) at 360kHz without performing any explicit negotiation with the Power Transmitter. This flexibility enables devices with limited resources (e.g., devices with no FSK support) to take advantage of the frequency change feature.
- Draft106 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-5:2025 defines the low-level (physical layer and the data link layer) formats of data bits, data bytes, and data packets. In addition, it provides requirements and guidelines for load modulation and frequency-shift keying.
- Draft23 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-8:2025 provides guidelines for detecting the presence of a Radio Frequency Identification (RFID) tag or Near Field Communication (NFC) card within the operating range of the Power Transmitter and preventing damage to the tag or card.
- Draft29 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-3:2025 identifies basic physical design requirements and guidelines for Power Transmitter and Power Receiver Products, including product and system dimensions, alignment of the products, surface temperature rise, and indications to the user.
- Draft15 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-2:2025 provides glossary of definitions, acronyms, and symbols for the the Qi Specification, which applies to flat surface devices such as mobile phones and tablets that use up to 15 W of power
- Draft15 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-1:2025 introduces the Qi Specification, which applies to flat surface devices such as mobile phones and tablets that use up to 15 W of power
- Draft17 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-6:2025 defines the messaging between a Power Transmitter and a Power Receiver. The primary purpose of this messaging is to set up and control the power transfer. As a secondary purpose, it provides a transport mechanism for higher-level applications such as Authentication. The communications protocol comprises both the required order and timing relations of successive messages.
- Draft139 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-9:2025 defines the architecture and application-level messaging for the Authentication of a Power Transmitter Product by a Power Receiver to ensure that the Power Transmitter Product is both Qi certified and the product of a registered manufacturer.
- Draft91 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-7:2025 defines methods for ensuring that the power transfer proceeds without heating metal objects in the magnetic field of a Power Transmitter. Although the Power Transmitter may optionally use any of these methods, some of them require assistance by the Power Receiver.
- Draft49 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the hardware requirements needed to carry out building automation tasks.
This document is applicable to physical devices, i.e.:
— devices that require human interaction, such as management stations or operator panels;
— devices for data storage and analysis, such as edge or cloud servers;
— devices for control applications, such as automation stations;
— devices for physical quantities acquisition, such as sensors and actuators.
This document provides a generic system topology based on a building network infrastructure, which includes both the devices inside the building envelope and those outside the building envelope.
- Standard22 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 63563-6:2025 defines the messaging between a Power Transmitter and a Power Receiver. The primary purpose of this messaging is to set up and control the power transfer. As a secondary purpose, it provides a transport mechanism for higher-level applications such as Authentication. The communications protocol comprises both the required order and timing relations of successive messages.
- Standard141 pagesEnglish languagesale 15% off
IEC 63563-9:2025 defines the architecture and application-level messaging for the Authentication of a Power Transmitter Product by a Power Receiver to ensure that the Power Transmitter Product is both Qi certified and the product of a registered manufacturer.
- Standard93 pagesEnglish languagesale 15% off
IEC 63563-7:2025 defines methods for ensuring that the power transfer proceeds without heating metal objects in the magnetic field of a Power Transmitter. Although the Power Transmitter may optionally use any of these methods, some of them require assistance by the Power Receiver.
- Standard51 pagesEnglish languagesale 15% off
IEC 63563-8:2025 provides guidelines for detecting the presence of a Radio Frequency Identification (RFID) tag or Near Field Communication (NFC) card within the operating range of the Power Transmitter and preventing damage to the tag or card.
- Standard31 pagesEnglish languagesale 15% off
IEC 63563-5:2025 defines the low-level (physical layer and the data link layer) formats of data bits, data bytes, and data packets. In addition, it provides requirements and guidelines for load modulation and frequency-shift keying.
- Standard25 pagesEnglish languagesale 15% off
IEC 63563-11:2025 describes Magnetic power profile (MPP) which is a protocol extension that provides additional messages, new power states/modes, new power transfer contract elements, and aims to provide the following functionalities:
• Operating Frequency Negotiation
• Cloaking (Power Pause)
• Generic Information Exchange
• Simultaneous Data Stream Transactions
• Fast PTx to PRx communication
• Maximum Power and Power Control Profiles Determination
• Extended Power Negotiation
• Extended PTx/PRx Identification and Capabilities
• Extended Control Error Packets and Received Power Packets
• Power Transmitter Battery Level Reporting
• Ecosystem Scalability
MPP extension allows devices to operate under Restricted mode (no PTx communication) at 360kHz without performing any explicit negotiation with the Power Transmitter. This flexibility enables devices with limited resources (e.g., devices with no FSK support) to take advantage of the frequency change feature.
- Standard108 pagesEnglish languagesale 15% off
IEC 63563-2:2025 provides glossary of definitions, acronyms, and symbols for the the Qi Specification, which applies to flat surface devices such as mobile phones and tablets that use up to 15 W of power
- Standard17 pagesEnglish languagesale 15% off
IEC 63563-10:2025 defines MPP (Magnetic Power Profile), an extension to Qi v1.3 BPP (Baseline Power Profile). Manufacturers can use this specification to implement PTx and/or PRx that are interoperable.
- Standard166 pagesEnglish languagesale 15% off
IEC 63563-4:2025 comprises guidelines and requirements for Power Receiver design, including circuitry, power consumption, operating power levels, power transfer efficiency, and standby power.
- Standard58 pagesEnglish languagesale 15% off
IEC 63563-1:2025 introduces the Qi Specification, which applies to flat surface devices such as mobile phones and tablets that use up to 15 W of power
- Standard18 pagesEnglish languagesale 15% off
IEC 63563-3:2025 identifies basic physical design requirements and guidelines for Power Transmitter and Power Receiver Products, including product and system dimensions, alignment of the products, surface temperature rise, and indications to the user.
- Standard17 pagesEnglish languagesale 15% off
This document specifies the hardware requirements needed to carry out building automation tasks.
This document is applicable to physical devices, i.e.:
— devices that require human interaction, such as management stations or operator panels;
— devices for data storage and analysis, such as edge or cloud servers;
— devices for control applications, such as automation stations;
— devices for physical quantities acquisition, such as sensors and actuators.
This document provides a generic system topology based on a building network infrastructure, which includes both the devices inside the building envelope and those outside the building envelope.
- Standard22 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements for data exchange at the interface between earth-moving machinery, as defined in ISO 6165, mobile road construction machinery, as defined in ISO 22242, and the worksite information systems. It focuses on data for management of a worksite and the assets specific to that worksite. This document includes: a) methods of local position correction and localization, including standardization of RTK corrections; b) method of implementation of a common design model; c) types of data and methods of data exchange between servers. This includes application programming interfaces (APIs) to exchange data between servers regardless of vendor. These APIs focus on project data, as-built data, and production data. Field-equipment-to-server and machine-to-machine are not included. This document covers both hardware mounted on earth-moving equipment and field measurement equipment. This document does not define methods of on-machine data collection, on-machine communication protocol (e.g. CAN bus), wireless transmission of data to the vendor’s server, or wireless transmission of data directly between machines onsite. This document also does not include design software requirements or other areas related to building information management (BIM). Data formats and transfer methods from design software to the SMS are not in scope.
- Technical specification182 pagesEnglish languagesale 15% off
- Technical specification191 pagesFrench languagesale 15% off
This document analyses challenges, considerations, and potential benefits of blockchain and distributed ledger technology (DLT) in relation to records management standards and related standards for systems that: — create records that are required to be authoritative records; — can be used as records systems; or — can be used for records management, including records controls. The target audience of this document includes records managers and allied professionals, IT professionals and application developers, legal and compliance professionals, researchers, educators and other interested parties.
- Technical report33 pagesEnglish languagesale 15% off
- Technical report33 pagesEnglish languagesale 15% off
This document specifies the simple HES gateway, which is one of a set of physical classes introduced in ISO/IEC 15045-1:2004
- Standard13 pagesEnglish languagesale 15% off
This document specifies a set of physical classes for the HES gateway system. It also specifies the requirements of HES gateway modules including home area network interface modules, wide area network interface modules, binding map service and service modules for any class chosen.
- Standard22 pagesEnglish languagesale 15% off
ISO/IEC 15045-4-1:2024 specifies a set of physical classes for the HES gateway system. It also specifies the requirements of HES gateway modules including home area network interface modules, wide area network interface modules, binding map service and service modules for any class chosen.
- Standard22 pagesEnglish languagesale 15% off
ISO/IEC 15045-4-2:2024 specifies the simple HES gateway, which is one of a set of physical classes introduced in ISO/IEC 15045-1:2004
- Standard13 pagesEnglish languagesale 15% off
ISO/IEC 15045-3-1:2024 describes the series of privacy, security, and safety standards to support the HES Gateway and attached devices. The purpose is to specify methods for protecting home and building systems from both internal and external threats, intrusions, or unintended observation of data and unsafe conditions that could result from network functions. Part 3 defines a set of basic and advanced requirements for gateway monitoring and control of both inbound and outbound traffic, including switching/routing, addressing, encryption, intrusion detection and prevention, and other “firewall” functions.
The Part 3 requirements specify the following functions:
1) prevention of active inbound attacks and unsafe commands,
2) discovery and classification of outbound traffic,
3) interoperability of premises internal network traffic,
4) management of privacy and security mechanisms, and
5) provision for a management and reporting dashboard for use by the non-technical end-user.
This standard describes the inter-relationships between privacy, security, and safety.
- Standard39 pagesEnglish languagesale 15% off
- Standard22 pagesEnglish languagesale 15% off
ISO/IEC 15045-3-2:2024 specifies cybersecurity requirements for protecting the privacy of premises and personally identifiable information through the use of the HES gateway and related HES standards. This document applies a set of principles including those specified in ISO/IEC 29100 that are applicable to the HES gateway such as consent, purpose legitimacy, collection limitation, data minimization, retention, accuracy, openness, and individual access.
- Standard29 pagesEnglish languagesale 15% off
This document gives a curated, factual knowledge about the past at a human scale. It specifies all information required for the exchange and integration of heterogeneous scientific and scholarly documentation about the past at a human scale and the available documented and empirical evidence for this.
A more detailed and useful definition can be articulated by defining both the intended scope, a broad and maximally-inclusive definition of general application principles, and the practical scope, which is expressed by the overall scope of a growing reference set of specific, identifiable documentation standards and practices that this document aims to semantically describe, restricted, always, in its details to the limitations of the intended scope.
The practical scope of this document is expressed in terms of the set of reference standards and de facto standards for documenting factual knowledge. This document covers the same domain of discourse as the union of these reference standards; this means that for data correctly encoded according to these documentation formats there can be an ISO 21127-compatible expression that conveys the same meaning.
- Standard195 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard190 pagesEnglish languagesale 15% off