...
- Asset Management Console and drill down
- configure search criteria under app preferences
- tabular view
- BMC Atrium demonstration
- Atrium Explorer and drill down
- graphical view (right click and edit for tabular view)
- Federation Manager
- Class Manager
- Atrium Explorer and drill down
- Remedy CMDB issues:
- Service Families absent from CI categorization
- Documents are uploaded separately (would need to create a CI that was a "bundle" and relate to several products/offerings)
- Asset management console only shows parent or child relationships, not both together
- The interface and categorizations does not map to the way staff think or use the information
- Can't join data the way we want (brands, aka, etc)
- Limited in terms of easy of use and approachability
- Glossary of terms is from Remedy and not true ITIL
- Remedy (by design) limits participation in knowledge management
- Administration of data is locked down to small group
- Dynamic changes/updates are not as supported
- View in Atrium explorer is limited
- Drill down takes time
- Scroll over does not stay visible for very long
- Search is limited (does not include text in notes, etc where branding and aliases are critical to get information quickly)
- Looks like we get 60% of our requirements met, but not 80%
- API issues:
- Not readily available (not Web 2.0)
- Based on pre populated forms in Remedy
- We would e building another application we would own
- Do we have the skills to build and support/maintain?
*Additional considerations:
- Do we have the skills to build and support/maintain?
- Priorities for Remedy
- Expanding change management to more teams
- Exploring problem management and incident management
- Knowledge management (Service Portfolio, Knowledge Base and IS&T Website) NOT priorities
- We have existing systems or prototypes for this information
- Service Portfolio landscape could change drastically over next 2 years, as could Remedy
- Take a more targeted approach to building the Service Portfolio
- Reduce investment overall but have something sooner (ROI)
- Reduce resources/costs
- Reduce timeline
- Reduce requirements
- Reduce investment overall but have something sooner (ROI)
- Take a more targeted approach to building the Service Portfolio
- Next steps:
- Review the final draft of the project proposal for 6/21
- Team will prepare edits to narrative
- Changes to resource plan
- Changes to support plan
- Dave will review cost and time estimates
- Team will prepare edits to narrative
- Review the final draft of the project proposal for 6/21
July 11, 2012
August 169, 2012
September 19, 2012