1 / 16

CISL Resource Information System

CISL Resource Information System. High Level Kickoff Meeting 10 January 2006. Notes. As a stakeholder, what do you need from/in the accounting resource “database” to perform your task/job/function? Database Redesign is the action which needs to be taken

norris
Télécharger la présentation

CISL Resource Information System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CISL Resource Information System High Level Kickoff Meeting 10 January 2006

  2. Notes • As a stakeholder, what do you need from/in the accounting resource “database” to perform your task/job/function? • Database Redesign is the action which needs to be taken Need a name for the database itself: • Resource Information System (RIS) • Resource Information Repository (RIR) • Resource Control Facility (RCF) • ….some clever acronym….

  3. Agenda • Project Need • Goals • Business Scope • High Level Requirements • Project Organization • Timeline • Stakeholders Requirements

  4. The Need: Old Paradigm • Computers did not change frequently • Computing resources were at one location • compute, storage, analyze • NCAR was an Island

  5. The Need: New Paradigm • Approx. 3-year cycle on computer changes • 2004-2005: • blackforest, lightning, bluevista • frost, coral, pegasus • 2006 • ICESS • Computing resources may be at multiple locations • Teragrid Partner ? • Support of new/other applications (Enact, Remedy, Directory Services?, etc) • Leverage finite staff for database support/use • Account: compute cycles, bytes archived, byte moved(?), byte residence on SAN, use of data/viz facility

  6. Goals • Design a flexible database to support new resource-use paradigm • Division-wide acceptance • Easy access • Internal, incoming dataflow to DB • Internal, outgoing dataflow to stakeholders • Verifiable • Follow industry standard best practices • Warehouse? • method to deal with old data • new data storage

  7. That’s HUGE How do we do this?

  8. NCAR Business • NCAR provides computing resources for the scientific community • Atmospheric and related sciences • Community could grow (NSF 625, Geosciences, etc.) • NCAR must ensure access for all members

  9. CISL Business • Allocate resources • facilities, communities, laboratories, divisions, PIs, groups, projects, users, etc. • Monitor Usage • for example, utilization, MSS archive size • Report Usage (multiple consumers) • Usage statistics by Lab, PI, Group, User, NSF Program, CSL PI, Univ PI, etc. • Regulate Resources • Fair-share access • “Hold” over-users • Support Operations • Account provision • Security (OTP)

  10. What’s the plan?

  11. Core Project Team • Project Manager: Lana Stillwell • Technical Development Team: AISG

  12. SDLC (Team Tasks) • Define high level goals (Charter) • Discover and Document Requirements • Risk Analysis • Development Costs • Stakeholder Costs (careful: initially hidden) • Review and Approve • Architect and Design • Implement • Stages? • Beta?

  13. Timeline Factors • Allocations Cycle • NCAR January 2006 • CSL March 2006 • Univ April and October • ICESS Delivery and Deployment • Winter 2006-2007

  14. Timeline • Target Beta Version • Define Beta Version • October 2006 • parallel execution/comparison with existing database? • Regular Updates to Stakeholders from Core Project Team

  15. Stakeholders (incomplete)

  16. End

More Related