The file is zip-compressed, has an NTPL file extension for Niagara template, and encapsulates at least two internal files:

You can include graphics and other internal files as needed to complete the template definition.

For a station, the embedded BOG file will be the station BOG. For a component template, it will be the component tree that was selected for the template. In either case, the resulting component tree will include a templateConfig component of type BTemplateConfig that captures the additional template configuration and metadata. The templateConfig component is a direct child of the template root component. It is added when the template is first created.

Within a station, deployed component templates are identified by the presence of the templateConfig component as a direct child of the template root component. Once a deployed template is found, it may be further differentiated as a device template by examining the component type of the root component.

Application templates have a file extension of NAPL. This distinguishes them from other template types, and the unique file extension enables these files to be used differently throughout the Niagara system. Application template files are stored in a separate folder from component template files, and they are not available from the Template sidebar in Workbench. Deployed application templates place the templateConfig component under the Application Service in the Services container.