Enhanced%20Data%20Center%20Management%20(Aperture)%20Project%20Status

1
Enhanced Data Center Management (Aperture)
Project Status

• David J. Ritchie
• CDO/Operations
• January 6, 2004

2
Present Approach Provides

• Smart Pictures Product from Aperture.
• A GUI I/F to a space management database.
• Easy RW accessibility for a single individual
  (Phil Lutz).
• Some web capability as in
• http//cd-aperture.fnal.gov/scripts/spserver/projl
  ist.dll

3
Shows A Variety of Information

• Data Communications Wiring
• Power Grid
• Cable Trays
• Relay Racks
• System Assignments (KTEV, CDF, DZero)

4
A Data Comm Example
5
A Floor Example
6
But Difficulties

• Hard for RW use by multiple individuals.
• No rack view plan view only.
• No work flow updates via unstructured e-mail,
  post-it notes, or worse.
• Maintained separately from Equipment Database.

7
The Argh Experience
8
The Solution - 1

• Upgrade to VISTA product from Aperture.
• Web Access formultiple users (less Argh!).
• Rack View essentialwhen it takes ½ hourto
  really view it.
• RW access fordesignatedindividuals.

9
The Solution - 2
10
Tasks 1

• Web enable existing Aperture product.
• Continue assigning of space by CDO/Operations.
• Introduce provisioning, recording of
  use/connectivity of the assigned space by
  designated individuals in other CD Departments.

11
Tasks 2

• Implement equipment install workflow.
• Interface to existing MISCOMP Equipment Database.
• Provide a locator service for alert software,
  e.g.
• NGOP show a floor, area, and rack display.
• MetaSys break out equipment according to
  circuit.
• Remedy locate failing equipment targeted by
  user report.

12
Issues

• Internet Explorer only for full functionality
  (not clear how limited for other browser)
• ?

13
Project Timeline and Scope

• Three phases
• Web access
• Work flow implementation
• EquipDB interfacing
• Three scoping options
• HDCF
• HDCF and NML
• HDCF, NML, FCC Data Centers, WH7SW(?)

14
The Matrix
Notes Annual Maint. 18 Sq. ft. (9.18 to 3.99) Prof. Svcs. 9K/wkT/E HDCF (4K sq. ft.) HDCF NML (8K sq. ft.) HDCF, NML, FCC, WH7SW (29K sq. ft.)
H/W (2 PCs, IIS, SQL Server) 6K 6K 6K
Web Access 36K 58K 115K (10 disc, 8K sqft incentive)
Web Access Workflow 159K (8K sq. ft. incentive)
Prof. Services (Inst 2d, Train 8d, Prep 2d) 28K 2 Weeks 28K 2 Weeks TBD (Non-self-install 5-9 Weeks 45K-85K)
EquipDB I/F TBD TBD TBD
15
A Middle Strategy

• Stay within budget by.
• Delaying workflow and rely on designated
  individuals.
• Adopting middle scope which allows self-install
  in a clean slate.

16
Phase 1

• Implement web accessible plan and rack view for
  the scope selected.
• Provide
• power route (device to panel).
• networking route (board to switch).
• People Phil Lutz, Designated CD Department
  tracking individuals.

17
Phase 2

• Implement work flow piece so that separate CD
  organizational units of the CD can record their
  actions with more parallelism.
• People Phil Lutz, David Ritchie, Designated CD
  Department install individuals.

18
Phase 3

• Interface the Miscomp equipment database and the
  Vista database together so that relevant updates
  to one will be populated in the other and vice
  versa.
• People
• David Ritchie, Phil Lutz as required.
• 1 FTE for 3 months from Database Systems Group.
• Aperture or other consultant.

19
Case Study Target - 1

• Yes, the retail store.
• Four Data Centers 90,000 sq. ft.
• Strong support from CEO on down for way of doing
  business (regulated access).
• A stringent need in their business for stability
  and reliability.
• Vista product - since v1.0.
• Mainly interact through Equipment Install part.
• Other (Eq. Move, Dispose, Change) too generic for
  their particular business processes.

20
Case Study Target - 2

• Very happy and positive on the core product
• Should expect to have to adapt the generic out of
  the box processes to our specific circumstances
• Amazing in what it lets them do
• 50,000 network paths
• 3,000 power breakers

21
Case Study Target - 3

• They have locked down their data center no one
  enters it w/o having registered their request
  through the appropriate form.
• Started at the time they built a new data center
• Defined policies and procedures by which changes
  were to occur.
• Track access through the Vista product. Its very
  easy.
• Recommendation get the individuals involved to
  define the processes

22
Case Study Target - 4

• Prior to Vista, they were running the place
  without defined processes.
• Random people would put in devices.
• Networking as a separate group.
• People with devices to install making independent
  phone calls to the networking people.
• To get Vista off the ground, Facilities Planning
  partnered with the Networking Group.

23
Case Study Target - 5

• Two people spent two days defining high level
  processes
• Who provisions what.
• Who does what.
• Avoided getting into nitty-gritty (I.e., specific
  fields).
• Sat with platform owners and worked out
  specifics of processes.

24
Case Study Target - 6

• Aim was to have web forms.
• not too difficult to fill out.
• Reasonable balance with regard to data collection
  versus utility of info.
• Presently, their system works to the level of
  dropping symbols onto a drawing as a way of
  recording the installation.
• 70 80 installs/month.

25
Case Study Target - 7

• Knows no other products that do this level of
  data center tracking
• Others are too CAD-like and therefore more
  labor-intensive and less flexible

26
Case Study Target - 8

• Fall 2001 approached Aperture in with idea of
  implementing equipment install on top of Smart
  Pictures.
• January 2002 testing and development
• May 2002 Opened Data Center
• June 2002 Went production
• Another 6 8 months shaking it down.

27
Market Analysis

• An afternoon with Google.
• Examined several products.
• Either CAD-oriented.
• Forms and note card oriented.
• Little graphical and flexible.