Connect Brick models to data with Scout

A Brick model describes spaces, equipment, points, and their relationships. Scout can start from the model to find missing data associations or use discovered data to propose point and property corrections.

Prerequisites and Inputs

• An approved Brick model representing the actual scope
• Confirmed MDM asset identities
• Time-series asset properties with defined units
• Active DFS field bindings to associate
• Appropriate Scout, model, MDM, and DFS read, write, review, or publication permissions

If the model list is empty, create or import the model at /platform/brick-schemas, connect its equipment and points to existing assets, and then refresh the list in Scout.

1. Create a model-scoped check

1. In Scout, select New equipment data check.
2. Select a business objective or Explore available data.
3. Choose By semantic model, then select the model name and version.
4. Review associated assets, point counts, evidence category, and time range.
5. Create the task.

The task preserves the model version selected at creation. After a new model version is published, create a check for the version that requires validation.

2. Review assets and existing fields

Open Existing data fields under Data associations. Review asset, property, unit, and binding status page by page. Select Return to source investigation when further discovery is required.

An empty list usually indicates that model nodes are not yet connected to assets, assets have no DFS bindings, the task scope is too narrow, or the user lacks read permission. Ask the model or data owner to correct the condition and refresh the task.

3. Prepare model draft changes

Select a model draft under Configure model points. If the current version has no draft, enter a new draft version and select Create draft.

For an existing point, select the point, confirmed MDM asset, and actual asset property:

• Save point property to draft updates the current draft for an operator with model-edit permission
• Submit property correction for review creates a proposal with field evidence and rationale

To add a point, choose Missing point, its asset, the actual property, and a compatible point class. Enter a clear name, field evidence, and rationale, then select Submit new point for review.

Compatible classes come from the ontology catalog used by the current model version and are filtered by the property unit. If the list is empty or truncated, ask the model administrator to review the unit, catalog version, and pagination scope.

The reviewer uses Model changes to inspect supporting evidence, contrary evidence, and open questions. After accepting a proposal, select Apply to model draft, then use Check updated draft to create a validation task.

4. Associate model points with DFS fields

Under Associate model points with data, select a named point and an existing DFS field with matching asset, property, and unit. Assign a source role:

Source role	Use	Enter or verify
LIVE	Continuously observed source	Recent reading, observation time, and freshness
BACKFILL	Source for a defined historical interval	Complete start and end time, and observed historical coverage

Times entered in the browser use the local time zone and are submitted as UTC. Explain the asset, property, location, and source evidence for the association, then submit it for review.

5. Preview and publish

1. In Publish point associations, select accepted proposals.
2. Add associations, replace named associations, or select associations for removal. Other active associations remain in place.
3. Select Preview and validate publication and review the model draft plus additions, replacements, retained items, and removals.
4. Have an approver approve the current valid plan.
5. Have a different release operator apply the approved plan.

Publication scope

Joint publication applies the selected model draft and publishes references from model points to existing active DFS field bindings. Connector configuration, ingestion, and application enablement continue in their respective workflows.

When the model, identity, or field binding changes, generate a new preview and obtain approval for that version.

6. Verify results and recover

In Results, review the active model version, published associations, source access, recent readings, and historical coverage. Use Check source readings to inspect values and observation time. Use Export Brick reference to download the Turtle reference for the active model version.

For recovery, select Check recovery options, choose a target returned by the service, enter the reason, and run Restore previous publication. Recovery creates a governed publication that restores model and reference state. Source data and ingestion settings remain under their owning systems.

Troubleshoot Blocked Tasks

Blocker	Action
Model or associated assets are unavailable	Prepare the actual model and connect existing assets in model management
Asset identity or property needs confirmation	Ask the MDM or model owner to confirm it, then refresh options
No compatible point class	Review property unit, ontology catalog version, and pagination scope
Model or binding changed during review	Refresh evidence and validate the current version again
Publication failed or timed out	Read the existing result, then use a recovery option returned by the service

Example

A pump has a temperature property but its Brick model has no corresponding point. An engineer confirms the asset, property, unit, and measurement location and submits a new-point proposal. A reviewer accepts it and applies it to the draft. The engineer then associates the point with an existing DFS temperature field. After independent approval and publication, the team verifies actual readings and records the model version, data reference, supporting evidence, and observation time.