Hi Jay,

You should develop your "Semantic Model B" inside the "Semantic Model A", because as both Ram and Gayathri said only a single semantic model can be deployed at a given time on a server.

If you look into your semantic model, you see it is split in layers: physical, logical, presentation. You can see this as 3 vertical separated layers (the vertical 3 windows split is the historical view of the model administration tool you can install on your Windows environment to develop models).

What you should do is to work with it like if it is also split horizontally. You can have multiple physical databases, schemas, objects in the same semantic layer. They can be shared or fully isolated. You just need to adopt a proper naming convention to keep your model clean.

Then you do the same for the logical model: you can define multiple logical models in the same semantic model, or you can build a "giant" single logical model (this choice depends on your data, your needs etc.).

And where the horizontal split really happen (if you used the same physical database and a unique large logical model), is in the presentation layer: you create separate subject areas, by topic usually.

In this way, in your single semantic model, you can have multiple subject areas that are accessible when you want to use them in a DV workbook for example.

Your Semantic Model A and Semantic Model B should both still be in DV, but only one is "active" (deployed). If you don't have conflicting object names, you can merge them (for example pushing both the same git repo and doing a merge, or by copy/pasting the JSON definition of one into the other etc.).

PS: support for multiple semantic model/rpd is on a roadmap for a number of years, don't expect to see it soon, you will need to merge your 2 semantic models together and do your future work into a single one for a number of months, or years…