| A Critical Challenge | |
| Strategic Partner Selection | |
| RSFT's Modular Approach | |
| Phase 1: Discovery | |
| Phase 2: Engineering | |
| Phase 3: Construction | |
| Five Key Success Factors |
The University Medical Center in Tucson Arizona
When the 365-bed University Medical Center (UMC) in Tucson, Arizona made a decision to relocate and upgrade its 2,300 square foot data center,
their MIS Director, Ray Harwood, faced a challenge that would have an impact on everyone who came in contact with the hospital. Particularly important were the people who relied most heavily on UMC's electronic brain center -- the critical-care patients, medical researchers and academicians of UMC. These last two groups included the closely affiliated University of Arizona College of Medicine and the University Physician's group practice, which included faculty physicians from the UA College of Medicine.Of chief concern at any healthcare facility are the lives of the patients who depend on the integrity of diagnostic information and medical records. At UMC, the data center played host to the hospital information system -- which includes patient admitting, scheduling, and billing -- in addition to human resource and material management systems (supplies). Other key systems hold data from laboratory tests, the pharmacy, electronic "charting" of patients by nurses, and data from fetal-monitoring equipment. In the case of UMC, there was the added dimension of medical research and the hospital's function as a training facility for physicians. Ranked as one of the best hospitals in the United States and a pioneer in new medical technologies, UMC has earned special recognition for its cancer and heart programs. Its medical leadership is also evident in the heart transplantation program, which boasts one of the best survival rates in the world, and other programs throughout the hospital -- starting with the 300 babies born there each month.
A Long-Awaited Facility
Years before, the hospital had recognized the limitations of the existing 2,300 square foot data center housed in a series of modular buildings that were never intended for permanent use. To remedy the situation, the hospital reserved 4,500 square feet of space in the basement of the new, four-story North Wing
that broke ground in 1993 and was completed in the following year. In anticipation of its future role, the basement in the North Wing was built with an 18-inch suppressed-slab foundation in order to accommodate the raised flooring that would eventually be installed in the planned data center.By 1995, it was time to begin planning for the new data center, and Ray Harwood was given the assignment. Along with his staff, Harwood established the overall objectives for the new data center, assembled the information and resources, and identified a method so that the project could hit the ground running once a budget was allocated in 1996.
As in the case of highly focused organizations everywhere, although UMC's in-house Facilities Maintenance staff was familiar with many aspects of creating a new data center, it did not have the highly specialized expertise and resources necessary for completing such a complex and infrequently executed project. Since UMC's computing environment was based on systems built by the Digital Equipment Corporation, Harwood naturally requested Digital's assistance and input. The experts at Digital immediately introduced UMC to Rancho Santa Fe Technology (RSFT), a company
with a history of working with Digital as a strategic partner to define, design, and build complex data centers. Harwood requested a formal proposal from RSFT, and to provide balance, he also requested a proposal from one of the world's most widely recognized computer system vendors.
RSFT proposed a three-phase approach to the project that was completely modular granting UMC the freedom to complete Phase 2 or Phase 3 of the project with another vendor or using in-house resources:
| Phase
1 -- Discovery. RSFT's in-house architect would conduct a series of interviews with the core members of UMC's information systems team to reveal how the hospital uses information and how it planned to do so in the future. As a result of this interactive process, RSFT would determine space, power, data flow, security, and user requirements including the inter dependencies and critical functions taking place in the facility. Deliverables for this phase would include bubble diagrams to depict the two-dimensional relationships of these functions, preliminary floor plans and sketches to help envision the new facility, and a final conceptual layout with three-dimensional views and an estimate of the square footage. |
|
| Phase
2 -- Architectural Engineering. RSFT would integrate all of the specialist's professional contributions and develop the conceptual layout into CAD-generated construction documents including a floor plan layout, elevations, and cross sections. These show all the structural elements, the placement of computer equipment, mechanical and electrical systems, raised flooring, ceiling clearances, and safety systems. When the documents were 25% complete, RSFT would interview the jurisdictions having authority over the project for their early comments. The 60% complete documents would show final placement of all the elements and incorporate all comments, at which time RSFT would submit a preliminary budget and schedule. The 90% complete documents would be submitted to the jurisdictional authorities. When RSFT incorporated the final changes and held all of the required permits, the documents would be 100% complete and be turned over with the final project budget and schedule. |
|
| Phase
3 -- Construction. RSFT's on-site superintendent would manage all of the construction trades and coordinate their activities. From a fully equipped office linked to RSFT's engineering staff, RSFT would also keep UMC informed about the progress of the work, conduct regular meetings, and furnish the necessary training upon completion. After providing the as-built drawings and certifications, RSFT would provide final move-in support to ensure a successful transition from the old data center. |
The Other Vendor's All-in-One Solution
The other vendor responded to UMC's request with a proposal to build the facility for a fixed fee and include
d the design for the data center at no cost. On the surface, this consolidated proposal appeared to offer significant cost savings and greater simplicity for UMC, so Harwood placed the RSFT proposal on temporary hold. He then conducted a series of question-and-answer sessions with the all-in-one vendor, and he outlined UMC's requirements and perceptions regarding the data center.After merging all of the stated requirements and performing independent calculations, the other vendor responded with a set of rough blueprints and specifications - along with a bottom-line proposal that would cost UMC less than $500,000. This seemed to be well within Harwood's budget until UMC began to probe individual items in key areas of the proposal. When Harwood inquired about the specific method of interfacing with UMC's existing power grid, it became clear that the vendor had not adequately interviewed UMC's Facilities Maintenance group. As a result, there was no provision for the power interface in the all-in-one package. After Harwood and his team identified a number of similar omissions, UMC realized the value of RSFT's three-phase approach, which began with a pro-active interview process that was structured to draw out all
of the critical information from the parties affected by the project. At this point UMC awarded the project to RSFT.
Phase 1 -- Discovery: Understanding the UMC Data Center and Its Users
With the increasing popularity of specialized interoperable software, client/server applications, and networked computing environments, the traditional model of running most applications on large, monolithic computer systems has become a thing of the past. Whereas floor space, power, and air conditioning used to be allocated in relatively large chunks to each mainframe device, the new computing paradigms offer a much wider range of options. The ability to flexibly configure, reconfigure and expand modular computing resources within standardized equipment racks has created options for "going vertical" and packing much more computing capacity into each square foot of data center floor space. Although it has increased the options for systems deployment, this trend to modular systems has greatly complicated the task of data center planning.
To ensure a comprehensive assessment of UMC's data center requirements, RSFT's senior staff met frequently with UMC's C
hief Information Officer as well as Ray Harwood and his technical team. RSFT developed a complete profile of all existing and planned computing resources, including detailed inter-functional matrices to identify all key dependency and adjacency requirements. In addition, RSFT met with UMC's Facilities Maintenance staff to include their specific requirements and to address any regulatory, fire, and safety code issues. For instance, one critical issue that surfaced early was the fire code requirement for a dedicated exit hallway cutting across part of the data center space. By identifying and incorporating this requirement during Phase 1, RSFT obtained a significant cost and time saving by preventing subsequent redesign and reworking later.At the end of Phase 1, RSFT presented UMC with a full set of analyses and back-up data - detailing existing requirements, functional relationships, growth projections, and other elements. In addition, RSFT presented alternative layout plans for UMC's consideration. The merits, projected costs, and operational issues were discussed for each alternative - enabling UMC to make an informed selection regarding the best layout to meet their needs.
According to Ray Harwood, "Developing a data center is a critical, one-time event that requires participation from a variety of functional areas. It's not something that can simply be defined from the exclusive perspective of the information systems staff, facilities management, or end users,
and it cannot overlook the unique needs of any of these groups. We ultimately selected Rancho Santa Fe Technology to design our data center because they brought together the expertise, the perspective, and the experience needed to blend all of our requirements into a comprehensive design that could be implemented within our real world constraints."Phase 2 -- Architectural Engineering: Meeting Operational and Cost Objectives
After UMC selected one of the Phase 1 alternatives, RSFT submitted a Phase 2 proposal to develop it to full architectural plans and specifications. Once again, if RSFT's bid had not been competitive, UMC had the option to walk away and use another vendor. After reviewing RSFT's Phase 2 bid and witnessing the deep level of expertise that RSFT demonstrated during Phase 1, UMC authorized RSFT to proceed with Phase 2.
A construction budget target of $800,000 was established and, throughout Phase 2, RSFT worked closely with Ray Harwood other UMC staff to identify potential cost risks and value-engineering opportunities to remain within budget. According to Ray Harwood, "As we went through the various design iterations, RSFT did an excellent job of working with our Risk Management staff on safety items and with Facilities Maintenance on code issues. As a matter of fact, we just gave RSFT the contact names for the Arizona State Fire Marshal and the State Department of Health Services, and they directly handled the regulatory contact, worked through the issues, and got all the required signoffs."
Phase 3 -- Construction: Pulling It Together on Site
After completing the data center's design in December 1996, construction began in February 1997. RSFT assumed full responsibility for all aspects of construction. A senior RSFT construction superintendent, Bill Barker, was the on-site project manager and resided at the UMC facility throughout Phase 3.
Bill Barker's role included hands-on management of all construction-related issues such as sub-contractors, quality control, coordination with inspectors from regulatory agencies, schedule monitoring, cost-containment, change orders, and progress reporting to UMC. In addition to conducting formal weekly walk-throughs, Barker provided informal status checks to Ray Harwood and his UMC staff almost
on a daily basis.Construction was completed on schedule and slightly under budget, and the data center was ready for start-up and move-in by July 1997, less than five months after construction began. Instead of shutting down all information systems for a 24-hour period, UMC and RSFT were able to sequence the move into the new facility over a three-day period. The carefully orchestrated transition schedule cut down-time to only four hours per system -- successfully avoiding an unacceptably lengthy disruption of mission-critical computing activities.
Since the initial move-in, UMC has completed more than five major new IS initiatives at the data center - each requiring
the installation of between one and three new server systems. This planned growth was smoothly accommodated because of the built-in flexibility of the data center's design. Not only are the electrical and air conditioning systems designed for easy re-configuration, but the data center was built with a separate staging area adjacent to it for vendors to test their new equipment before moving it into the main computer room. For future growth considerations, RSFT designed the staging area using a de-mountable wall that can be removed or relocated if the main computer room requires expansion.
Five Key Factors for Successful Design and Construction
From the customer’s perspective, the planning, design, and construction of UMC's new data center was an overall success that can be traced directly back to Rancho Santa Fe Technology's in-depth expertise and hands-on involvement. For anyone considering a major data center design and construction project, the following key factors are critical to achieving similar success:
| Discovery (learning about your operation and planning your project) | |
| Architectural Engineering | |
| Construction |