You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 73 Next »

Service Portfolio Prototype

The Service Catalog team (Rich Murphy, Alison Bell and Christine Fitzgerald) are invited to participate in all Sponsor meetings through April 2012 (when the website launched), as we share the same Sponsor (Barbara Goguen) and our projects have dependencies on one and other.

January 10, 2011

  1. Review of Service Portfolio Scope
  2. Review of Service Portfolio time line Service Portfolio Project Plan Revisited January 6, 2011
  3. Review of Service Catalog status
    1. RFP
    2. draft categories and services by 3/1/11
  4. Agreements:
    1. Portfolio will feed the Catalog
    2. Catalog will go with what is currently on the IS&T Website until Portfolio is complete
    3. continue joint sponsor meetings

February 9, 2011

  • 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
    • 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

March 7, 2011

  • technology options - Barbara will review with Marilyn this week
    • contract DCAD to build in drupal
    • 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)
      • could be vanilla out of the box drupal
      • needs support model - will Rich be able to absorb on his team in future?
    • consider Remedy demo for Service Portfolio module
      • pushing technology implementation out further
  • interim work - prototype for June 15, 2011
    • "digesting the data"
      • work on refining the model and creating the service maps
      • enumerate other categories to be mapped
      • walk through an entry at senior staff (Pat to set up)
      • populate info in mind mapping software
    • base assumptions
      • map out professional services separately to see where they may fall
        • windows desktop support
        • browser support
  • Library of Procedures update

April 4, 2011

  • draft presentation for Senior Staff 4/7: IST Service Portfolio Entry.ppt** review of high level categories
    • review of Services (3-4) under each category
    • review of solutions under 2-3 Services (in Communications category)
    • drill down into Exchange and Outlook 2011

May 2, 2011

  • team is now split into two subgroups, each mapping five categories in Catalyst over the next 6 weeks
  • present progress to senior staff 6/2/11
    • categories with definitions
      • Services
        • solutions
  • continue to share information with Catalog team

June 6, 2011

  • mapped top three levels of Portfolio in Catalyst
  • shared definitions for each Service Family with Catalog
  • reviewed Catalog taxonomy draft
  • reviewed senior staff presentation currently scheduled for July 7th Service Portfolio Progress Update.pp

July Sponsor Meeting Cancelled - Presentation to all Senior Staff July 7, 2011

August 15, 2011

  • Service Portfolio Brainstorm August 11, 2011
  • review of portfolio database business case
    • Barbara will socialize with sr staff
  • update on data model progress
    • to be finalized by end Sept and reconciled with requirements
  • portfolio gathering content October to December
  • update on distributed sw life cycle processes/recommendation - rescheduled for 8/22
  • update on next steps with service catalog team
    • meeting 8/18
      • mechanics of building content
      • prototype for portfolio
      • catalog confirm content fields for consumption
    • current status of catalog
      • content gap analysis end August
      • need to develop plan for developing new content
      • will look at whether Drupal has ITIL module

September Sponsor Meeting Cancelled - vacation schedule and Back to School

October 21, 2011

  • review prototype approach and plan
  • reviewed discussions with Catalog team

November Sponsor Meeting Cancelled - holiday schedule

December 15, 2011

  • sponsor report: Service Portfolio Prototype Sponsor Report Dec2011.doc
  • review project plan: Service Portfolio Prototype Project Plan Dec2011.xlsx** info/demo session in February for IS&T staff
    • data collection: in addition to team contact information, capture hours of operation
    • Remedy and Website (catalog) need to think about data reconciliation and maintenance cycle
  • status on distributed software as a service
    • Barbara still needs to socialize with ADs
    • kick off meeting with original group (including Finance and Procurement) once we have green light

January 5, 2012

February 6, 2012

March 12, 2012

April 2, 2012

April 23, 2012

  • reviewed options for portfolio implementation: Portfolio Options.xlsx
  • team will move forward with Remedy exploration

June 7, 2012

  • 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
  • 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:
    • 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
  • 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
    • meet with KM Core and give status update 6/14

ITSM Tool Evaluation

Barbara Goguen and Mark Silis are cosponsoring the ITSM Tool Evaluation that will kick off at the end of August 2012.

July 11, 2012

  • Barbara and Mark in attendance
  • Create a picture of what an ITSM Program would look like for our department
    • Statement of Direction
      • articulate a vision
      • identify benefits - why are we doing this
        • visibility into processes
        • resources become interchangeable to some extent
        • better analysis
        • some consistent process where we had none
      • identify pain points/biggest gaps
      • identify stakeholders
      • identify places where we have the potential for success
        • base on lessons learned from Remedy Change Management implementation
        • what parts make sense in our environment
        • exclude areas where processes and/or tools are already embedded
          • we don not want to replace existing processes or tools
        • include areas where we can collect, connect and automate ("glue together")
          • ITSS incident and response
          • request fulfillment
          • problem management
      • clearly define what is in and out of scope
        • limit to Operations & Infrastructure and Customer Support
        • articulate how far down the slope we go
      • articulate milestones and time line
        • digestible chunks of work - the sequence of events to do this right
        • what we get at each step along the way
  • Barbara and Mark cosponsor this larger effort once we have agreement on the vision and the work
  • projects come next
    • for example, Remedy CMDB build out with custom UI (service data but not asset data) based on prototype
  • deliverable draft statement for next sponsor meeting 8/22/12

August 22, 2012

  • review ITSM Statement of Direction with Barbara and Mark: ITSM Statement of Direction Final Draft.docx
  • next steps:
    • lightweight evaluation of ITSM tools 9/15 - 10/31
      • look at all modules and interfaces
      • use customer perspective
      • identify any show stoppers
      • commit to ONE TOOL by 10/31
    • rework ITSM Statement of Direction
      • narrow scope to 18 months
      • delineate more tangible deliverables (name services, the processes we would apply and the value proposition)
    • meet with KM Core and give status update 8/23

September 27, 2012

  • Mark in attendance
  • use cases for ITSM demos: ITSM Tool Evaluation FY2013.docx
  • review milestones: ITSM Tool Evaluation
  • feedback on Remedy OnDemand and RemedyForce demos
  • final decision should be accompanied by resource plan:
    • ongoing maintenance and baseline support
    • training
    • development
  • need resource commitment before we move forward with any implementation

October 29, 2012 cancelled due to Hurricane Sandy

November 7, 2012

  • ITSM Tool Evaluation FY2013.docx
  • follow up with vendors by 11/15/12
    • still deliberating internally
    • initial licensing proposal would be helpful in terms of evaluation
      • licensing
      • professional services
      • additional tools
  • business case for tool acquisition by 12/15/12
    • include maintenance and support needs
    • limit scope to internal IS&T use only
    • emphasize improved customer experience
    • need for improved support analyst interface
  • Mark and Barbara will bring finalized business case to senior staff January 2013
  • once we have direction, internal communication to IS&T
  • need to think about disposition of Request Tracker for separate community communication

December 21, 2013

  • Mark and Barbara agree that we need to move forward with implementing more parts of our service management processes in Remedy OnDemand
  • they agree that:
    • it makes sense to expand on our change management implementation
    • that we move forward with service request and service portfolio
    • at the same time, there is work that can start within RT to streamline incident and problem management processes preparing for future Remedy implementation
  • The team should move forward and make the financial and time investments necessary, within reason, to:
    • expand our Remedy licensing/training
    •  develop a compelling Remedy ITSM prototype that illustrates the potential benefits of an ITSM rollout for the IS&T organization

January 31, 2013

 Status updates:

  • Remedy 8 Prototype
  • Knowledge Management
    • demo of Remedy 8 Knowledge Base scheduled for 2/7 (Release Core and KM Core)
  • Change Management
    • initial planning meeting scheduled for 2/4 (service offerings and stakeholders)
    • roll out process planning meeting scheduled for 2/13
    • finalize roll out plan by 2/20
    • need to identify PM and BA for this effort
  • No labels