Users that have access to the design page will probably spend a good bit of time here. The design page is where the operations model is maintained and managed. The following screenshot shows the design page with one object opened.

2.6.1 Design Tree
The design tree (shown on the left side of the screenshot above) contains all objects within the operations model. The tree includes the following root, or top-level objects:

• Alarms
• Devices
• Networks
• Reports
• Sets
• Templates

Objects and folders related to each of these object types are included as children in the tree. Click on the + next to each tree item to open the tree up and to see the available child items. Whenever an object in the tree is clicked on, AutoNOC will open a object dialog box for that object.

An operations model in AutoNOC is constructed by creating and configuring objects within the model. The user adds devices, defines reports, customizes alarms, designs sets, and customizes monitoring behavior. It is through this process that AutoNOC is customized to manage an organization's network.

For complete information and descriptions of the objects available for designing models, please see section 3.1 - Object Model.

2.6.2 Window Manager
Whenever you click on an object in the design tree, AutoNOC will open up a new object dialog. It has a built in window manager that remembers where you left off with each object. This feature is useful if you are working on many different objects at the same time.

As the picture above shows, the window manager opens new windows for each new object clicked on. The window manager also provides the following buttons:

• Close Window
  When this button is clicked on, the window for the current object will be closed.
• Close All Windows
  This button closes all open object dialogs.

2.6.3 Object Dialogs
Every object in the design tree has an associated object dialog. Each of these dialogs usually has the following tabs:

• Menu
  The menu tab, always the first tab, shows the icons and actions that the user can perform on this particular object.
• Properties
  Typically includes modifications of the object name, system flags, and other features.
• Other Settings
  Most objects will have other settings that are user modifiable and these will be listed as subsequent tabs on the object dialog.

The picture above shows the Properties tab of an example device. Every control in the AutoNOC web GUI has an associated ?+ collapsible help button next to it. To get more detailed information about how the setting behaves, click on that button to open the help for it up.

AutoNOC does the best it can to remember each setting that you enter in a dialog, but these settings are not permanently stored until you click on the Save button that is at the bottom of every dialog that has user editable objects.

AutoNOC will not keep your settings until you press on the Save button. When it is pressed, the values for the page are written to the object and kept.

2.6.4 Adding Child Objects
When you click on an object it will show you a Menu of actions possible with the object as well as any objects that may be created as children of the object. For instance, when you click on the Device top level root object, AutoNOC shows you something that looks like the following:

Clicking on New Folder for instance, will create a new folder as a child. That is how child objects are added to AutoNOC.