Federal Data Center Consolidation Initiative (FDCCI) Data Center Closings 2010-2013

Updated February 8, 2013. Federal Data Center Consolidation Initiative (FDCCI) Data Center Closings 2010-2013. The Administration has expanded the data center consolidation initiative to include data centers of any size, rather than just those 500 square feet and above. And as we expand the initiative we are also expanding our goal. Moving forward, the government’s goal will be to close at least 40% of identified data centers, consistent with our original consolidation goal. By expanding the initiative to include data centers of any size, we expected the baseline to increase. We now have a comprehensive inventory of all data centers varying in size. Although our baseline has increased, we are still committed to consolidate over 1200 data centers by the end of 2015 – a goal that requires us to continue aggressively rooting out duplication and waste. As of March 2012, updates reflect a shift from calendar year to fiscal year reporting. This dataset reflects information provided by the agencies. All questions or inquiries should be directed to the specific agencies. The FY2010 through FY2013 dataset provides a list of planned or closed data centers by agency and by city/state location since the FDCCI started in February 2010. The Data Center Consolidation Task Force meets monthly to review the progress of each consolidation project and ensure government-wide alignment among agency efforts, where appropriate. The Task Force comprises data center program managers, facilities managers, and sustainability officers from 24 agencies that work together to share progress toward individual agency goals. As its work evolves, the Task Force will serve as a "community of practice" for agency CIOs and data center program managers to share best practices and enhance consolidation effectiveness. See collateral information about the FDCCI, including the definition of a data center and other FAQs at cio.gov/fdcci.

Getting Started

All communication with the API is done through HTTPS, and errors are communicated through HTTP response codes. Available response types include JSON, XML, and CSV, which are selectable by the "extension" on API requests or by HTTP Accepts headers.

This documentation also includes inline, runable examples. Click on any link that contains a gear symbol next to it to run that example live against the Federal Data Center Consolidation Initiative (FDCCI) Data Center Closings 2010-2013 API.

App Tokens

All requests should include an app token that identifies your application, and each application should have its own unique app token. A limited number of requests can be made without an app token, but they are subject to much lower throttling limits than request that do include one. If you don't have an app token yet, click the button to the right to sign up for one.

Once you have an app token, you can include it with your request either by using the X-App-Token HTTP header, or by passing it via the $app_token parameter on your URL.

Response Codes

One of the following response codes will be returned with every request:

  1. 200Successful request.
  2. 202Request processing. You can retry your request, and when it's complete, you'll get a 200 instead.
  3. 400Bad request
  4. 401Unauthorized. You're not authorized to access this resource.
  5. 404Not found. The resource requested doesn't exist.
  6. 429Too Many Requests. The client has made too many requests and is currently being rate limited.
  7. 500Server errors. Our bad!

Code Samples

#!/usr/bin/env ruby

require 'net/https'
uri = URI('https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?recall_id=94')

http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_PEER

request = Net::HTTP::Get.new(uri.request_uri)
request.add_field('X-App-Token', ARGV[0])

response = http.request(request)
puts response.code
puts response.body
#!/usr/bin/env python

import sys
import requests

r = requests.get('https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?recall_id=94', headers={'X-App-Token': sys.argv[1]})
print r.status_code
print r.text
request = require 'request'
options = uri: 'https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?$$app_token=APP_TOKEN&recall_id=94'
request options, (err, response, body) ->  console.log body
#!/bin/sh 

curl --header "X-App-Token: $1" "https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?recall_id=94"

Fields

The following fields are available on the Federal Data Center Consolidation Initiative (FDCCI) Data Center Closings 2010-2013 API.

department_name

Human Name: Department Name
Type: text
Name of the department closing the datacenter

Examples

Retrieve all records with department_name equal to U.S. Agency for International Development:

Retrieve all records where department_name is within 1 kilometer of Seattle, WA (47.598177,-122.33448):

https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?$where=within_circle(department_name, 47.598177,-122.33448, 1000)

data_center_name

Human Name: Data Center Name
Type: text

Examples

Retrieve all records with data_center_name equal to ZION:

Retrieve all records where data_center_name is within 1 kilometer of Seattle, WA (47.598177,-122.33448):

https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?$where=within_circle(data_center_name, 47.598177,-122.33448, 1000)

data_center_location

Human Name: Data Center Location
Type: location

Examples

Retrieve all records with data_center_location equal to longitude: -106.58187814499968, latitude: 35.077063671000474, human_address: {"address":"PO Box 5400 (Loc 385/CA-13)","city":"Albuquerque","state":"NM","zip":"87185"}:
Retrieve all records with data_center_location equal to longitude: -106.58187814499968, latitude: 35.077063671000474, human_address: {"address":"PO Box 5400 (Loc 385/CA-13)","city":"Albuquerque","state":"NM","zip":"87185"}:

Retrieve all records where data_center_location is within 1 kilometer of Seattle, WA (47.598177,-122.33448):

https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?$where=within_circle(data_center_location, 47.598177,-122.33448, 1000)

status

Human Name: Status
Type: text

Examples

Retrieve all records with status equal to To be closed between 03/01/2014 and 09/30/2014:

Retrieve all records where status is within 1 kilometer of Seattle, WA (47.598177,-122.33448):

https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?$where=within_circle(status, 47.598177,-122.33448, 1000)

latitude

Human Name: Latitude
Type: number

Examples

Retrieve all records with latitude equal to 64.84507923900048:

Retrieve all records where latitude is within 1 kilometer of Seattle, WA (47.598177,-122.33448):

https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?$where=within_circle(latitude, 47.598177,-122.33448, 1000)

longitude

Human Name: Longitude
Type: number

Examples

Retrieve all records with longitude equal to -66.10276845099963:

Retrieve all records where longitude is within 1 kilometer of Seattle, WA (47.598177,-122.33448):

https://explore.data.gov/resource/federal-data-center-consolidation-initiative-fdcci-data-center-closings-2010-2013.json?$where=within_circle(longitude, 47.598177,-122.33448, 1000)