Revision history [back]

I am creating some custom libraries of space types, schedules, and loads that I would like to save as a resource for multiple projects. From what I understand, the best way to do this is create a new OSM model, create all my 'library' content, and save the OSM to the typical library path for easy access (OpenStudio 1.7.0\share\openstudio-1.7.0\OSApp). I can then choose 'load library' in a new model to pull that content in.

This is a little open ended, but are there any tips or tricks to creating custom libraries outside of the process described above? Would I tap into the BCL at all, or simply create OSM model libraries and save them individually on my machine (as described above)? How have other OS users leveraged custom libraries to improve their workflow?

Lastly, all new OSM models seem to be populated with a library of DOE reference / ASHRAE 189.1 schedule sets, constructions, and space types. Is there any way to remove this extraneous content from a new model?

I am creating some custom libraries of space types, schedules, and loads that I would like to save as a resource for multiple projects. From what I understand, the best way to do this is create a new OSM model, create all my 'library' content, and save the OSM to the typical library path for easy access (OpenStudio 1.7.0\share\openstudio-1.7.0\OSApp). I can then choose 'load library' in a new model to pull that content in.

This is a little open ended, but are there any tips or tricks to creating custom libraries outside of the process described above? Would I tap into the BCL at all, or simply create OSM model libraries and save them individually on my machine (as described above)? How have other OS users leveraged custom libraries to improve their workflow?

Lastly, all new OSM models seem to be populated with a library of DOE reference / ASHRAE 189.1 schedule sets, constructions, and space types. Is there any way to remove this extraneous content from a new model?

I am creating some custom libraries of space types, schedules, and loads that I would like to save as a resource for multiple projects. From what I understand, the best way to do this is create a new OSM model, create all my 'library' content, and save the OSM to the typical library path for easy access (OpenStudio 1.7.0\share\openstudio-1.7.0\OSApp). I can then choose 'load library' in a new model to pull that content in.

This is a little open ended, but are there any tips or tricks to creating custom libraries outside of the process described above? Would I tap into the BCL at all, or simply create OSM model libraries and save them individually on my machine (as described above)? How have other OS users leveraged custom libraries to improve their workflow?

Lastly, all new OSM models seem to be populated with a library of DOE reference / ASHRAE 189.1 schedule sets, constructions, and space types. Is there any way to remove this extraneous content from a new model?

UPDATE: UPDATE ISSUE: Following up on the above... I loaded some space types, loads, and schedules into my model and applied the appropriate space types to each space in the facilities tab. After running the model and looking back, OS created a ridiculous amount of identical schedules and space types ('Example Schedule' got duplicated to 'Example Schedule 1', 'Example Schedule 2', 'Example Schedule 3', etc...). Any idea why this is happening and how to avoid the creation of mass duplicate schedules and space types? Thanks!

I am creating some custom libraries of space types, schedules, and loads that I would like to save as a resource for multiple projects. From what I understand, the best way to do this is create a new OSM model, create all my 'library' content, and save the OSM to the typical library path for easy access (OpenStudio 1.7.0\share\openstudio-1.7.0\OSApp). I can then choose 'load library' in a new model to pull that content in.

This is a little open ended, but are there any tips or tricks to creating custom libraries outside of the process described above? Would I tap into the BCL at all, or simply create OSM model libraries and save them individually on my machine (as described above)? How have other OS users leveraged custom libraries to improve their workflow?

Lastly, all new OSM models seem to be populated with a library of DOE reference / ASHRAE 189.1 schedule sets, constructions, and space types. Is there any way to remove this extraneous content from a new model?

I am creating some custom libraries of space types, schedules, and loads that I would like to save as a resource for multiple projects. From what I understand, the best way to do this is create a new OSM model, create all my 'library' content, and save the OSM to the typical library path for easy access (OpenStudio 1.7.0\share\openstudio-1.7.0\OSApp). I can then choose 'load library' in a new model to pull that content in.

This is a little open ended, but are there any tips or tricks to creating custom libraries outside of the process described above? Would I tap into the BCL at all, or simply create OSM model libraries and save them individually on my machine (as described above)? How have other OS users leveraged custom libraries to improve their workflow?

Lastly, all new OSM models seem to be populated with a library of DOE reference / ASHRAE 189.1 schedule sets, constructions, and space types. Is there any way to remove this extraneous content from a new model?

I am creating some custom libraries of space types, schedules, and loads that I would like to save as a resource for multiple projects. From what I understand, the best way to do this is create a new OSM model, create all my 'library' content, and save the OSM to the typical library path for easy access (OpenStudio 1.7.0\share\openstudio-1.7.0\OSApp). I can then choose 'load library' in a new model to pull that content in.

This is a little open ended, but are there any tips or tricks to creating custom libraries outside of the process described above? Would I tap into the BCL at all, or simply create OSM model libraries and save them individually on my machine (as described above)? How have other OS users leveraged custom libraries to improve their workflow?

Lastly, all new OSM models seem to be populated with a library of DOE reference / ASHRAE 189.1 schedule sets, constructions, and space types. Is there any way to remove this extraneous content from a new model?