Contact
Site: US UK AU |

Facility Access Policy (OTR)

Facility Access Policy (OTR)

Overview

This document outlines how colo clients can gain access to the Nexcess data center in Dearborn, Michigan (OTR). For additional information about Nexcess data center security and safety policies, refer to the DC Manual.

Identification policy

All visitors are required to wear visible RFID access cards or visitor badges during their entire visit. Anyone using a temporary visitor badge to gain access must relinquish their badge at the end of their visit.

Escort and shared spaces

Unless noted otherwise in this document, team members are to escort visitors at all times when not in a shared space. Shared spaces are strictly defined as the lobby, bathrooms, and kitchen..

Access levels

Client

Clients are individuals with co-located equipment owned by the client and located in one or more Nexcess facilities. Clients have management-approved and assigned access cards that allow direct access to the facility. As long as they wear their access cards, they do not require escorts within the facility or sign in, although a Nexcess Team member will maintain line-of-sight with clients within the data center.

Clients without access cards can only gain access by using the procedure provided in the “Visitor access” section below.

Visitor

Visitors are defined as anyone that does not have an access card. Visitors must carry temporary non-RFID black badges that do not operate any doors, and must be escorted at all times outside of shared spaces by a Nexcess team member or authorized access-card-carrying client. 

Client access

Clients, as defined in the above “Access levels” section, may enter the OTR data center unimpeded. Clients may remove equipment only after the DCOps Team verifies the hardware’s colo ID tag and description match their records.

Visitor access

The procedure below applies to all individuals without RFID access cards.

  1. Upon the visitor’s arrival, a DCOps or Facilities Team member greets the visitor, who enters the facility through the main entrance.

  2. The visitor presents government-issued photo ID, and the team member verifies the visitor’s given name and appearance match the ID. If the visitor is a colo client’s guest, the team member also cross references the guest’s identity with the ticket described in the “Guests of colo clients” section below.

  3. The visitor signs in using the Guest Sign-In System.

  4. The team member gives a visitor badge to the visitor, who wears it in a visible location.

  5. The team member escorts the visitor at all times when not in a shared space (defined above).

At the end of the visit, the visitor signs out of the Guest Sign-In System, relinquishes the visitor’s badge, and exits through the main entrance.

Guests of colo clients

Clients’ guests are considered visitors and are therefore subject to the procedure provided in the “Visitor access” section above. They are also subject to all visitor policies within the DC Manual, and visitors under the age of 18 are not permitted.

Clients should schedule their visits whenever possible, though exceptions are permissible. The procedure to do so is as follows:

Attention: Unannounced guests are denied access until the Nexcess team calls the Superuser on the account, who must provide both verbal authorization and written authorization within a ticket.

  1. No fewer than 5 business days before the date of entry into the facility, the Superuser or DC User on the account submits a ticket to the Support Team with the following information:
    1. Visitor's full name
    2. Company name
    3. Facility location
    4. Date of visit
    5. Duration of visit
    6. Estimated time of arrival
  2. DCOps verifies the Superuser or DC User is in fact the party making the request, then secures approval from the Nexcess executive team.
  3. Upon approval, DCOps notifies the Superuser or DC User by replying to the original ticket.
  4. The visitor calls DCOps at 1 (248) 752-0441 at least 15 minutes before arrival.

Revision History

DateNameComment
2016-July-14 TWD First Draft
2016-Oct-10 TWD Changed title; overview now points to companion document 
2018-Jan-21 TWD Reordered Steps 1 - 4 in Guests of colo clients section

(Last reviewed by Esmahan Abdulla on Jan 21 2018)

For 24-hour assistance any day of the year, contact our Support Team by email or through the Client Portal.

Article Rating (No Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
 
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
How to transfer domains
Added on Wed, Nov 23, 2016
What is GeoIP?
Added on Fri, Oct 31, 2014
How to decompress files in gzip
Added on Tue, Jan 6, 2015
How to request and revoke facility access (MEL, TMR)
Added on Wed, Feb 28, 2018
What are the benefits of dedicated IP addresses?
Added on Thu, Jan 14, 2016
How to interpret MTR results
Added on Tue, Jun 26, 2018
How to flush Memcached
Added on Mon, Apr 30, 2018
How to request and revoke facility access - OTR
Added on Mon, Jan 22, 2018
How to flush Redis
Added on Thu, Apr 7, 2016
How to change SSH passwords from the CLI
Added on Thu, Feb 8, 2018