DFS Workflows

Use workflow guides when a DFS rollout spans multiple product areas or teams. A workflow page shows the sequence from source connection to governed output, including when to use DFS Lite, when to promote data into DFS Pro, and where reviewer decisions are required.

Workflow selection flow

Before you start

Prepare the downstream workflow, source owner, data reviewer, target identity, expected fields, and acceptance criteria before choosing a workflow guide.

Available workflows

Workflow	Use when
Lite to Pro Operational Pipeline	A connector feed needs to become a governed data asset for Inspector, FactVerse AI Agent, BI, predictive maintenance, or other repeatable operational workflows.
Prepare DFS Data for AI Agent Workflows	An Agent workflow needs source data, stable identity mapping, quality notes, governed datasets, fusion review, and a handoff record before validation.

Workflow checkpoints

Before using a DFS workflow in regular operations, confirm:

• the source is reachable and ownership is clear;
• mappings use stable target identities;
• sync history and data quality are reviewed;
• governance ownership is assigned where reusable datasets are created;
• uncertain rows, conflicts, and rejected rows have a review path;
• the consuming FactVerse workflow has acceptance criteria and handover records.

Expected outputs

Output	Why it matters
Evidence contract	Defines source systems, target identity, timestamps, units, owner, and accepted use.
Connector and mapping record	Shows how source values become operational fields.
Quality and sync note	Explains whether the data is fresh, complete, and acceptable for the use case.
Dataset or fusion output	Provides a reusable governed data asset when the workflow needs repeatability.
Handoff record	Gives Inspector, AI Agent, BI, or Physical AI reviewers the source context and limits.

Handoff standard

Do not treat a DFS workflow as complete when data merely appears in a table. The handoff should name the source owner, data steward, downstream workflow owner, latest successful sync, known quality issues, and reviewer decision. This keeps later Agent, Inspector, BI, or simulation work from guessing where the data came from or whether it is current enough for the task.

For workflows that stay in DFS Lite, the handoff can be a connector, mapping, sync, and quality note. For workflows promoted to DFS Pro, include dataset version, lineage, validation state, fusion task, and unresolved review items.

Use the same handoff standard when the consuming workflow is still in pilot, because early ambiguity becomes production support debt quickly.

Related pages

Page	Use
Getting Started with DFS	Verify a small connector-to-quality loop before running a broader workflow.
DFS Lite	Connect source systems and map source data.
DFS Pro	Govern datasets, fusion tasks, review queues, pipelines, and BI outputs.
DFS Recipes	Follow task-oriented examples for common operating scenarios.