The present document will provide a comparison between both internal and external 'cloud-based' solutions with a life cycle analysis addressing: aenergy consumption; b)green-house gas (GHG) emission; c)water consumption; d)waste management from production to end-of-life management.
The present document replaces TS 103463 and defines in greater detail a number of Key Performance Indicators (KPIs) for Smart Areas (both urban and rural) expressing sustainability performance in terms of People, Planet, Prosperity and Governance. Certain of the KPIs are grouped and presented as Global KPIs in TS 103 463-2.
This part of ISO 9735 specifies syntax rules for EDIFACT security. It provides a method to address message/package level, group level and interchange level security for authenticity, integrity and non-repudiation of origin, in accordance with established security mechanisms.
This document outlines the concepts and principles for information management at a stage of maturity described as "building information modelling (BIM) according to the ISO 19650 series". This document provides recommendations for a framework to manage information including exchanging, recording, versioning and organizing for all actors. This document is applicable to the whole life cycle of any built asset, including strategic planning, initial design, engineering, development, documentation and construction, day-to-day operation, maintenance, refurbishment, repair and end-of-life. This document can be adapted to assets or projects of any scale and complexity, so as not to hamper the flexibility and versatility that characterize the large range of potential procurement strategies and so as to address the cost of implementing this document.
This document establishes a framework for a trustworthy environment for information processing and communication that protects integrity along the supply chain of physical and related electronic documents, products, software and services life cycle to mitigate product fraud and counterfeit goods, by using object identification techniques.
This document gives guidelines to establish a framework for ensuring trust, interoperability and interoperation via secure and reliable electronically signed encoded data set (ESEDS) schemes for multi-actor applications which are even applicable in multi-sector environment.
This document does not interfere with existing traceability and identification and authentication systems but is able to support interoperations between them by introducing an ESEDS scheme.
This document specifies a process to qualify the suitability, reliability and effectiveness of artefact metrics as well as artefact metric recognition principles for identification and verification.
The artefact metric recognition described in this document can be used to identify or verify artefacts using one or more measurements of their characteristics, each of which is unique to an individual artefact and is supposedly impossible to reproduce.
This document is applicable to artefact metrics throughout the life cycle processes of products.
Measurement of the resilience of the system where the distinguishing characteristic is degraded is out of the scope of this document.
This document is applicable to performance testing of artefact metric systems and algorithms through analysis of the comparison scores and decisions output by the system, without requiring detailed knowledge of the system’s algorithms or of the underlying distribution of characteristics in the objects of interest.
This document excludes performance testing where deliberate attacks undermine the artefact metric system.
This document specifies the Visible Digital Seal (VDS) data structure. The document also specifies possible forms of representation, generation and verification processes applicable to Visible Digital Seals. This document contains support for future types of data encoding. All formats and processes are irrespective of the documents or objects they relate to. This document does not establish the requirements to implement and deploy VDSs, nor the detailed Response Formatting Functions (RFF).
The OpenAPI Naming and Design Rules technical specification defines an architecture and a set of rules necessary to specify, describe and implement APIs based on an OpenAPI specification to consistently express business information.
This document will provide guidance for developing, implementing, monitoring and improving infrastructure resilience in order to help ensure the continuity and effective outcomes of critical services. It can be used by any level of government, institutions, donors, infrastructure regulators, investors and owners, designers and contractors, service providers and international organizations.
This document gives guidelines for performance criteria and an evaluation methodology for authentication solutions that aim to unambiguously establish material good authenticity and integrity throughout an entire material good's life cycle. It focuses on the authentication of a material good and, if appropriate, its components, parts and related data:
— covered by intellectual property rights;
— covered by relevant international, regional or national regulations;
— with counterfeiting-related implications;
— otherwise with a distinctive identity.
This document is applicable to all types and sizes of organizations that require the ability to validate the authenticity and integrity of material goods. It will help organizations to determine the categories of authentication elements they need in order to combat counterfeiting-related risks, and the criteria for selecting authentication elements, after having undertaken a counterfeiting risk assessment.
Authentication solutions can be used in areas such as anti-counterfeiting, prevention of product fraud and prevention of diversion.
This document does not specify economic criteria aiming to correlate performance and costs of the authentication solutions.
This document gives guidelines for establishing interoperability among independently functioning product identification and related authentication systems, as described in ISO 16678. The permanent transfer of data from one system to another is out of the scope of this document.
It also gives guidance on how to specify an environment open to existing or new methods of identification and authentication of objects, and which is accessible for legacy systems that may need to remain active.
It is applicable to any industry, stakeholder or user group requiring object identification and authentication systems. It can be used on a global scale, or in limited environments. This document supports those involved in planning and establishing interoperation.
This document specifies three business requirements for the visibility of logistics traffic flow based on the use cases and gap analysis in Annex A. It includes
1) LISS network architecture requirements,
2) visibility data interchange requirements between LISSs, and
3) visibility data interface and process requirements for an LISS network.
These three business requirements are described further in Clause 6, Clause 7 and Clause 8 respectively.
Furthermore, Clause 8 describes the requirement for a guideline for business participants and stakeholders in an LISS network such as logistics information service providers, single window/SSP operators, data providers and logistics data users.
This document does not include standardization
1) at the level of logistics devices (areas of standardisation covered by ISO/TC 104, ISO/TC 204),
2) for ships, navigation and marine technologies (areas of standardisation covered by ISO/TC 8), or
3) related to international data exchange such as standards developed, published and maintained by UN/CEFACT, GS1, WCO which are referenced as appropriate in this document.
