...
- Scope
- getting data and making it available and easy to use
- seen as interim solution as we evolve our change management tools
- Requirements
- team to review by 2/17/11
- sign off by sponsor by beginning of March (3/7 sponsor meeting)
- Data Dictionary Reconciliation
- team to review for 2/17/11
- PS to follow up with Alison on Catalog taxonomy and share dictionary
- confirm categories/services definitions
- catalog has 2 levels
- portfolio has 3-4 possible levels
- drives HD ticket categorization
- reconcile
- confirm categories/services definitions
- Oliver will send out sample architecture
- team will begin planning data collection and populate fields
- keep data in transferable format
- Library of Procedures
- escalation process complete
- CG and GZ to look at 2-3 more processes to define
- use process swim lanes as guide
- Vehicle
- make it part of staff work flow (easily updated)
- drupal - could we stand up our own instance?
- distributed work flow
- change management
- audit capabilities
- future tool, but moving format with data collection in parallel
- will need support plan for drupal instance
- Barbara will look for funding for vm
- RT Stock Replies - doesn't look like it will meet requirements
- Hermes - may work for initial data collection (structure and prototype)
- will need to limit staff who edit and contribute as work flow is not supported
- drupal - could we stand up our own instance?
- make it part of staff work flow (easily updated)
March 7, 2011
- technology options
- use IS&T Website templates, copy to new instance, and populate
- need access controls (IS&T only)
- set up a multi site drupal instance with DM (RAFT On Line Help)
- needs support model
- consider Remedy demo for Service Portfolio module
- use IS&T Website templates, copy to new instance, and populate
- in general, we need to formalize process to capture change requests and responses
- we need to move procedures to functional place: Hermes
- need to help staff interact with these procedures (change management)