1. 10 January 2006 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. 10 January 2006 Agenda Project Need Goals Business Scope  High Level Requirements Project Organization Timeline Stakeholders Requirements

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

5. 10 January 2006 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. 10 January 2006 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. 10 January 2006 That’s HUGE How do we do this?

8. 10 January 2006 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. 10 January 2006 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. 10 January 2006 What’s the plan?

11. 10 January 2006 Core Project Team Project Manager:Lana Stillwell Technical Development Team:AISG

12. 10 January 2006 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. 10 January 2006 Timeline Factors Allocations Cycle  NCARJanuary 2006  CSLMarch 2006  UnivApril and October ICESS Delivery and Deployment  Winter 2006-2007

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

15. 10 January 2006 Stakeholders (incomplete) StakeholderRepresentativeRoleActivity PolicyTom BettgeCustomerRegulate Allocations Utilization Ginger Caldwell Tom Engel Customer Allocations, usage, reports Utilization, job efficiency SSG/DASGCustomerProvide supercomputer/data-viz statistics Consume active account information to manage resources NETSMarla MeehlCustomer MSSGCustomerProvide MSS statistics CPGLinda LaBrieCustomerUser identity, OTP Token Activation SecurityLynda/RichCustomerUCAS DSGGreg WoodsCustomerMail information ApplicationsNate WilhelmCustomerConsume SCD Data AISG – Core TeamLana M. StillwellProject Manager DB Developers Accounts Managers Developers, database management, user account management

16. 10 January 2006 End