Introduction

Scenario: The supply-chain lead wants a daily board showing late shipments, high-risk suppliers, and inventory exposure.

Day 04 turns the ontology you have been building into operational analysis surfaces. The supply-chain lead does not want raw datasets; they want a daily board that answers three questions at a glance: which shipments are late, which suppliers are high-risk, and where inventory exposure is concentrated. Foundry serves this through Object Views, the reusable central hub for everything related to a single object, and through Object Explorer, the search-and-analysis tool for answering questions about anything in the Ontology by building and refining object sets. Because both surfaces read directly from object-type configuration and the links you have defined, the analysis stays live and tied to the underlying data and permissions model rather than to a stale extract.

Today you will combine four documented capabilities. Object Views give each Shipment and each Supplier a contextual page that surfaces properties, linked objects, and embedded visualizations. Object Explorer lets you assemble the late-shipment object set with simple keyword search or full property filters and save it so it auto-refreshes with new data. Quiver, Foundry's point-and-click, no-code interface for object and time-series data, lets you visualize and transform that set and 'search around' links to pull connected suppliers without writing joins. Finally, Quiver dashboards render a read-only, interactive view that embeds straight into an Object View or Workshop app for the lead.

This matters to the disruption-response problem because operational decisions during a disruption happen on the clock. A configured Object View becomes the default landing experience for a supplier or shipment, putting risk indicators next to the actions a responder can take, while saved object sets and embedded dashboards mean the lead sees today's late shipments and exposed inventory without rebuilding anything. You are moving from data engineering to decision support.

Capability focus: Object Views, object sets, Quiver dashboards, analytics · Artifact: Analyst-ready risk dashboard

Key concepts

Companion video

1. 1

   Create object views for shipment and supplier risk

   Every object type already has a standard Object View auto-generated from its configuration, but for the disruption board you will build configured Object Views in Workshop so they become the default landing page for Shipment and Supplier objects. Lay out each view to surface the risk-relevant properties (delay status, ETA, risk score) alongside linked objects, so a responder opening a single late shipment immediately sees its supplier, origin, and affected inventory. Add a panel Object View variant for Supplier so the streamlined risk summary can later embed inside the shipment view, keeping the standard view available as a fallback.

   not startedself-attested

   Mark complete

   Self-attested: object-view configuration is not exposed by a read API (instructor-checked).

2. 2

   Configure the late-shipment object set

   Open Object Explorer and build an object set over the Shipment object type using property filters, for example status equals delayed or actual-delivery later than promised ETA, refining the set until it captures exactly today's late shipments. Save the exploration so it automatically shows updated results as new shipment data lands, giving the lead a self-refreshing daily list rather than a one-time snapshot. Confirm the set can be opened in Quiver and is reusable, since you will feed it into the supplier and dashboard steps next.

   not startedinstance check

   Run check

   Confirms an aggregation reproduces the expected count of late shipments.

3. 3

   Surface high-risk suppliers

   Open your late-shipment object set in Quiver and use 'search around' to traverse the Ontology links from shipments to their suppliers, pulling in connected suppliers without writing any joins. Apply Quiver's no-code transforms and formula language to rank suppliers by frequency of late shipments and inventory exposure, then visualize the result as a chart or table to isolate the high-risk tail. Because Quiver can write back through Actions, you can optionally flag a supplier's risk tier on the Supplier object so the rating persists in the Ontology and shows on its Object View.

   not startedinstance check

   Run check

   Confirms an aggregation reproduces the count of high-risk suppliers.

4. 4

   Prepare a three-minute risk walkthrough

   Publish your Quiver analysis as a read-only, interactive Quiver dashboard showing late shipments, ranked high-risk suppliers, and inventory exposure, then embed it into the Shipment Object View or a Workshop app so the supply-chain lead reaches it in one place. Rehearse a tight three-minute narrative: open on the late-shipment count, drill into the top high-risk supplier, and end on the exposed inventory the lead must act on. Confirm the embedded dashboard refreshes from the live object set so the walkthrough reflects today's disruption, not a stale export.

   not startedself-attested

   Mark complete

   Self-attested: your walkthrough tells a coherent risk story.