Product(s):	OpenBuildings Designer, AECOsim Building Designer
	Version(s):	CONNECT Edition
	Area:	Import/Export
	Subarea:	i-Model

Question

When I publish an i-Model the process actually creates multiple files with the same name but different file extensions. What is the purpose of each of these files?

FileName.i.bim
FileName.i.bim.TitleCache
FileName.i.bim.issues
FileName.iModel
FileName.i.dgn

Solution

To some extent it may be more accurate to use the term “i-model” to represent a set of engineering data or information contained in a group of files, or a distributed database, vs. the one file that uses the *.imodel extension. For example, certain processes such as the Issues Resolution Service or iModel Hub don’t necessarily use the *.imodel file itself but instead others from that group. This concept is different than the original *.i.dgn format, but it shows how the i-model ecosystem has changed and evolved over time.

In regards to the files themselves:

*.imodel – this is the published read-only file that packages or compresses the engineering data for portability purposes.
*.i.bim – this is the uncompressed version of the *.imodel and is considered a “coordinated” copy of that data; i.e., where updates are performed using iModel Hub or Issues Resolution Service.
*.i.bim-issues – this is an ASCII text file (like a log) created when the iModel is published.
*.i.bim.TileCache – this is used for viewing i-model data via a web browser.
*.i.dgn - this is the original single i-model output.