Hi @Stefanie Culley, Having a HUB where the Business keys are derived from business rules can add performance benefits using your data and it gives you a standard approach to using and managing this data. It will allow you to hang as many satellites as you need or want for testing, prototyping or reporting. A very good thing to have in my opinion. I'm not convinced you need to give this hub a special BV name or keep it separate from your other hubs. For now, your hub may only contain keys derived from business rules, but what happens if a new source system is built/acquired/ingested that contains these business keys. You would want the business keys from this new source system to be in the same HUB - they are the same business keys. But now your hub would have both RV and BV data, would you change the name and move it from the BV schema or leave it there? If a BV hub can end up with some RV business keys and vice versa what becomes the definition of a BV/RV hub? Satellites don't have this issue - just create another satellite - but we don't want multiple Hubs for the same business key. I tend to think that all Hubs should live in the RV space, they hold the business keys for the business entity - it doesn't matter where the keys come from.