Role   | 
 Members     | 
 Primary Responsibilities   | 
 Communication   | 
 Sponsor   | 
 Christine Meholic   | 
	- Provide overall direction, goals & funding
 
	- Approve charter, scope, milestones, budget
 
	- Remove obstacles
 
 
 | 
	- Monthly written status report
 
	- Invitation to attend steering committee 1st Monday each month
 
 
 | 
 Steering Committee     | 
	- Bart Dahlstrom
 
	- Wendy Bastos
 
	- Kevin Lyons
 
	- Ken Levie
 
	- Gillian Emmons
 
	- Christine Meholic
 
 
 | 
	- Provide oversight, schedule resources
 
	- Define roles & responsibilities
 
	- Set standards, guidelines, processes, metrics
 
	- Remove obstacles, resolve issues
 
	- Approve go/no go decision
 
 
 | 
	- Monthly steering committee meetings - October - January
 
	- 10/5/2009 (Tentative)
 
	- 11/2/2009 (Tentative)
 
	- 12/7/2009 (Tentative)
 
	- 1/7/2010 (Tentative)
 
 
 | 
 Project Manager     | 
 Ken Levie   | 
	- Complete project on time, on budget
 
	- Manage overall project: plan, track progress, resolve issues, escalate when necessary, ...
 
	- Communicate: with project team, sponsors, steering committee, stakeholders, broader community
 
	- Ensure appropriate business and IS&T resources are assigned to project tasks
 
	- Coordinate work among project teams, data warehouse, OIS, IS&T help desk, ...
 
 
 | 
   | 
 Transport Manager     | 
 John Tuttle     | 
	- Define process, lists, tracking procedures
 
	- Plan and track effort to move pending transports to production before freeze
 
	- Manage any critical transports during freeze to ensure they are included in upgrade
 
	- Manage all transports related to support pack project
 
 
 | 
   | 
 Core Team: Technical Leads     | 
	- Basis/security - Ron Parker
 
	- ABAP, ITS - Wai-Ming Li
 
	- Web - Rich Murphy
 
 
 | 
	- Prepare environments
 
	- Apply support packs 
 
related to support pack project * Execute SF3 modification testing; Resolve & retest issues 
	- Unit test (joint with functional team)
 
	- Analyze & resolve issues
 
	- Execute cutover activities
 
	- Coordinate work of basis team and developers
 
 
 | 
 | 
 Core Team: Functional Leads     | 
	- HR/Payroll - Frank Quern
 
	- Financial - Mary Ellen Gearin
 
	- EHS, Travel -Lee Collier
 
	- Procurement (xECAT3), Facilities, Parking - Rita Zhovnirovsky
 
	- ECAT3 - Elda Prudden
 
	- AP, Smart - Ken Levie
 
	- Functional Team leads - Julie Block, Bob Romanowicz, Hao Wen
 
 
 | 
	- Unit testing (joint with technical team, track and report process)
 
	- System integration testing (define scope, update & execute scripts, track and report progress)
 
	- User acceptance testing (assist if needed)
 
	- Serve as primary liaison with business owners
 
	- Analyze & resolve issues
 
	- Execute cutover activities
 
	- Coordinate work of business analysis and business owners
 
 
 | 
 | 
 Core Team: QA     | 
	- Wendy Bastos
 
	- Amanda Gilbert
 
 
 | 
	- Define & communicate process & templates to manage test cases
 
	- Set standards for quality assurance process
 
	- Oversee QA work on the project
 
 
 | 
 | 
 Extended Team     | 
	- sais-sap@mailman.mit.edu 
	
		- which includes all SAIS & Data Warehouse staff supporting SAP.
 
		- Conact Kevin Lyons, Wai-Ming Li or Bart Dahlstrom if you are not on the list and think you should be.
 
	 
	 
 
 | 
	- Perform tasks as directed by core team leads
 
 
 | 
 | 
 Business Owners     | 
 
  
	- GL Reporting, JV - Magdalene Lee
 
	- HR/Payroll - Scott Ball
 
	- HR/Benefits - Judy Raymond
 
	- Facilities - Lisa St. Croix
 
	- Stockroom - Tammy Doyle
 
	- EHS - Laurie Veal
 
	- Spons. Billing - Doug Levie
 
	- Gen AR - Donna Cairns
 
	- Cashiers - Cheryl Whelan
 
	- Property: Kevin Milligan
 
	- Fund Centers: Peggie McGrath
 
	- IST Telecom: Allan Wallace
 
	- Tech Review: Jim Coyle# AP - John Larkin
 
	- Procurement - Mary Bacci, John Doyle
 
	- eCAT - John Doyle
 
	- Travel - John Doyle, Paul Arsenault
 
	- SMART - Mary Bacci, John Larkin
 
	- OSP - Steve Dowdy
 
	- OBO - Rob Slauzis
 
 
 | 
	- Perform user acceptance testing (define scope, update & execute scripts, retest as needed)
 
	- Report issues via RT
 
	- Train end users if any changes are discovered (none anticipated)
 
	- Sign-off that updated system is accepted for your business area and support packs can move to production
 
	- Perform any business cut-over activities
 
	- Validate production system (define criteria, validate system)
 
 
 | 
 |