In case you folks are not involved in your local Tivoli user groups, here's
some information I recently received from ("Karen Nickelson"
<karen.nickelson AT hewitt DOT com>).
There are some websites at the end. The Netview line does not appear on
their
radar, as far as I can tell, but it could..... That's up to the users.
Big issues there, daily details and how-to help here, maybe?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
=====================================================================================
To: Tivoli Users Group Community
From: Global Tivoli Users Group (GTUG) Council Representatives
Date: March 3, 2002
Subject: GTUG Newsletter - Issue #1
Remember the days when your enhancement request went into a big bucket
in the sky never to be heard of again? We are here to help you.
Your GTUG Council representatives would like to invite the Tivoli users
community to participate in requirements definition and prioritization.
We would also like to share some news with you on what we have been up to.
Activities
The GTUG Council has been listening to Tivoli representatives from various
levels of the organization on support, training, new product ideas,
communications and ways to ensure both us the customers and our users
groups can be more effective. The monthly discussions are well attended by
your representatives and often result in lively discussions about the
products and the issues which impact us all. Danyel Otteson, Tony Thuy and
Erma Moffett from the Tivoli Executive Relations Offices have been leading
us and ensuring information continues to flow in both directions.
Brief History
June 2001 - Global Tivoli Users Group formed with 12 members from
America & EMEA
September 2001- EMEA members meet at UK Users group
October 2001 - Approved Mission and Charter
November 2001 - Appointed 5 member steering committee
Appointed 2 members to the Tivoli Board of Advisors Group
February 2002 - First steering committee meeting held at Share, Nashville
TN
March 2002 - 23 members represented including Asia/Pacific region
April 2002 - steering committee compiled a list of issues for discussion
and
selected an issue and formally initiated a change request
The Mission and Charter
The Mission and Charter following were approved by the Council in the fall
of 2001.
Mission
'To extend the effectiveness of Tivoli User Groups by providing operational
feedback for the improvement of Tivoli's products and services, working
proactively with Tivoli on planning, strategy and development
prioritisation, and expanding Tivoli User Groups networking capabilities
globally.'
Charter
2. Objectives - This organisation is a Tivoli User Group driven forum,
with primary objectives to: -
2.1. Provide guidance to Tivoli on product strategy and direction.
2.2. Act as a conduit for external Tivoli communication, facilitating
the dissemination of information to the customer base.
2.3. Act as a focal point for customer issues, and through lobbying of
Tivoli pursue satisfactory conclusions.
2.4. Assist Tivoli with prioritisation of new developments and
maintenance releases.
2.5. Share information amongst disparate regional User Groups, providing
cross fertilisation of; ideas, best practices, processes, strategies,
issues and solutions.
2.6. Exchange knowledge with Tivoli and customer base to maximise return
on investment and improve mean time to value.
2.7. Active participation in the Tivoli Board of Advisors, bringing
consolidated issues and ideas to/from that separate but equally focussed
forum.
Note: the complete charter in word format is attached.
Requirements Process
Item 2.3 in the Charter states that your GTUG council representative will
act as a focal point for customer issues, and through lobbying of Tivoli
pursue satisfactory conclusions. To this end, the members have compiled a
list of broad issues and request your feedback. Your GTUG representative
will also accept new issues. Requests submitted by April 19th will be
reviewed at the May 1st GTUG Council meeting. The GTUG Council meets
monthly and will select items that are of benefit to a majority of the
customers. A champion for the change will be selected and Tivoli will
provide a resource to discuss the issue and propose solutions. The
council will review and track progress on the issues and report back to
the local users groups. Monthly newsletters will be available from the
GTUG Council and will be distributed to the users group community by your
local representative. In the Americas, users will find this newsletter on
the ephibian web site.
Requirements - High Level Issues as of April 2002.
Rank each issue with 1-5 with 1 being low impact to you and 5 being
important and provide the results to your local GTUG representative.
Support & Service
- Continuity between support levels. - Start Date: April 3, 2002
- Faster time to open APARS from PMR's
- Stability of existing code
- Upgrade procedures
- Product support web site enhancements
- Product requirements and documentation
- Customer Support Account Representatives
Tivoli Management agent (client)
- Size of light client code
- Ghosting
- Deployment Issues
- Auto discovery
- Auto recognition
Development
- Standards
- ITIL
- CIM
- WMI
- Java
- Endpoint upgrades and required reboots
- Java runtime engine product version requirements. We need 3 different
versions on a machine
- Gui When is it going to take advantage of the new processes and
products(presentation service)
Change management
- Easier change management
- Easier upgrades
- Better documented upgrade path
- Efficient back out path
- Better integration with existing products
Security
- Role based and not ACL
- More continuity across products
- Less administration effort
Product Value
- ROI
- Actual business value
- Report
- Metrics
- Best of Breed Management Products
- More Robust Products
Submitting New Requirements
These are suggested questions you need to answer when submitting
requirements.
What is the need? Why do you need it? What products and/or platforms?
What is the impact if this is not resolved? Technical and Business contact
Information.
ISSUE #1 - Continuity Between Support Levels - Why does Tivoli lose our
Traces?
Start Date: April 3rd, 2002
Last Update: April 3rd, 2002
GTUG Champion: The honourable member from South Central (Dallas, USA)
Users Group
Tivoli Contact: TBD (Erma Moffat will provide a contact)
Status: Open
At the April 2002 meeting, the group agreed that we would pursue the issue
of
Continuity between support levels. The issue includes:
- How product logs are collected and what happens to them when a problem
moves from level 1 to
level 2 and beyond?
- Why does Tivoli come back to the customer and ask for information we
believe we provided earlier?
- Can the logs and supporting documents follow the problem throughout its
life cycle?
- Can there be a consistent method for providing these logs to Tivoli
though the web interface or some other mechanism
accounting for various types and sizes of logs?
- Can the customer see and refer to logs and traces provided earlier?
More Information
Tivoli User Group Website: <
http://www.tivoli.com/support/getting/usergroups/>
Ephibian Tivoli Users Group Website: <
http://www.techgroups.tivoli.ephibian.com/>
Sincerely,
Karen Nickelson, Hewitt Associates
David Boggess, Principal Financial
Toronto Canada
<<GTUGCcharter.doc>> <<GTUG.ppt>>
(See attached file: GTUGCcharter.doc)(See attached file: GTUG.ppt)(See
attached file: GTUG Minutes 4.3.02...doc)
#### GTUGCcharter.doc has been removed from this note on April 19 2002 by
Leslie Clark
#### GTUG.ppt has been removed from this note on April 19 2002 by Leslie
Clark
#### GTUG Minutes 4.3.02...doc has been removed from this note on April 19
2002 by Leslie Clark
|
