1. 1 State of Georgia (GTA) Desktop Inventory Workshop March 16, 2009 © 2009 IBM Corporation IBM

2. 2 Agenda  Inventory Overview  Inventory Capture Approach  Introductions  Inventory Stakeholders: GTA, Agencies, IBM, Dell  End User Equipment  Data Elements Collected  Site Escort  Data Reconciliation  Asset Agency Lead  GTA Focal  Inventory Locations & Schedule  Interim Change Management  Asset Systems Flow Chart  Next Steps

3. 3 Inventory Overview  Desktop inventory is planned to start April 1 st  The scope of the inventory project includes physical asset attribute data collection  Technicians will physically visit each desktop machine at the agency locations and inventory the hardware’s attribute information  Capture accurate physical asset information (Serial Number, Make and Model) for all in scope desktop assets  Apply IBM asset tags to each desktop device (assuming an IBM asset tag is not already on the machines)  The inventory provides a Wall-to-wall baseline file of all of the asset equipment Lee

4. 4 Inventory Capture Approach Perform Inventory Planning By:  Confirming sites for physical inventories  Confirming any pilot sites  Ensuring inventory communications distributed to end users  Security and parking access (if applicable)  Site walkthrough (if applicable) Lee

5. 5 Introductions  State of Georgia, Dell, IBM Meeting Attendees  Take a few minutes to have introductions with attendees in the meeting  Analysts in the meeting room and on the phone  Name  Agency Representing  Role Lee

6. 6 Inventory Stakeholders  State of Georgia  Dell  IBM Lee

7. 7 End User Equipment Inventory Assets:  Desktop PC units  Laptop PC units  Tablet PC units  Standalone Servers not in Data Centers – physical scan only  Thin Client systems – physical scan only  Network Printers – physical scan only  Local Printers – physical scan only  Projectors – physical scan only  Scanners – physical scan only  Monitors – physical scan only Thekkekara Assets Not Inventoried:  Specialized Equipment (Development Equipment, Test Equipment which sometimes could be in a cubicle)  Other PC Peripherals (i.e. Mice, Keyboards, etc.)

8. 8 Data Elements Collected Hardware Level information Manufacturer Model Name Type Number Serial Number Status (ie. Production, Storage) Standard/Non-Standard Designation Dell Service Tag Number Legacy Agent Asset Number, if any IBM Asset Tag Number (Including any leading zeros) Ownership (Agency Name) Thekkekara Contact Level Information User Last Name User First Name User ID Location Location Code (official State of Georgia site codes) Agency / Sub-Agency Code Building Address City State County Floor Office/Cubicle Number Physical Address of Equipment Custodian User ID

9. 9 Site Escort  Need ability to allow wall-to-wall technicians to enter agency facilities wherever in-scope EUC equipment resides  Physical Key  Keycard  Key Codes  Other security access methods for typically restricted areas with in-scope EUC equipment  Alleviate any liability concerns Thekkekara

10. 10 Data Reconciliation Post Site Inventory Reconciliation Steps  Complete Location Inventory  Compare Wall-to-Wall Inventory Records with Contract Baseline Records  Develop Wall-to-Wall Inventory Comparison Reports 1.Contract Baseline Inventory Matches (No Discrepancies) 2.Contract Baseline Inventory Matches with Discrepancies 3.New Finds  Resolve Asset Discrepancies in Report 2  Obtain Inventory Sign-Off Thekkekara

11. 11 Asset Agency Lead  Review and Verify Site List Accuracy  Review and Verify Site Contact List & respective contact information  If Site Contact List unavailable, provide appropriate Site Contact and/or alternate contact  Ensure Site Contacts are available during scheduled day of Wall 2 Wall event  Verify Overall agency/site asset counts  Obtain internal Agency Management (GAIT Lead) approval Thekkekara

12. 12 GTA Focal  Create Agency level forum to ensure communication, alignment & consistency  Review Agency Focal deliverables to ensure there are not additional or additional Agency level concerns/gaps that have not been messaged to IBM/Dell teams regarding W2W activities  Review and analyze Asset Baseline collected from W2W and approve for all Agencies prior to data import date for Maximo (May 15) Thekkekara

13. 13 Inventory Locations & Schedule  April 1. End User Computing Wall-to-Wall begins  May 15. Initial Data Import into Maximo  June 1. Begin Future Mode of Operations utilizing DDM/Maximo for Asset management Lee, Thekkekara

14. 14 Interim Change Management  Prior to Maximo Launch (June 1), Asset Data will be maintained manually at an Agency level via existing Business As Usual (BAU) method  Maintain existing records to clearly identify assets impacted by any IMACD activity from 4/1 through 6/1 to ensure proper data reconciliation takes place  Agency’s are expected to follow the correct interim change procedure Thekkekara

15. 15 Asset Systems Flow Chart Lee Maximo DDM BRAVO GSMRT Software Scan Data DeployedAuthorized Wall-to-Wall Inventory Data Scan Tool Integration Hardware Inventory Data Reporting Interface Hardware Data Flow Change Management

16. 16 Next Steps Thekkekara  Commence with Joint Planning (IBM & Dell)  Determine / Establish Actual Inventory Dates  Identify candidate sites for pilot prior to April 1  Determine Final Approver of Agency Inventory Baselines  Verify & Approve Site List for Each Agency and Make Appropriate Corrections  Identify Site Contacts and identify backup Site Contacts and respective availability for W2W  Identify ALL Security Requirements (physical/logical) that may be Required to Physically Tag Assets  Update Asset Lists/Databases to accurately reflect the following and readily available at the time of W2W:  EUC deployed or “live” systems  EUC systems in storage/inventory  EUC systems (specialized equipment/lab equipment) that are out of scope  EUC systems that fulfill the role of a server (i.e. serve applications to multiple users, utilize server OSes)

17. 17 Questions / Discussion