Installation and Startup Guide | Envision for BACtalk

Figure 1 Envision for BACtalk directory structure

Alerton root directory

Alerton Standard directory
• Factory-standard displays and graphics and DDC.
• If displays and templates are modified, they must be saved to a job folder.
• Any job can use displays, bitmaps, DDC, and documentation from Alerton Standard.
• Documentation directory stores sequences and point list for standard applications.

Stores communications protocol drivers

Generic directory (with Generic job within it)

• Provides a default login if rep/job is lost or corrupt.
• Do not delete.

Stores hardware key drivers

Sample Rep

Sample User Job

Archive
• Stores data when log and report information is archived.

Bitmaps directory
• Stores bitmaps used by data displays and templates in the displays directory. If not in
this location, Envision for BACtalk will not find bitmaps for displays and templates.

DDC directory
• Stores all DDC files for the job.

Device data directories

• One for each device, named Dev<devinst> where <devinst> is the device instance of
the controller.
• Stores device setup data for device manager and applicable object images (schedules,
trend logs, demand limiters, etc.) for the device.

Displays directory
• Stores all displays and templates for the job.

More user job directories

• In this case, two jobs for remote sites.
System directory
• Stores core operating files for BACtalk system and ROC files for host devices.

VisualLogic directory
• Stores core operating files for VisualLogic.

34 © Honeywell. All Rights Reserved. LTBT-TM-ADMIN26 Rev. A