Enterprise and solution data models: should solution views map to enterprise containers?

We’re designing a layered data model in Cognite Data Fusion and would like to hear how other teams handle the boundary between enterprise and solution models.

Our current approach is:

• Enterprise layer: Create domain views that use implements: to extend relevant CDM or IDM views, with enterprise-owned containers for our domain properties.

• Solution layer: Create application-specific views that map properties directly from enterprise containers, instead of implementing enterprise views. The intent is to let each solution shape its own consumption interface while reusing the underlying data.

We’re considering enterprise containers as the longer-lived storage contract and views as versioned interfaces for different consumers. Cognite’s guide to designing scalable data models appears to support direct container mappings for solution views.

For teams using this pattern in production:

1. Do your solution views map directly to enterprise containers, implement enterprise views, or use a mix? What drives that choice?

2. If a solution view maps directly to containers, how do you keep inherited CDM/IDM properties, relationships, and filters consistent with the enterprise view?

3. How do you govern changes to shared containers and coordinate version changes across enterprise and solution views?

4. When a solution needs to create or update data, where do you place its own containers and write-back model?

A concrete example or a lesson learned from a deployed model would be especially helpful.