Create governed, reusable data products with stable data interfaces that unify data across systems—so teams can discover, access, and act on trusted data without moving it.
Business-entity–centric packaging (Customer360, Billing, etc.) • Reusable, discoverable assets in the data catalog • Clear ownership & lifecycle management • Multi-source composition (external + ServiceNow + derived) • Interface-driven access (no direct table coupling)
1. Data Interfaces (Stable Data Contracts) • Define Data Interfaces (DI) as durable, schema-based contracts over data • Unified SQL-based access across external and ServiceNow data sources • Support for multi-source composition (e.g., unions, DBView-backed joins) • Late binding to underlying data sources for flexibility • Backward-compatible interface evolution (additive schema changes) ⸻ 2. Data Products (Governed Data Assets) • Create Data Products (DP) as reusable, business-aligned data entities • Package one or more Data Interfaces into a single governed asset • Define ownership, lifecycle, and metadata for each Data Product • Enable discoverability via Data Catalog integration • Provide a consistent access layer for consumers (analytics, workflows, AI) ⸻ 3. Zero-Copy Data Access (Data Fabric Tables) • Leverage Data Fabric Tables (DFTs) for zero-copy access to external data • Query data in-place using federated access (Trino-based) • Avoid data duplication while enabling real-time or near-real-time access • Support external sources such as Snowflake and Databricks • Enable pushdown query execution to optimize performance ⸻ 4. Governance and Access Control • Integrate with ServiceNow ACL and role-based access control models • Enable controlled access to Data Interfaces and Data Products • Support request-based access workflows (via catalog) • Ensure governed exposure of underlying data sources • Lay foundation for future policy-driven governance and masking ⸻ 5. Catalog-First Authoring Experience • Discover data assets through Data Catalog integration • Create Data Interfaces and Data Products starting from catalog assets • Define schema mappings and transformations during authoring • Improve reusability and reduce duplication of effort
Requires Australia early access or GA.