Table 2

EC derived through literature review for CCDT

Engineering characteristicsExamples
Public goodOpen access to non-sensitive data (EC1)Access to information on city-related issues without exposing the sensitive data of the person posting the issues (Nwogu et al., 2022)
Shared access with approved users (EC2)Have specific access controls and restrictions on the use of data among providers and users (Haße et al., 2022)
StandardsA vendor-neutral platform built based on an open Application Processing Interface (APIs) (EC3)Integrating an API that conforms to the design architecture of the representational state transfer architectural style (Ibm, 2023)
User-friendly and easy of navigation graphical user interface (EC4)Designed with clarity of the layout and easy to navigate between the layouts (Lim and Chin, 2023)
Comment management automates comment analysis and is compliant with federal laws (EC5)Trends in comments posted related to infrastructure (Xu et al., 2019; Bouchrika, 2023)
QualityMeet the minimum necessary data quality standard (EC6)Meeting the requirements of ISO 8000, which is the global standard for Data Quality and Enterprise Master Data (Goknil et al., 2023)
Use of hardware camera (EC7)To facilitate image capturing and object detection for assessing the impact of an issue (White et al., 2021; Han et al., 2019)
Use of hardware GPS (EC8)Tracking locations when posting issues (Han et al., 2019)
Links to transportation APIs (EC9)Integrating real-time location and transport information for public transport (Yoon and Park, 2022)
OpennessComprise open or shared data supported by open standards (ANZLIC, 2019) (EC10)Use of CityGML, which is an open standardised data model to store 3D city models (Ruohomaki et al., 2018)
Security and privacyBuilt based on security and privacy-preserving principles (EC11)Using data encryption to protect confidential data in the system (Damjanovic-Behrendt, 2018)
A standardized approach for authorization access to data (EC12)Using data encryption to protect confidential data in the system (Damjanovic-Behrendt, 2018)
Provide access based on the user-defined role (EC13)Privacy-Preserving Identity and Access
Management for federated login (Damjanovic-Behrendt, 2018)
Facilitate the protection of sensitive and confidential data (EC14)Using data encryption to protect confidential data in the system (Damjanovic-Behrendt, 2018)
CurationHave clear ownership to support the governance and ongoing developments (EC15)The digital twin can be governed by the government, industry research or the community (ANZLIC, 2019)
Workflow automation (EC16)Routing of submitted forms/labels/comments for departmental processing (Bouchrika, 2023)
AdaptationData in CCDT can be managed in consistent, interoperable, cross-platform and platform-agnostic ways (EC17)Integrating an API that conforms to the design architecture of the representational state transfer architectural style (Ibm, 2023)
ValueFacilitates data integration by allowing the upload of data coming from different sectors and institutes (EC18)Individual actors agree on using common semantic standards (Haße et al., 2022)
On-demand data synchronization for real-time or non-real-time data (EC19)Condition monitoring where undesirable events should be detected immediately (Haße et al., 2022)
communication between the physical and the virtual part with a simultaneous data flow between them (EC20)Integration of city components (traffic lights, transport network) with the virtual model (White et al., 2021)
Federated modelCapable of integrating with other devices such as a crowdsourcing mobile app to share information (EC21)Using crowdsourcing to extract additional information (Fan and Yucheng, 2020)
Integration of machine learning models allowing predictive analysis (EC22)Object detection to perform analysis on environmental degradation
Source(s): Created by authors

or Create an Account

Close Modal
Close Modal