- I Lotus Green Data Centers Handbook
- II Requirements
- III Drawings
- IV Labels and signage
- V Procedures
- VI Alarms and monitors
- VII Throws and controls
- VIII Parts catalog
- X Appendix
Book
Book
Creator: Lotus Green Data Center forge contributors
I Lotus Green Data Centers Handbook
You can edit these pages when logged in. Users can define notifications for the whole XoWiki instance (by clicking on the notifications button in the menu bar or for categories or by clicking on the letter symbol next to the category entries at the bottom of the page)
Files are shared at http://lotusgreendatacenters.com/forge/files-storage/
Discussions are at: http://lotusgreendatacenters.com/forge/forum/
Excuse the document maze. We are trying some new features with Xowiki that help to convert the pages into a linearly organized book.
I.1 Release Notes
Status: Under development.
These data center plans were originally worked out under Dekka Corp for EORIT. The specific design is being generalized for the benefit of those interested in building fully scalable, green data centers most anywhere on the planet. Constructive contributions are welcome.
There are two key parts to the scalable aspect of the DC:
The floor plan (at drawings ) is inside a concrete, cylindrical vault with the floor buried about 3 to 6 meters below ground surface to maximize stability in constant temperature/humidity.
The vault placement ( structure-mechanical ) uses a variation of the Kagome lattice to maximize scalability in growth requirements regardless of type of local conditions.
The design places few constraints on localization requirements. This allows the design to be localized according to code, environmental, economic and other constraints.
I.2 Introduction
problem
Data centers are historically designed according to industrial requirements from the 1950's main frame computers.
Data center cabinet power consumption and heat density continues to rise steadily.[Brill] Conventional climate control processes, such as raised floor cooling, breakdown at about 40 watts/SF. Very few data centers have sufficient capacity to handle operating power loads and dissipate higher heat densities of newer technologies such as blade servers [Brill]. Hardware manufacturers are beginning to use water cooling and other unconventional means to convey heat out of the cabinets [Brill].
The simplest solution to air cooling consists of increasing fan performance in enclosures and airflow in datacenter spaces. Yet this technique is not suitable where personnel frequent due to intolerable noise level of fans and increased airflow [Nicolai].
"IDC believes that most enterprises will need to consider fitting out new datacentre facilities in the near future.."[Fleischer]
A new paradigm of data center design is needed to:
- solve the crisis found in antiquated designs,
- anticipate and resolve emerging issues in data centers,
- and maximize the long-term value and sustainability of data centers.
-----
Brill, Kenneth G. "2005-2010 Heat Density Trends in Data Processing, Computer Systems, and TElecommunications Equipment." Uptime Institute. 2006.
Fleischer, Daniel and Eibisch, James. "Creating Cost and Energy Efficiency Through Outsourcing Hosting Solutions" IDC. Aug 2007.
Nicolai, Michael. "IT Climate Control" Rittal 2005.
I.3 GNU Free Documentation License v 1.2
from: http://www.gnu.org/licenses/fdl.txt
GNU Free Documentation License
Version 1.2, November 2002
Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
0. PREAMBLE
The purpose of this License is to make a manual, textbook, or other
functional and useful document "free" in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
This License is a kind of "copyleft", which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The "Document", below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as "you". You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of
the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall subject
(or to related matters) and contains nothing that could fall directly
within that overall subject. (Thus, if the Document is in part a
textbook of mathematics, a Secondary Section may not explain any
mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
The "Invariant Sections" are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format, SGML
or XML using a publicly available DTD, and standard-conforming simple
HTML, PostScript or PDF designed for human modification. Examples of
transparent image formats include PNG, XCF and JPG. Opaque formats
include proprietary formats that can be read and edited only by
proprietary word processors, SGML or XML for which the DTD and/or
processing tools are not generally available, and the
machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, "Title Page" means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as "Acknowledgements",
"Dedications", "Endorsements", or "History".) To "Preserve the Title"
of such a section when you modify the Document means that it remains a
section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
3. COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
B. List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
C. State on the Title page the name of the publisher of the
Modified Version, as the publisher.
D. Preserve all the copyright notices of the Document.
E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
F. Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
G. Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
H. Include an unaltered copy of this License.
I. Preserve the section Entitled "History", Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled "History" in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
J. Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the "History" section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
Preserve the Title of the section, and preserve in the section all
the substance and tone of each of the contributor acknowledgements
and/or dedications given therein.
L. Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled "Endorsements"
or to conflict in title with any Invariant Section.
O. Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties--for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
5. COMBINING DOCUMENTS
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History"
in the various original documents, forming one section Entitled
"History"; likewise combine any sections Entitled "Acknowledgements",
and any sections Entitled "Dedications". You must delete all sections
Entitled "Endorsements".
6. COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an "aggregate" if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
8. TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements",
"Dedications", or "History", the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.
9. TERMINATION
You may not copy, modify, sublicense, or distribute the Document except
as expressly provided for under this License. Any other attempt to
copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this
License will not have their licenses terminated so long as such
parties remain in full compliance.
10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License "or any later version" applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation.
ADDENDUM: How to use this License for your documents
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
I.4 The TAPR Open Hardware License v 1.0
from: http://www.tapr.org/TAPR_Open_Hardware_License_v1.0.txt
The TAPR Open Hardware License
Version 1.0 (May 25, 2007)
Copyright 2007 TAPR - http://www.tapr.org/OHL
PREAMBLE
Open Hardware is a thing - a physical artifact, either electrical or
mechanical - whose design information is available to, and usable by,
the public in a way that allows anyone to make, modify, distribute, and
use that thing. In this preface, design information is called
"documentation" and things created from it are called "products."
The TAPR Open Hardware License ("OHL") agreement provides a legal
framework for Open Hardware projects. It may be used for any kind of
product, be it a hammer or a computer motherboard, and is TAPR's
contribution to the community; anyone may use the OHL for their Open
Hardware project.
Like the GNU General Public License, the OHL is designed to guarantee
your freedom to share and to create. It forbids anyone who receives
rights under the OHL to deny any other licensee those same rights to
copy, modify, and distribute documentation, and to make, use and
distribute products based on that documentation.
Unlike the GPL, the OHL is not primarily a copyright license. While
copyright protects documentation from unauthorized copying, modification,
and distribution, it has little to do with your right to make, distribute,
or use a product based on that documentation. For better or worse, patents
play a significant role in those activities. Although it does not prohibit
anyone from patenting inventions embodied in an Open Hardware design, and
of course cannot prevent a third party from enforcing their patent rights,
those who benefit from an OHL design may not bring lawsuits claiming that
design infringes their patents or other intellectual property.
The OHL addresses unique issues involved in the creation of tangible,
physical things, but does not cover software, firmware, or code loaded
into programmable devices. A copyright-oriented license such as the GPL
better suits these creations.
How can you use the OHL, or a design based upon it? While the terms and
conditions below take precedence over this preamble, here is a summary:
* You may modify the documentation and make products based upon it.
* You may use products for any legal purpose without limitation.
* You may distribute unmodified documentation, but you must include the
complete package as you received it.
* You may distribute products you make to third parties, if you either
include the documentation on which the product is based, or make it
available without charge for at least three years to anyone who requests
it.
* You may distribute modified documentation or products based on it, if
you:
* License your modifications under the OHL.
* Include those modifications, following the requirements stated
below.
* Attempt to send the modified documentation by email to any of the
developers who have provided their email address. This is a good
faith obligation - if the email fails, you need do nothing more
and may go on with your distribution.
* If you create a design that you want to license under the OHL, you
should:
* Include this document in a file named LICENSE (with the appropriate
extension) that is included in the documentation package.
* If the file format allows, include a notice like "Licensed under
the TAPR Open Hardware License (www.tapr.org/OHL)" in each
documentation file. While not required, you should also include
this notice on printed circuit board artwork and the product
itself; if space is limited the notice can be shortened or
abbreviated.
* Include a copyright notice in each file and on printed circuit
board artwork.
* If you wish to be notified of modifications that others may make,
include your email address in a file named "CONTRIB.TXT" or
something similar.
* Any time the OHL requires you to make documentation available to
others, you must include all the materials you received from the
upstream licensors. In addition, if you have modified the
documentation:
* You must identify the modifications in a text file (preferably
named "CHANGES.TXT") that you include with the documentation.
That file must also include a statement like "These modifications
are licensed under the TAPR Open Hardware License."
* You must include any new files you created, including any
manufacturing files (such as Gerber files) you create in the
course of making products.
* You must include both "before" and "after" versions of all files
you modified.
* You may include files in proprietary formats, but you must also
include open format versions (such as Gerber, ASCII, Postscript,
or PDF) if your tools can create them.
TERMS AND CONDITIONS
1. Introduction
1.1 This Agreement governs how you may use, copy, modify, and
distribute Documentation, and how you may make, have made, and
distribute Products based on that Documentation. As used in this
Agreement, to "distribute" Documentation means to directly or indirectly
make copies available to a third party, and to "distribute" Products
means to directly or indirectly give, loan, sell or otherwise transfer
them to a third party.
1.2 "Documentation" includes:
(a) schematic diagrams;
(b) circuit or circuit board layouts, including Gerber and other
data files used for manufacture;
(c) mechanical drawings, including CAD, CAM, and other data files
used for manufacture;
(d) flow charts and descriptive text; and
(e) other explanatory material.
Documentation may be in any tangible or intangible form of expression,
including but not limited to computer files in open or proprietary
formats and representations on paper, film, or other media.
1.3 "Products" include:
(a) circuit boards, mechanical assemblies, and other physical parts
and components;
(b) assembled or partially assembled units (including components
and subassemblies); and
(c) parts and components combined into kits intended for assembly
by others;
which are based in whole or in part on the Documentation.
1.4 This Agreement applies to any Documentation which contains a
notice stating it is subject to the TAPR Open Hardware License, and to
all Products based in whole or in part on that Documentation. If
Documentation is distributed in an archive (such as a "zip" file) which
includes this document, all files in that archive are subject to this
Agreement unless they are specifically excluded. Each person who
contributes content to the Documentation is referred to in this
Agreement as a "Licensor."
1.5 By (a) using, copying, modifying, or distributing the
Documentation, or (b) making or having Products made or distributing
them, you accept this Agreement, agree to comply with its terms, and
become a "Licensee." Any activity inconsistent with this Agreement will
automatically terminate your rights under it (including the immunities
from suit granted in Section 2), but the rights of others who have
received Documentation, or have obtained Products, directly or
indirectly from you will not be affected so long as they fully comply
with it themselves.
1.6 This Agreement does not apply to software, firmware, or code
loaded into programmable devices which may be used in conjunction with
Documentation or Products. Such software is subject to the license
terms established by its copyright holder(s).
2. Patents
2.1 Each Licensor grants you, every other Licensee, and every
possessor or user of Products a perpetual, worldwide, and royalty-free
immunity from suit under any patent, patent application, or other
intellectual property right which he or she controls, to the extent
necessary to make, have made, possess, use, and distribute Products.
This immunity does not extend to infringement arising from modifications
subsequently made by others.
2.2 If you make or have Products made, or distribute Documentation
that you have modified, you grant every Licensor, every other Licensee,
and every possessor or user of Products a perpetual, worldwide, and
royalty-free immunity from suit under any patent, patent application, or
other intellectual property right which you control, to the extent
necessary to make, have made, possess, use, and distribute Products.
This immunity does not extend to infringement arising from modifications
subsequently made by others.
2.3 To avoid doubt, providing Documentation to a third party for the
sole purpose of having that party make Products on your behalf is not
considered "distribution," and a third party's act of making Products
solely on your behalf does not cause that party to grant the immunity
described in the preceding paragraph.
2.4 These grants of immunity are a material part of this Agreement,
and form a portion of the consideration given by each party to the
other. If any court judgment or legal agreement prevents you from
granting the immunity required by this Section, your rights under this
Agreement will terminate and you may no longer use, copy, modify or
distribute the Documentation, or make, have made, or distribute
Products.
3. Modifications
You may modify the Documentation, and those modifications will become
part of the Documentation. They are subject to this Agreement, as are
Products based in whole or in part on them. If you distribute the
modified Documentation, or Products based in whole or in part upon it,
you must email the modified Documentation in a form compliant with
Section 4 to each Licensor who has provided an email address with the
Documentation. Attempting to send the email completes your obligations
under this Section and you need take no further action if any address
fails.
4. Distributing Documentation
4.1 You may distribute unmodified copies of the Documentation in its
entirety in any medium, provided that you retain all copyright and other
notices (including references to this Agreement) included by each
Licensor, and include an unaltered copy of this Agreement.
4.2 You may distribute modified copies of the Documentation if you
comply with all the requirements of the preceding paragraph and:
(a) include a prominent notice in an ASCII or other open format
file identifying those elements of the Documentation that you
changed, and stating that the modifications are licensed under
the terms of this Agreement;
(b) include all new documentation files that you create, as well as
both the original and modified versions of each file you change
(files may be in your development tool's native file format,
but if reasonably possible, you must also include open format,
such as Gerber, ASCII, Postscript, or PDF, versions);
(c) do not change the terms of this Agreement with respect to
subsequent licensees; and
(d) if you make or have Products made, include in the Documentation
all elements reasonably required to permit others to make
Products, including Gerber, CAD/CAM and other files used for
manufacture.
5. Making Products
5.1 You may use the Documentation to make or have Products made,
provided that each Product retains any notices included by the Licensor
(including, but not limited to, copyright notices on circuit boards).
5.2 You may distribute Products you make or have made, provided that
you include with each unit a copy of the Documentation in a form
consistent with Section 4. Alternatively, you may include either (i) an
offer valid for at least three years to provide that Documentation, at
no charge other than the reasonable cost of media and postage, to any
person who requests it; or (ii) a URL where that Documentation may be
downloaded, available for at least three years after you last distribute
the Product.
6. NEW LICENSE VERSIONS
TAPR may publish updated versions of the OHL which retain the same
general provisions as the present version, but differ in detail to
address new problems or concerns, and carry a distinguishing version
number. If the Documentation specifies a version number which applies
to it and "any later version", you may choose either that version or any
later version published by TAPR. If the Documentation does not specify
a version number, you may choose any version ever published by TAPR.
TAPR owns the copyright to the OHL, but grants permission to any person
to copy, distribute, and use it in unmodified form.
7. WARRANTY AND LIABILITY LIMITATIONS
7.1 THE DOCUMENTATION IS PROVIDED ON AN "AS-IS" BASIS WITHOUT
WARRANTY OF ANY KIND, TO THE EXTENT PERMITTED BY APPLICABLE LAW. ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND
TITLE, ARE HEREBY EXPRESSLY DISCLAIMED.
7.2 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL ANY LICENSOR
BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES ARISING OUT OF
THE USE OF, OR INABILITY TO USE, THE DOCUMENTATION OR PRODUCTS,
INCLUDING BUT NOT LIMITED TO CLAIMS OF INTELLECTUAL PROPERTY
INFRINGEMENT OR LOSS OF DATA, EVEN IF THAT PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
7.3 You agree that the foregoing limitations are reasonable due to
the non-financial nature of the transaction represented by this
Agreement, and acknowledge that were it not for these limitations, the
Licensor(s) would not be willing to make the Documentation available to
you.
7.4 You agree to defend, indemnify, and hold each Licensor harmless
from any claim brought by a third party alleging any defect in the
design, manufacture, or operation of any Product which you make, have
made, or distribute pursuant to this Agreement.
####
I.5 Contributors
Liselotte Scheu, Benjamin B Brink, Torben Brosten, Eric Scheu, Marc Fournier
Please let us know if you or someone belongs on this page but is not.
I.6 Glossary
- Availability - service availability ( MTBF / ( MTBF + MTTR )
- AHU - Air Handler unit
- BEU - Blade machines in Enclosure Unit ( 7 x CPU )
- BGP - border gateway protocol http://en.wikipedia.org/wiki/Border_Gateway_Protocol
- BPM - Business Process Management (a streamlined, holistic, continual-improvement style ERP endevour, see: http://en.wikipedia.org/wiki/Business_process_management )
- Cabinet - a Rack with side, top and bottom panels that create an enclosed space
- CAR - Central Apparatus Room (or Central Machine Room) commonly found at broadcast facilities (see http://en.wikipedia.org/wiki/Central_apparatus_room )
- Chassis - an enclosure for conveniently mounting computer equipment in a Rack
- Context Analysis - http://en.wikipedia.org/wiki/Context_analysis
- COP - Coefficient of Performance, amount of heat removed for each unit of energy
- CPE - Compute Power Efficiency, ( IT Equipment Utilization / PUE ) a unitless percentage with target value of 1.0
- CPU - central processing unit (aka motherboard)
- CRAC - Computer Room Air-Conditioners
- CRAH - Computer Room Air-Handlers
- CSF Critical Success Factor - http://en.wikipedia.org/wiki/Critical_success_factor
- CVP - Cost-Volume-Profit
- DC - data center http://en.wikipedia.org/wiki/Data_center
- DCiE - Data Center Infrastructure Efficiency ( IT equipment power x 100 / Total facility power ) a percentage, target is infinity.
- DCP - Data Center Productivity (Useful Work Produced / Total Quantity of a Resource Consumed Producing this Work) a family of metrics DCxP.
- DCeP - Data Center energy Productivity (Useful Work Produced / Total Data Center Energy Consumed Producing this Work ) see thegreengrid.org
- DCUV - Data Center Utility Vault containing a server cluster and network node
- Enclosure - a large Chassis for containing computing equipment, such as CPUs and for mounting in a Cabinet or Rack
- EPU - Enclosed-rack (cabinet) Power Unit ( 1 EPU per BEU )
- ERP - Enterprise Resource Planning (see http://en.wikipedia.org/wiki/Enterprise_resource_planning and BPM / Six Sigma )
- Gap analysis - http://en.wikipedia.org/wiki/Gap_analysis
- HA - High Availability
- IDU - Incremental Deployment Unit ( 2 x RLU )
- ISO 20000 - an ITSM standard (see http://en.wikipedia.org/wiki/ISO_20000 )
- IT - Internet Technology
- ITEU - IT Equipment Utilization, has no clear definition of utilization as a measure of useful work.
- ITIL - Information Technology Infrastructure Library (see http://en.wikipedia.org/wiki/ITIL or alternately ITSM )
- ITSM - IT Service Management (as subset of ERP, see http://en.wikipedia.org/wiki/IT_Service_Management )
- KPI - Key Performance Indicator http://en.wikipedia.org/wiki/Key_performance_indicator
- kWh - kilowatt hours
- KVM - keyboard, video, and mouse
- LAN - Local Area Network
- NIC - Network Interface Card
- NSU - Network Switching Unit
- MSP - Managed Services Provider
- MTBF - Mean Time Between Failures
- MTTR - Mean Time To Replacement/repair
- NOC - Network Operations Center
- PD - Power Density (actual power used by computing equipment / the floor area occupied by the equipment) Equipment space includes egress paths, AC equipment and PDU's, but not empty floor space.
- PDC - Power Density Capacity (total electric power capacity available to computing equipment (Watts) / total "raised floor" area (SF) of DC's computer room.
- PDU - Power Distribution Unit
- PUE - Power Usage Effectiveness ( Total facility power / IT equipment power OR 1/DCiE ), ratio target is 1.0
- Rack - a standardized frame, usually 42RU (up to 45RU = 7ft) and 19inch wide, for mounting computer equipment, see http://en.wikipedia.org/wiki/19-inch_rack Telecommunications equipment sometimes uses Western Electric 23-inch standard width. Seismic zone racks for Zone 4 are most secure. http://en.wikipedia.org/wiki/19-inch_rack#Four-_and_two-post_racks
- RAS Reliability, Availability, Serviceability
- RLU - Rack Location Unit (1 BEU + 1 EPU )
- ROI - Return On Investment
- RAID - Redundant Array of Independent Disks
- RU - Rack Unit (often abbreviated U), a unit that describes Chassis or Enclosure height ( 1U = 1.75 inches)
- SAN - Storage/system Area Network
- SC - Server Cluster
- Six Forces Model - http://en.wikipedia.org/wiki/Six_Forces_Model
- Six Sigma - a specific BPM process, see http://en.wikipedia.org/wiki/Six_Sigma
- SWOT - Strengths, Weaknesses, Opportunities, Threats more at: http://en.wikipedia.org/wiki/Swot_analysis
- Targeted Cooling - practice of removing heat at the source, such as attaching vent hoods to cabinets instead of using CRACs
- TCO - Total Cost of Ownership
- CMDB - Change Management Data Base, see ITIL
- UV - Utility Vault, see http://en.wikipedia.org/wiki/Utility_vault
- VLAN - virtual local area network
- WAN - wide area network
I.6.1 Parapet
A parapet in a rampart. For the purposes of Lotus Green DC fortified data center facilities, a parapet is a single fortified tower (small castle) that is mostly or fully underground, and is integrated with a rampart.
rampart: an earthen embankment that surrounds the parapet and functions as a defensive wall and insulator.
references
defensive wall http://en.wikipedia.org/wiki/Defensive_wall
parapet http://en.wikipedia.org/wiki/Parapet
rampart "A type of defensive wall consisting of a low earthen embankment topped by a parapet or palisade" http://en.wikipedia.org/wiki/Rampart
I.6.2 Green definition
Green represents environmental friendliness[1] and sustainability[2]. Any definition would have to encompass the principles and concepts[3]. Measuring sustainability[4] and green accounting[5] are key components to making green decisions ie. living green.
1. http://en.wikipedia.org/wiki/Environmentally_friendly
2. http://en.wikipedia.org/wiki/Sustainability
3. http://en.wikipedia.org/wiki/Sustainability#Principles_and_Concepts
4. http://en.wikipedia.org/wiki/Sustainability_measurement
5. http://www.eoearth.org/article/Green_accounting
I.6.3 Pod name : Parapet
What should each of the circular data center rooms be called? en:parapet
Each Lotus Green data center building structure has characteristics of:
- module
- castle
- bastion
- a parapet in a rampart of a fortification
- bulwark
- vault - tends to be horizontal orientation
- tower
- crib
- pit
- nacelle - covering of a (heat producing) aircraft engine, small boat (of a convoy of boats)
- silo - risky in that "silo" conveys a simpler structure than this
- stupa - as in Kalachakra stupa ( http://en.wikipedia.org/wiki/Kalachakra_stupa ) and particularly the Great Stupa of Nepal ( http://en.wikipedia.org/wiki/Boudhanath and perspective view at http://monlam.org/images/boudhastupa.jpg ). Any religious significance of the structure is not consistent with the structure's purpose.
- pod - used by Sun/APC for portable container data centers
- watchtower - not consistent with function of structure
I.7 DC Numbering System
Dimensions of Expertise
- Communication
- Network
- Structure/Mechanical
- Electrical
- Plumbing
- HVAC/Mechanical
- Zone (within or relating to property)
- Glossary
- Other
Documentation
- Requirements
- power
- cooling
- network
- site
- structure (weight,space)
- security
- Drawings
- Labels and signage
- Procedures
- Alarms and monitors
- Throws and controls
- Standards and compliance
- Parts catalog
- manufactured parts
- assemblies
- purchased parts
DC model numbers
..should refer to "max number of cabinets", "level of reliability", and "peak power consumption per cabinet" since these are the most significant factors that limit everything else.
- maximum number of cabinets (multiples of 6)
- 6,12,18,24,30,36..
- redundancy (level of reliability).
- 1N (t1)
- 1N+1 (t2)
- 2N (t3)
- 2N+1
- 2(N+1) (t4).
- peak power consumption per cabinet (power density).
- 2kW
- 5kW
- 10kW
II Requirements
Build green* data center structures in smaller, moduler sizes (around 1000SF), to help manage growth through incremental replication, and so that each structure evolves from continual improvement processes
dimensions of systems
- Communication
- Electrical (power)
- HVAC / Mechanical (cooling)
- Network
- Other (security etc)
- Structure / Mechanical (and weight / space)
- Zone (within or relating to property)
* What is green? see Green
II.3 HVAC / Mechanical (cooling)
Passive cooling is priority over active cooling.
One possibility to is wrap or cap the parapet with metal in a configuration similar to an electronics heatsink. http://en.wikipedia.org/wiki/Heat_sink
II.6 Structure / Mechanical
One data center function is as a fortress. Wikipedia presents a useful summary of the evolution of structural fortifications ( http://en.wikipedia.org/wiki/Fortification ).
The goals of super scalability and redundancy can be applied to the physical structure as well networking and software infrastructure.
History proves that building structures in circular forms of only a few meters in radius maximizes stability, durability and provides best heat/cold characteristics of any shape. Circular forms have the least amount of wall area per floor space, resulting in less build resource requirements and less heat loss/gain surfaces.
The Kagome lattice ( http://en.wikipedia.org/wiki/Kagome_lattice ) appears to provide the perfect balance of redundancy in fortification, networking, power and climate control while minimizing paths of inputs and outputs. Images of current variations on this pattern are in http://lotusgreendatacenters.com/forge/files/.
The structure consists primarily of 6 circular structures, each a data center en:parapet. In the image below, the parapets are represented by small circles in a hexagonal pattern. The flower-like pattern represents a raised soil "island". The central circle may be used for a separate power generating facility or control area, depending on location specific requirements. The outer leaf-like star formations may represent cooling ponds or wells, soil embankment or hedge thicket etc. depending on location specific risks and resources also.
Wikipedia has a useful summary on Star Forts ( http://en.wikipedia.org/wiki/Star_fort ), which resemble a single unit of a complete Lotus Green Data Center:
Threats to structures:
- direct attack / Wikipedia provides a historical summary of siege tactics and trends http://en.wikipedia.org/wiki/Siege
- weather (water/humidity/wind/lightning/ice/flood) / environment
- earthquate / environment
- fire / environment
- industrial accident / environment
- vibration / environment
- "impossible" accidents / physical (potential, kinetic) energy in/around facility
- "impossible" accidents / chemical potential in/around facility
- "impossible" accidents / electrical
III Drawings
See the files section of the forge for current information, such as:
- renderings in 3D using Google Sketchup (see "SSOYE Koan Files" at: http://lotusgreendatacenters.com/forge/files-storage/
- Floor schematic: dc-floorplan-2.gif or dc-floorplan-2.odg or dc-floorplan-2.pdf
- Floor schematic calculations: dc-floorplan-2-calcs.ods
IV Labels and signage
V Procedures
This page will list procedures.V.1 Decision-making priorities
in order of highest priority first
- safety - low fire danger, low bad air danger, low shock hazard, structurally sound with "fail-safe" secondaries for technicians and for equipment in case of shelter failure
- green - use nontoxics, sustainable practices and options even at a greater cost or lower efficiency etc.
- climate-control - keep climate temperature and humidity within equipment operating range
- resilient - greater than 10 year life expectancy, able to handle extreme environmental conditions, including earthquake, flooding, weather / lightning, extended seasonal heat, extended seasonal cold, high water-table
- low energy input - minimize operating power input requirements
- economical - low maintenance, secure, long-life cycle, recyclable (able to be converted for other uses)
- scalable - must be repeatable within a defined surface area
- versatile - able to be deployed in a variety of locations with minimum (or predictable) variation