Get Started with FactVerse Scout

This guide walks through a first data-readiness check using a small, well-understood equipment scope. Do not begin with an entire enterprise or plant.

Before You Begin

Confirm the following with your team:

• the application or use case you want to enable;
• a site, system, or equipment group small enough to review;
• access to the relevant source and asset definitions;
• the real provenance of the data you will use;
• a reviewer and approver/deployment owner.

Your tenant administrator must also enable DFS Pro and Scout and give you the appropriate role.

Inputs

Bring the business goal, a reviewable equipment scope, and the correct provenance label for the data. The application template and tenant inventory supply the internal requirement versions and stable IDs automatically.

Example Outcome

A reliability team wants to use vibration data for pump health analysis. At the end of the check, the team should be able to show:

• which pumps were reviewed;
• which vibration requirement was satisfied or missing;
• which source signal was matched to each asset attribute;
• who approved the match and why;
• whether the health application consumed the approved signal.

1. Open Scout

Open DFS / Data & Governance > Scout and select New check.

If Scout is not visible, ask the tenant administrator to check Administration. A copied direct link does not bypass access controls.

2. Choose the Goal and Equipment

The first step asks what capability you want to enable. For the current Predictive Maintenance template, Scout explains the outcome and shows the data it will look for:

• Required: vibration velocity RMS. Missing this signal blocks readiness.
• Recommended: bearing temperature. Missing it is visible but does not block the required result.

You do not enter application IDs, provider names, requirement versions, Twin IDs, or relationship depth. Scout uses the currently published application template and tenant inventory.

Select the equipment scope in one of three ways:

• By space: choose an existing site, building, or area.
• Select equipment: search by equipment name and select named assets.
• By equipment type: select pumps, motors, fans, compressors, or another type supported by the chosen goal.

If the required space or equipment is not listed, stop and correct the tenant asset inventory. Do not paste an internal identifier into another field.

3. Label the Data and Review

Choose the provenance that matches reality:

• Customer source: data received from the customer's connected system or equipment.
• Demo-derived: platform demonstration data, used only to demonstrate the workflow. Review the goal, scope, provenance, and expected output. Use a readable name such as Plant A pump data readiness - 2026-08-26, then create the check.

4. Review Readiness

The Mission page shows the current status, coverage, blockers, evidence date, and recommended next action.

Check the following before continuing:

1. The selected equipment and application requirement are correct.
2. The data provenance label matches reality.
3. The coverage count includes the assets you expected.
4. Missing and uncertain items are not shown as numeric zero.
5. Each blocker has an owner or a clear next action.

Refresh the assessment only after a source, asset definition, or requirement has materially changed. Previous assessments remain part of the review history.

5. Investigate a Gap

Use the Data gaps step in the Mission workspace and select a missing, partial, uncertain, or blocked item. Open technical details only when the summary is not enough for diagnosis.

Ask:

• Is the required asset attribute defined?
• Does the source contain a signal for it?
• Do the signal meaning, unit, channel, and equipment position agree?
• Is the source active and current enough for the application?
• Is business or source-owner approval required?

Some gaps should be resolved outside Scout, for example by granting source access or correcting an asset definition. Record the owner instead of forcing a match.

6. Propose and Review a Match

In the Mission's Data matches step, compare the ranked governed source signals with the target asset attribute. Review the name, equipment, topology, type, unit, freshness, and quality evidence, then accept, reject, or request more evidence. Internal source, schema, and mapping IDs are resolved by the platform.

The reviewer should accept only when identity, meaning, unit, provenance, and ownership are clear. Rejection is a valid outcome: it prevents an uncertain match from reaching an application and keeps the reason available for follow-up.

7. Validate, Approve, and Apply

After every required signal has an accepted match, continue in the same Mission workspace:

Validate samples -> Approve validation -> Review DFS changes -> Apply bindings

Validation performs a bounded read and does not change active bindings. The approver confirms the exact passing evidence. Before applying, Scout shows DFS create, update, and deactivate counts plus affected applications. DFS Mapping V2 and native point bindings remain the runtime authority; Scout does not publish a second runtime.

8. Confirm the Application Is Using the Data

Use Verify application readiness after the bindings are applied. Confirm that the readiness result shows:

• the active data binding;
• a readable observation window;
• the intended application installation;
• a consumption record and result;
• CANONICAL_TIMESERIES as the consumer source;
• the latest evidence time.

An empty result means the application result has not been verified. It must not be interpreted as a value of zero.

Validation Checklist

• Scope and owner are clear.
• Coverage includes the expected equipment.
• Every unresolved item has an owner.
• Accepted matches contain an understandable reason.
• Validation passed and the approval is recorded.
• The Mission readiness result identifies the application result and canonical consumer source.
• The provenance label still matches the actual source.

Continue with Operate a Mission for regular team handoffs.