Glossary
Key terms and concepts used throughout the DataHive documentation.
Organisations and Roles
For a full breakdown of roles and permissions, see User Roles.
| Term | Definition |
|---|---|
| Single Source of Truth (SSOT) | SSOTs are designated by Smart Nation and Digital Government Office (SNDGO) to collect the core data as part of the Government Data Architecture (GDA). See User Roles and IM Circular 5/2023. |
| Trusted Centre (TC) | An entity established as part of the Government Data Architecture (GDA) to aggregate, process, and distribute core data on behalf of multiple SSOTs. A TC operates as a Tenant on DataHive and is responsible for: formulating data requirements and standards for their domain, establishing SLAs with SSOTs, driving core data quality through data fusion and validation, processing and fusing core data for WOG use cases, managing data securely per GDD safeguards, facilitating data discoverability and acting as a data concierge, assessing and approving core data requests under PSGA, and driving data sharing across agencies. See IM Circular 8/2020. |
| Data Providing Agency (DPA) | An Agency that provides the data. This includes Agencies sharing their own data, or data which they had received from upstream data provider(s) and processed and/or transformed. See Data Provider guide and IM Circular 02/2026. |
| Data Consuming Agency (DCA) | An Agency that acquires the data from the DPA and uses it. See Data Requests guide and IM Circular 02/2026. |
| Non-Government Entity (NGE) | A third-party organisation outside of government that may receive data from DataHive under specific agreements and conditions. See NGE Data Sharing. |
| Chief Data Officer (CDO) | An officer who oversees data governance for an agency, including managing the CDO Team and tenants. See CDO Team Management. |
| Internal Approver (IA) | A designated officer within a DCA who reviews and approves or rejects outgoing data requests on behalf of their agency. IAs are assigned by the CDO or CDO Team Manager. See For Internal Approvers. |
| Tenant Manager (TM) | A user who oversees tenant-wide activities including managing users, approving fast-tracked datafields, and approving dataset lifecycle actions. See Tenant Management. |
| Tenant Admin (TA) | A user responsible for managing specific datasets within a tenant, including uploading data, publishing, and verifying incoming data requests. See Dataset Management. |
Platform Concepts
| Term | Definition |
|---|---|
| Tenant | An organisational unit on DataHive that manages datasets. A Tenant is normally a DPA - for example, a Trusted Centre operates as a Tenant managing Core Data, or an agency may self-publish and distribute its own datasets. See Tenant Management. |
| Data Request (DR) | A digital data-sharing request submitted by a DCA to access datasets. The data request on DataHive is based on the Standard Data Sharing Form (SDSF). See Data Requests and SDSF (IM8). |
| Core Data | Datasets that are collected, aggregated, and managed by a Trusted Centre on behalf of source agencies. |
| De-identified Data | Data that has been processed to remove or obscure direct identifiers, making it difficult to identify specific individuals. DataHive uses tokenisation (hashing) to de-identify data. See Datafields Hashing. |
| Tokenisation | The hashing process DataHive uses to de-identify personal data fields. A Key and Initialisation Vector (IV) are used to produce hashed values that cannot be reversed to reveal original data. See Datafields Hashing. |
| Fast-tracked Fields | Datafields that are to be approved by the Tenant Manager and do not require SSOT approval when requested. Non-fast-tracked fields require approval from the SSOT. See Approve or Reject Data Request. |
| Scope Filter | A datafield configuration that enables row-level data filtering, allowing requestors to specify which subset of data they need. |
| Reference Period | The time period for which statistical results or data are collected or calculated. The exact definition may vary depending on the dataset - check with the relevant DPA for specifics. |
| Concierge Service | An optional service where a Tenant Admin performs bespoke data processing (e.g. joins, aggregations) for a specific data request before fulfillment. See Data Request Approval. |
| System Connection | A non-interactive, service principal-based connection to DataHive's API or data warehouse for automated data access. See System Connection guide. |
| Data Lineage Records | An audit trail of dataset metadata changes and access events, downloadable by Tenant Admins and Managers. See Data Lineage Records. |
Legislation and Governance
| Term | Definition |
|---|---|
| PSGA | The Public Sector (Governance) Act 2018. Governs data sharing between public agencies in Singapore and provides the legal basis for PSGA Data Sharing Directions. (Learn more) |
| IM8 | The Infocomm Technology and Smart Systems (ICT&SS) Management policy that defines security requirements for government ICT systems. See IM Portal. |
Infrastructure and Access
| Term | Definition |
|---|---|
| Entra ID | Microsoft's identity platform (formerly Azure Active Directory) used by WOG for authentication into DataHive. See Sign In. |
| GSIB | Government Standard Image Build - a government-issued device used to access DataHive. |
| COMET | A cloud-based government device that can also be used to access DataHive. |
| SOE ID | Standard Operating Environment ID - your government login identity used for authentication. |
| GEN | Government Enterprise Network - the internal government network. |
| Service Principal (SPN) | A machine identity used for automated system-to-system connections to DataHive. See System Connection setup. |