Skip to main content
Data Products are views maintained by First Resonance that pre-join and aggregate common queries, so you don’t rebuild the same multi-table joins in every dashboard. Each data product is delivered as a queryable view inside the Data Connector. Use them as the source for your BI dashboards, such as Power BI, Tableau, Looker, or Sigma, or for downstream pipelines. Refresh latency follows the standard Data Connector SLAs.
Data Products are part of the Data Connector offering. If you don’t see them in your warehouse yet, contact your Customer Success Manager about enabling the Data Connector for your organization.
Data Products are the computed tier of the Data Connector. For the raw and cleaned (_enriched) tiers, a near 1:1 replica of every ION entity, see Available tables.

All data products

The complete set of computed views available through the connector. The most commonly used products are documented in detail below.
The set available to your organization depends on which ION features you use. A data product for a feature you don’t use returns no rows.

Kitting data products

These data products cover parts, substitutions, inventory, and fulfillment in the kitting process.

part_kit_item_fulfillment

Unique key: (part_kit_id, part_kit_item_id) Fulfillment status for each item in a kit. It joins the part_kit structure with the individual part_kit_items and tracks whether each component has been sourced, picked, staged, or installed. Use it to monitor kit readiness and find staging or fulfillment bottlenecks before work begins.

part_substitutes

Unique key: (part_id, substitute_part_id, mbom_item_id) Approved substitute parts for a given part_id within the context of a specific mbom_item_id. It merges two sources of substitution logic: engineering-driven mBOM alternatives and operations-driven part interchangeability mappings. Planners and operators use it to choose a substitute when the primary part is unavailable or low in inventory.

part_quantities_by_inv_status

Unique key: (part_id) Current inventory for each part, grouped by inventory Status (Available, Quarantined, Installed, and others). It shows how much of each part is usable versus allocated, blocked, or consumed. Join it with demand metrics to flag low-availability parts.

BOM data products

full_bom

A flattened, multi-level BOM rollup for fast querying of supply chain and planning data. Dashboards that previously joined the BOM tree at query time, such as Clear to Build, can read directly from full_bom for faster load times. To use Notable Assembly with full_bom:
  • Define a “Notable Assembly” attribute at the part library level (text or single-select).
  • Populate the attribute on the parts you want flagged.
  • Configure the attribute name in your Clear-to-Build reporting setup.

manufacturing_readiness

Unique key: (top_level_part_id, part_id, inventory_part_id) mBOM readiness for each assembly: what the build requires, what’s available, what’s short, and how many complete builds the parts on hand allow. Junction tables such as purchase order lines and kit items are aggregated before the join, so a required part stays one row per assembly. Use it for Clear to Build reporting when the demand comes from mBOMs. When the demand comes from Autoplan instead, use build_status or autoplan_results_by_plan_input.

Purchasing data products

These data products cover purchase orders, receiving, and supplier delivery performance.

purchase_order_tracker

Unique key: (purchase_order_line_id) One row per purchase order line, with the receiving and inventory joins already done and the common measures already calculated: whether a line is open, whether it’s past due and by how many days, the quantity and percentage received, the value still outstanding, and the supplier’s on-time delivery rate and average lead time. Use it for supplier scorecards, open-order reports, and past-due queues without joining purchase orders, lines, receipts, and inventory yourself. Receipts and inventory links are aggregated per line, so a line that was received in three shipments is still one row.

purchase_order_receipts

Unique key: (receipt_item_id) One row per line received, with the part, supplier, and purchase order context attached. Use it to analyze receiving activity over time. To report on ordering rather than receiving, use purchase_order_tracker.

Inventory data products

inventory_health

Unique key: (part_inventory_id) One row per inventory record, with its part, location, status, and cost, plus the purchase order line it came from. Use it for inventory valuation and on-hand reporting.

inventory_expiring

Unique key: (part_inventory_id) Inventory records that carry an expiration date, each bucketed by how close that date is to today. Records with no expiration date are excluded. Use it to find stock that needs to be consumed or scrapped.
The expiration buckets are calculated against the date the query runs, so a record moves between buckets over time and a saved result doesn’t stay accurate.

inventory_reorder_tracking

Unique key: (part_id, revision) Reorder position for each part revision, combining on-hand and on-order quantities with demand. Use it to decide what to buy next.

Issue data products

These data products cover manufacturing issue tracking, triage, and resolution. They unify run, step, part, and supplier context with workflow signals such as labels, redlines, related issues, and approvals.

issue_details

Unique key and grain:
  • Primary grain: one row per issue (issue_id).
  • When an issue is linked to part inventory or PO line information, the grain expands. In those cases, treat the compound grain as (issue_id, part_inventory_id, purchase_order_line_id).
  • If your dashboard expects one row per issue, either filter to the desired part or PO context, or aggregate back to the issue level.
A pre-joined dataset that centralizes the most commonly used fields for issue analysis: assignment, lifecycle timestamps, run and step context, related parts and inventory, supplier and PO traceability, labels, redlines, related issues, approval-based resolution date, further-action rollups, attachments, and freshness signals such as days since last update. Use it for issue queues, SLA tracking, and continuous-improvement dashboards.