Administration (Enterprise Level Data)

Import using feature path: Administration/Tools/Implementation Imports/Settings & Configuration

Import Sites, Huts and Branches [Sites]

• Group: Lets you to categorize sites that are affiliated with your enterprise.  Site groups are imported along with the site information.  For example, sites may be grouped by city, state or country. If the group does not exist prior to import, it will be created.
• Type: Specifies Site type. The options are: Site, Branch, and Hut.
• GR._Site.Name: The Site name (for example, New York Data Center).
• GR._Site.Hide: Sites with this value set to True will only be manageable by and visible to administrators. The default setting is False (not hidden).
• GR._Site.Disabled: This is value is used to hide sites that are no longer in use. When set to True the administrator will only be able to view it. The default setting is False.
• GR._Site.Sample: This value sets sites to be Read Only for all users. No changes can be made within while this value is set to True. The default setting is False.
• GR.Address.Address1: The address of the Site.
• GR.Address.City: The city associated with the address.
• GR.Address.State: The state associated with the address, if in the United States. Can be used for region if the address is international.
• GR.Address.Country: The country associated with the address.
• GR.Address.Zip: The zip code or mailing code associated with the address.

 

Optional fields include:

• GR._Site.Description: A short description of the Site.
• GR._Site.TimeZone: The time zone of the site.
• GR.Address.Address2: The second line of the address, if applicable.
• GR.Address.URL: The site’s URL address.
• GR.Address.LatLng: The latitude and longitude of the site.

 

Import Inter-Site Connectivity Paths [Inter-Site Connectivity]

• Name: The name of the Inter-Site Connection (for example, New York to Chicago).
• FromSite: The Site name where the connection starts (for example, New York Data Center).
• ToSite: The Site name where the connection ends (for example, Chicago Data Center).

 

Optional fields include:

• Description: A short description of the connection.
• Icon: The the image file you want to use to represent the connection.

 

 

Import Inter-Site Connectivity Segments [PathSegments]

• Path: The name of the Inter-Site Connectivity Path (for example, New York to Chicago).
• Name: The name of the Inter-Site Connectivity Segment (for example, New York to Chicago).
• CableType: The connection type for the path, usually Copper, Fiber, Satellite, Wireless or Internet.
• CableWidth: Specifies the pixel width on the Google Maps.
• CableColor: Specifies the line color for the Google Maps (for example, #b91d0b is Milano Red). Color Codes use standard HEX code color values.

 

Optional fields include:

• Description: A short description of the connection.
• Attribute: Specifies the path type icon (BackHaulFiber.ico, LongHaulFiber.ico, ShortHaulFiber.ico, Other.ico).
• Deployment: Specifies the path deployment type icon (Overground.ico, Underground.ico, Undersea.ico, Underwater.ico, Other.ico).
• LandingPoint: Specifies the Landing Point icon (Hut.ico, Microwave.ico, Repeater.ico, SubseaLanding.ico, Tower.ico, Other.ico).

 

Import Inter-Site Connectivity Waypoints [SegmentWayPoints]

• Path: The name of the Inter-Site Connectivity Path (for example, New York to Chicago).
• Segment: The name of the Inter-Site Connectivity Segment (for example, New York to Chicago).
• LatLng: The latitude and longitude of the waypoint.

 

Import Company Groups [CompanyGroups]

The predefined Company Groups in NetZoom are:

• Company: Default company group.
• Owner: Defines Licensee Company.
• Tenant: Defines Organizations to whom you provide services.
• Vendors: Defines Companies that supply equipment or services to your organization.

 

The required fields for a successful Company Group import are:

• Name: Name of the Company Group you are creating.
• Description: Description of the group you are creating.

 

Import Companies [Companies]

• Group: The company group. If the group does not exist prior to import, it will be created.
• GR._Company.Name: The Company name.
• GR._Company.Shortname: An abbreviation or acronym of the Company to be displayed on diagrams.  The short name cannot contain any punctuation or special characters.
• GR.Address.Address1: The first line of the company address, if applicable.
• GR.Address.City: The city associated with the address.
• GR.Address.State: The state associated with the address, if in the United States.
• GR.Address.Country: The country associated with the address.
• GR.Address.Zip: The zip code or mailing code associated with the address.

 

Optional fields include:

• GR._Company.Description: A Description of what services the company provides.
• GR.Address.Address2: The second line of the Company address. 
• GR.Address.URL: The Company’s URL address.
• GR.Email.Email: A Company email address.
• GR.Email.Description: The email address type. Examples: Work, Home, or Other.
• GR.Phone.Phone: The Company’s main phone number.
• GR.Phone.PhoneType: The phone number type. Options: Work, Home, Mobile, Fax, SMS, Skype, or Customer Support.

 

Import Contact Groups [ContactGroups]

• Group: The name of the Contact Group you are creating.
• Description: A brief description of the group you are creating.

 

Import Contacts [Contacts]

• Group: The name of the Contact Group to be associated with the Contact. If the group does not exist prior to import, it will be created.
• GR._Contact.Name: The name of the person who is the contact.
• GR._Contact.Description: A brief description of the reason why the person should be contacted (for example, if the person was in “Emergency” Contact Group, the contact description might be “Ambulance Service” or “Hazmat Service”).
• GR._Contact.Designation: The department or job title for the Contact.
• GR.ContactInfo.Email: The email address of the Contact.
• GR.ContactInfo.Phone: The phone number of the Contact.
• GR.Address.Address1: The first line of the Contact’s address.
• GR.Address.City: The city associated with the address.
• GR.Address.State: The state associated with the address, if in the United States.
• GR.Address.Country: The country associated with the address.
• GR.Address.Zip: The zip code or mailing code associated with the address.

 

Optional fields include:

• GR.Address.Address2: The second line of the company address, if applicable.
• GR.Address.URL: The URL address of the contact’s company.

 

Import Licenses [Licenses]

• Group: The name of the License Group to be associated with the license. If the group does not exist prior to import, it will be created.
• Subscription:The subscription number of the License to be added.

 

Import Roles [Roles]

• CompanyName: The name of the Company.
• ParentRole: The name of the supervisory role for the new role you are creating.
• RoleName: The name of the role you wish to create.

 

Optional fields include:

• Description: A short description of the role you wish to create.

 

Import Users & User Groups [Users]

• Group: The name of the User Group to be associated with the User. If the group does not exist prior to import, it will be created.
• Role: The name of the NetZoom Access Role assigned to the User.
• Company: The name of the Company to be associated with the User.
• GR._User.Name: The name of the User.
• GR._User.Domain: The Domain Name for the User’s login credentials.
• GR._User.LoginName: The User identification used to log into NetZoom.
• GR.Address.City: The city associated with the address.
• GR.Address.State: The state associated with the address, if in the United States.
• GR.Address.Country: The country associated with the address.

 

Optional fields include:

• GR._User.Description: Additional information regarding the User.
• GR._User.Designation: Additional information regarding the User’s job title or role in the Data Center.
• GR._User.BirthDay: The User’s birthday (only the month and day will be visible to others).
• GR.Address.Address1: The first line of the User’s work location address. 
• GR.Address.Address2: The second line of the Company address. 
• GR.Address.Zip: The zip code or mailing code associated with the address.
• GR.Address.URL: The URL address of the Contact’s Company.

 

Import Roles vs. Sites Assignment [SiteRoles]

• SiteName: The Site name (for example, New York Data Center).
• RoleName: The name of the role you wish to have permissions to the Site.

 

Import Users vs. Sites Assignment [SiteUsers]

• SiteName:The Site name (for example, New York Data Center).
• UserName:The name of the User you wish to have permissions to the Site.

 

Import Shifts [Shifts]

 

• SiteName: The Site name for the Shift Location (for example, New York Data Center).
• CompanyName: The Company name.
• Name: The name of the Shift you wish to create.
• Description: A brief description of Shift.
• Color: The calendar color for the Shift (for example, #8b50a9, #ffffff).  Color Codes use standard HEX code color values.
• StartDate: The start date for the Shift.
• EndDate: The end date for the Shift.
• StartTime: The start time for the Shift.
• EndTime: The end time for the Shift.
• Abbreviation: The 3-digit abbreviation for the Shift.

 

Import Shift Schedules [ShiftSchedules]

• SiteName: The Site name for the Shift Schedule Location (for example, New York Data Center).
• CompanyName: The Company name.
• Name: The name of the Shift Schedule you wish to create.
• Description: A brief description of Shift Schedule.
• TeamCount: The number of team members required for the Shift Schedule (for example, 5).
• RepeatCycle: The number of days before the Shift Schedule starts again (for example, 7).
• StartDate: The start date for the Shift Schedule.

 

Import Escalation Rules [Escalation Rules]

Note: Service Escalation Policies can be imported with Alert Escalation Rules.

• Name: The name of the Escalation Policy.
• Description : A brief description of the policy
• RepeatCount: The number of times to repeat the notification before escalation to the next level.
• Interval: How long to wait before repeating the notification or escalation to the next level.
• Service: This value is set to False (this is a service policy) for Alert Escalation Policies and set to True (this is a service policy) for Service Escalation Policies.

 

Import Service Task Policy Templates [PolicyTemplates]

• ID: The internal ID number of the Template.
• Category: The Template Category.
• SubCategory: The Template Subcategory.
• Name: The name of the Template.
• Description: A brief description of the Template
• LogTemplate: The message that will be entered into the log when the Service Task is triggered.
• SMSTemplate: The message that will be sent via SMS message when the Service Task is triggered.
• HTMLTemplate: The message that will be displayed in the Service Task feature when the Service Task is triggered.
• HTMLExpr: Any expressions required for the Template.
• Severity: The severity level of the Service Task when it is triggered.
• Internal: This value is set to False (this is a NetZoom template) for Templates that are not used by NetZoom and set to True (this is a NetZoom template) for Templates that are used by NetZoom.
• Note: This value is set to False (add note) for templates that should not have the Log also added as a permanent note and set to True (add note) for Templates that should have the Log also added as a permanent note.
• Maintenance: This value is set to False (this is a Maintenance task) for Templates that are not NetZoom Maintenance Tasks and set to True (this is a Maintenance task) for Templates that are NetZoom Maintenance Tasks.

 

Import Services Escalation Policy [ServiceEscalationPolicy]

Note: Service Escalation Policies can be imported with Alert Escalation Rules.

• Name: The name of the Escalation Policy.
• Description: A brief description of the Policy.
• RepeatCount: The number of times to repeat the notification before escalation to the next level.
• Interval: How long to wait before repeating the notification or escalation to the next level.
• Service: This value is set to False (this is a service policy) for Alert Escalation Policies and set to True (this is a service policy) for Service Escalation Policies.

 

Import Message Templates [MessageTemplates]

• ID: This is the internal ID number of the template.
• Category: The Template category.
• SubCategory: The Template Subcategory.
• Name: The name of the Template.
• Description: A brief description of the Template.
• LogTemplate: The message that will be entered into the log when the Message is triggered.
• SMSTemplate: The message that will be sent via SMS message when the Message is triggered.
• HTMLTemplate: The message that will be displayed in the Message feature when the Message is triggered.
• HTMLExpr: Any expressions required for the Template.
• Internal: This value is set to False (this is a NetZoom template) for Templates that are not used by NetZoom and set to True (this is a NetZoom template) for Templates that are used by NetZoom. Note: This value is set to False (add note) for Templates that should not have the Log also added as a permanent note and set to True (add note) for Templates that should have the Log also added as a permanent note

 

Import Alert Templates [AlertTemplates]

• ID: This is the internal ID number of the template.
• Category: The template category.
• SubCategory: The template Subcategory.
• Name: The name of the template.
• Description: A brief description of the template.
• LogTemplate: The message that will be entered into the log when the Alert is triggered.
• SMSTemplate: The message that will be sent via SMS message when the Alert is triggered.
• HTMLTemplate: The message that will be displayed in the Alerts feature when the Alert is triggered.
• HTMLExpr: Any expressions required for the template.
• Severity: The severity level of the Alert when it is triggered.
• Internal: This value is set to False (this is a NetZoom template) for Templates that are not used by NetZoom and set to True (this is a NetZoom template) for Templates that are used by NetZoom. Note: This value is set to False (add note) for templates that should not have the Log also added as a permanent note and set to True (add note) for Templates that should have the Log also added as a permanent note.

 

Import Broadcast Announcement Information [Information]

• TipID: This is the internal ID number of the custom tip. This can be blank.
• CompanyName: This is the Company name. This can be blank.
• SiteName: This is the site name where the tip should be displayed.
• UserName: This is the name of the user that created the tip.
• Title: This is the name of the tip.
• Topic: This is the name of the Menu where the tip should be displayed.
• TipHTML: This is the HTML format message the tip should display.
• WikiHelpURL: This is the Wiki Help link that should be added to the tip. This can be blank.
• StartDate: This is the date to start displaying the tip.
• EndDate: This is the date to stop displaying the tip.
• RepeatAfterDays: This is the number of days to wait before re-displaying the tip.

 

Import Work Flow Tasks Role Assignments [WFTaskRoles]

• WFName: The Workflow name.
• RoleName: The name of the role you wish to have permissions to the Workflow.

 

Import Work Flow Tasks User Assignments [WFTaskUsers]

• WFName: The Workflow name.
• UserName: The name of the User you wish to have permissions to the Workflow.

 

Import Work Flow Task Escalation Policy Assignments [WFTaskPolicy]

• PolicyName: The name of the Escalation Policy.
• AlertName: The name of the Policy Template.
• AlertCategory: The Policy Template category.
• AlertSubCategory: The Policy Template Subcategory.

 

Import Policy Escalation User Assignments [PolicyUsers]

• PolicyName: The name of the Escalation Policy.
• UserName: The name of the User you wish to assign to the Escalation Policy.

 

Import Alert Template Escalation Policy Assignments [PolicyAlerts]

• PolicyName: The name of the Escalation Policy.
• AlertName: The name of the Alert Template.
• AlertCategory: The Alert Template category.
• AlertSubCategory: The Alert Template Subcategory.

 

Import Management Units [ManagementUnits]

Note: Management Units can only be created for the Licensee and Tenant Companies.

• CompanyName: The Company name.
• Category: The category or department for the Management Unit Team
• Name: The name of the Management Unit Team.
• Description: A brief description of the Management Unit Team.
• UserName: The name of the user you wish to assign to the Management Unit Team.

 

Import to Populate Entity Data [~EntityName]

Note: You may create any additional columns for property edits you wish. Export the Entity to obtain a full list of all available properties.

• EntID: This is the record’s Primary Key in the Database. Use the Property Export to obtain this value before doing a property update import.