Text Size:   A+ A- A   •   Text Only
Find     
Site Image
Session 8: Requirements Analysis - Remedy Configuration Management and Asset Management
 

Dates:
Monday August 20, 2007 to Wednesday August 22, 2007
Time:
8:30 am – 4:30
Location:
Fort Rock Room 118
3414 Cherry Ave NE Suite 150
Salem, OR 97301
 

Facilitator:
Column Technology Remedy SME – Rob Tucker
Melody Riley, Pilot Project Lead
Participants:
IT Asset Coordinators
IT Procurement Staff
Pilot Remedy Application Administrator
Pilot Project Manager
Service Desk Managers
Service Desk Lead Worker
Special Guests:
 
None
 
Pre-session work required

Assignment:
  1. Review the Atrium CMDB Common Data model diagram classes and attributes
  2. Review current configuration item (Asset) life cycles in your organization
  3. Review current support, warranty and software license contracts in your organization
  4. Complete “Agency location/organization” assignment sheet.
 
Due Date:
 
Start of Session
 
Agenda

 
Topic
Presenter
Length
Outcome
1
Welcome
  • Session Overview & Agenda
  • Review Pre-work
 
M. Riley
08/20/07
8:30am to 9:30 am
 
2
Configuration Management
 
Review of the Remedy Atrium CMBD Common Data Model (CDM)
 
Walk through the different classes of configuration items in the Remedy Atrium CMDB 2.0 Common Data Model (CDM)      
 
This will form the basis for what classes will be populated in the CDM and the relationships that are possible between the different CI’s
 
Column Tech.
08/20/07
9:45am to Noon
  • Define Business Objectives and Scope
 
3
Configuration Item Class and Attribute Identification
 
Identification of CDM classes that will be tracked in the CMDB
 
Identification of the attributes for the identified CDM classes
Column Tech.
08/20/07
1:30pm to 3:30pm
 
4
Data Sources
 
Identify and define content, dynamics, and state of Data Sources
Column Tech
08/20/07
3:45pm to 4:30pm
  • Define Data Sources (Discoverable, Not Discoverable and  Manual)
 
5
Data Sources (Continued)
 
Review Data Sources
 
Column Tech.
08/21/07
8:30am to 10:30am
  • Initial Source to Configuration Item Class mapping
  • Initial Source to Configuration Item attribute mapping
6
Configuration Item Life cycle
 
The Lifecycle (Status) of a Configuration Item.  How does a CI get registered into the CMDB
For example:
  • Ordered
  • Received
  • Assembled
  • Deployed
  • In Repair
  • Down
  • End of Life
 
Column Tech
08/21/07
10:45am to Noon
 
7
Configuration Item Associated Contracts and Schedules
 
Identify Support, Warranty, software contracts associated with CI’s
 
Identify Maintenance and Audit Schedules associated with CI’s
Column Tech
08/21/07
1:30pm to 3:30pm
 
8
Review of Foundation Data Structures
 
Column Tech.
08/21/07
3:45pm to 4:30pm
 
9
Defining Companies/Agency’s or Bureaus
  • Working with “Companies (Agency’s or Bureaus)
  • Company Types
  • Roles & Security Access
  • Workflow
  • Navigation Tiers
  • Overall access within or between Companies (Agency’s or Bureaus).
Column Tech.
08/22/07
8:30am to 9:30am
Identification of:
  • Company Names (Agency’s or Bureaus)
  • Identify Multi-Tenancy workflow considerations
 
10
 
Defining Organizations & Physical Locations
  • Working with “Company (Agency or Bureau)” fields
  • Reporting needs, automated assignment routing and service level management mapping requirements.
Column Tech.
08/22/07
9:45am to
10:45am
Identification of:
  • Organizational structure
  • Physical Location attributes
11
Defining Support Groups
  • Working with “Support groups” for assignment
  • Support Staff associated with Support Group
  • Virtual support groups
 
 
08/22/07
11am to Noon
Identification of:
  • Agencies’ IT Support Structure and high level procedures or functions
12
Defining Service & Product Categorizations
  • Working with “Categorizations”
  • Tier 1, 2 & 3
Identification of:
  • Service & Product Tiers
 
08/22/07
1:30pm to 3:30pm
 
13
Defining People
  • customers (internal or external) and support staff (internal or external)
  • “Company (Agency or Bureaus)”  and Location attributes for contact profile
  • Permission Groups and Functional Roles
  • Individual access to data
  • People associated to CIs and Support Groups.
  • Approval mappings
 
 
08/22/07
3:45pm to
4:45pm
Identification of:
  • IT Staff roles within Agency or Bureau support organization
 

Session 8 Workproduct