Llogari Casas Cambra
1) To carry out a gap analysis on standards related to City Information Modelling and Urban Digital Twins;
2) To use the gap analysis to develop requirements for the standards needed for the implementation of City Information Modelling and Urban Digital Twins;
3) To develop those standards relating to City Information Modelling and Urban Digital Twins that are within its competence, including a reference architecture that takes into account the differing perspectives of City Information Modelling and Urban Digital Twins.
Note for information:
1 The Joint Working Group is not expected to develop many standards itself, but rather through a process of use case/case study collection, the development of an integrated reference architecture, and standards mapping, to identify the gaps in existing standards and support the relevant specialist technical committees to address these.
2 The reference architecture is intended to be coherent with ISO/IEC 42010 and the developing work on Smart Cities Reference Architecture (IEC 63205), the Digital Twin Reference Architecture (ISO/IEC 30188), the IoT Reference Architecture (ISO/IEC 30141 Ed2) and other relevant standards.
This document defines minimum specific elements required for BIM process with new lifts. It does not define the BIM process itself. This document specifies a minimum set of information for lifts following the structure of ISO 7817-1, for the purpose of building planning during pre-design stage, schematic design stage and detailed design stage of a building. It covers the geometrical information and the alphanumerical information.
NOTE: The BIM processes are defined in ISO/TC 59/SC 13 standards.
This document does not cover requirements during other stages (information delivery milestones) and the documentation.
This document does not cover definition of actors, which are project specific.
The definitions are for a single lift. This document does not describe the structures required for multiple lifts in the same building.
This document describes the information of a lift and its interfaces to the building which are relevant for the planning of the building. The structural forces are out of the scope of this document.
This document is not applicable to lifts, which are installed before the date of its publication.
This document specifies cybersecurity requirements for new lifts, escalators and moving walks, referred to in this document as “equipment under control (EUC)”, designed in accordance with the ISO 8100 series. It is also applicable with other lift, escalator and moving walk standards that specify similar requirements, and to other lift-related equipment connected to the EUC.
This document specifies product and system requirements related to cybersecurity threats in the following lifecycle steps:
— product development (process and product requirements);
— manufacturing;
— installation;
— operation and maintenance;
— decommissioning.
This document addresses the roles of product supplier and system integrator as shown in IEC 62443-4-1:2018, Figure 2, for the EUC.
This document does not address the role of asset owner as shown in IEC 62443-4-1:2018, Figure 2, but defines requirements for the product supplier and system integrator of the EUC to establish documentation allowing the asset owner, referred to as the “EUC owner” in this document, to achieve and maintain the security of the EUC.
This document specifies the minimum cybersecurity requirements for:
— essential functions;
— safety functions;
— alarm functions.
This document is applicable to EUCs that are capable of connectivity to external systems such as building networks, cloud services, or service tools. The capability to connectivity can exist through equipment permanently available on site, or equipment temporarily brought to the location during the installation, operation and maintenance, or decommissioning steps.
EUC interfaces to external systems and services are in the scope of this document. External systems and services as such are out of the scope of this document.
This document does not apply to EUC that are installed before the date of its publication.
Scope of the technical specification is to define ontology for the interoperability covering following use cases: Remote monitoring of the lift system Remote call registration Building automation interfacing Robot interfacing (AGV and MAR). The document also specifies safety related functions and aspect related to interoperability. In the document, oneM2M and OPC UA are used as examples how to apply the ontology.
This document covers means for software code and software configuration updates for lifts, escalators, and moving walks (EUC). Both on-site and remote updates are covered. This document does not apply to EUC that are installed before the date of its publication.
This document specifies for passenger lifts and goods passenger lifts:
This document is not applicable to passenger lifts, goods passenger lifts or lift components, which are installed or manufactured before the date of its publication
This document specifies the safety rules for lifts permanently serving buildings and constructions and intended for the transport of persons or persons and goods. It applies to traction lifts, positive drive lifts and hydraulic lifts that:
This document also applies to the electrical equipment of these lifts including the lighting and socket outlets in the well.
This document specifies safety rules related to:
This document does not specify additional requirements for:
This document is not applicable to passenger and goods passenger lifts, which are installed before the date of its publication.
This standard offers practical guidance on integrating health and wellbeing into community development efforts, with a specific focus on aligning with ISO 37101's sustainability goals. It is designed to help local governments, organizations, and communities implement strategies focused on health, that promote wellbeing, physical, mental, social, and environmental health aspects. The scope of the standard covers the entire lifecycle of health and wellbeing management, from policy development to continuous improvement. It provides a framework for establishing health-promoting policies, ensuring that health considerations are embedded in community planning, governance, and urban design. By applying the standard, organizations and communities can develop strategies for creating environments that foster both mental and physical health, reduce health disparities, and improve the quality of life for all residents. This standard emphasizes the importance of urban planning and infrastructure, encouraging access to green spaces, recreational facilities, clean water, and safe environments, all of which are essential for health. Very significantly, it integrates with the 12 key areas of action outlined in ISO 37101, such as governance, education, and community infrastructure, ensuring that health and wellbeing are considered across all sectors of development. The standard provides guidance on planning and implementing initiatives tailored to local needs, using evidence-based approaches to tackle health challenges. Ultimately, the scope is about creating a holistic approach to health and wellbeing that aligns with sustainable development principles. By offering actionable steps for integration, monitoring, and evaluation, the standard empowers communities to create healthier, more resilient environments that support long-term wellbeing for current and future generations.
The sectors of Digital Twins, Virtual Worlds/Citiverse, IoT and Data Spaces are fragmented, especially the uneven uptake of NGSI‑LD, Smart Data Models/SAREF and governance models creates a barrier for cross‑domain interoperability in cities. Therefore, I focus on harmonising these layers within ITU‑T Citiverse and EU Local Digital Twin (LDT) Toolbox. I also contribute to aligning LDT and Data Space governance with UNE 0087:2025 and the Gaia‑X Trust Framework to operationalise sovereignty, compliance and automated conformance. Moreover, I contribute to mapping LDT/MIM8, NGSI‑LD, SIMPL and Citiverse deliverables to speed deployment and avoid duplicate or conflicting specs.