How would you model a single Data Object with multiple Systems of Record in Blueprint to ensure accurate sizing?

Example scenario:

• Data Object: Account
• System 1 provides name, address, etc.
• System 2 provides E# and CustomerID

Given Blueprint’s current data and integration design of associating one SoR directly to a DO, how would you design this?

• Option 1: Create one DO, associate the primary SoR, use notes for details, then add the second SoR under SoRs in Blueprint (bottom of screen)
• Option 2: Create two DOs (Account – System 1 and Account – System 2), each tied to its respective SoR

Curious how you all approach this in your designs.