Colocation NOC

This feature is available only to organizations with a Platinum/Gold license.

The Colocation NOC solution is designed for organizations that manage multiple sites and host several colocation companies on each site. The solution allows the organization to control the data each colocation company can see per site. This way the organization does not expose all of the available data to all colocation companies on the site.

In addition, there is an API tool that enables users to query the active status of alarms within the Colocation NOC.

Use Case

TowerCo wants to provide better service to their clients and let them know if something is wrong with the sites but at the same time, TowerCo wishes not to expose all of the available site data. This is why the end clients do not have access to Galooli’s main software platforms. The Colocation NOC dashboard is only showing digital flags and alarms, and this way does not expose sensitive information. In addition, the end clients will see alarms only in the sites they are hosted in, meaning, if the end client is X and in one of the sites there is an active alarm but tenant X is not on that site, Tenant X will not see the site on the alarm status dashboard.

Display General Information

In order to use the Colocation NOC solution just open the “Apps” solution and choose “Colocation NOC”.
The app will be similar to the NOC table display.

  • Site name - The unit name in the system

  • Tenant’s site id - Represents the specific site id that the tenant set on this site. The tenant can see data only about their self

  • Session start time and last alarm time - The time when the unit was added to the list and the last time any of the alarms were activated on the site

  • Tenant Meter Disconnected - An indication that a meter of a particular tenant is disconnected

  • Tenant power down - An indication that there is no voltage and no current

  • Tenant load down - An indication that there is voltage but no current

  • Data Export - The "Colocation Report" allows you to export the table data to an Excel file.

  • The alarms that will be shown will be the alarms that were defined through the NOC category configuration

  • NOC functions like acknowledgment, tickets, etc, are not available through this app, it is only for display purposes

  • Alarms display order is that the latest alarm at the top of the list

View Permissions

Please contact support to open specific view permissions. Users will generally only be able to view alarms for tenants whose permissions they have been granted - https://galooli.atlassian.net/wiki/spaces/KP/pages/2584182813

Alarms Configuration

  1. The NOC application should be active in the organization.

  2. When creating alarms within the NOC application, select the Colocation NOC category and add the relevant alarms.

Colocation NOC API

The Colocation NOC API enables customers to get data from the Galooli backend platform and combine this data with their own systems, such as ERP systems, CRM systems, applications, etc.

The API provides a method for querying the active status of alarms within the APPs - Colocation NOC.

Report Name

Colocation NOC Alarms

Description

Displays detailed information about all current alarms in the Colocation NOC solution.

User Credential Perquisites

  • A valid user (Authorized to login to Galooli’s platform)

  • The user must have access permission to the ‘APPs - Colocation NOC’

  • The user must have at least one assigned TENANT

Service Limitations

Max request interval (per user): Request per 10 seconds.

Request Example

New URL

https://space-apps2.galooli.com/ColocationNOC/APIColocationNOC?user=%5busername%5d&password=%5bpassword
  • Global User

In order to receive a response from the API, the following variables must be filled in:

-USERNAME

-ORGANIZATION

-PASSWORD

  • One Organization User

In order to receive a response from the API, the following variables must be filled in:

-USERNAME

-PASSWORD

Old URL

https://space-apps.galooli.com/AlarmsStatus/AlarmsStatusIndex?handler=APIColocationNOC&user=[USER]&password=[PASSWORD]

Error Result Codes

Requests are too frequent - max request interval is 10 seconds (per user)

Authentication failed – wrong user/password

Invalid User Configuration - Missing Credentials or missing Tenants configuration

Failed to retrieve categories - [Internal] Error while requesting service categories configuration

Invalid Data - [Internal] Error while requesting active alarms status

Results Structure

Note - api_noc_Alarms_item field varies per the configuration of the ‘APPs - Colocation NOC’ service.

[ { "SiteName": "SITE NAME 1", "api_noc_Alarms_item": [ { "AlarmName": "AC power", "IsActive": true }, { "AlarmName": "LVD", "IsActive": false }, { "AlarmName": "High temperature", "IsActive": false }, { "AlarmName": "DC Available", "IsActive": true } ], "Session_start_time": "2023-04-21T15:09:12", "Last_alarm_time": "2023-04-21T15:54:15", "TenantsSiteId": "SITE ID 1", "DisconnectedTenants": "", "PowerDownTenants": "TENANT NAME", "LoadDownTenants": "TENANT NAME" }, { "SiteName": "SITE NAME 2", "api_noc_Alarms_item": [ { "AlarmName": "AC power", "IsActive": false }, { "AlarmName": "LVD", "IsActive": false }, { "AlarmName": "High temperature", "IsActive": false }, { "AlarmName": "DC Available", "IsActive": true } ], "Session_start_time": "2023-04-24T00:57:58", "Last_alarm_time": "2023-04-24T00:57:58", "TenantsSiteId": "SITE ID 2", "DisconnectedTenants": "", "PowerDownTenants": "TENANT NAME", "LoadDownTenants": "TENANT NAME" } ]