YES - IT WORKS BUT!! 2

Transcription

1 1

2 YES - IT WORKS BUT!! 2

3 DOES IT FIT? FOR YOUR NEEDS? FOR YOUR END-USER? IN YOUR ENVIRONMENT?. 3

4 WORKPLACE STRATEGY WORKSHOP Hewlett-Packard (Switzerland) TS Infrastructure Consulting HP Confidential

5 WORKPLACE STRATEGY WORKSHOP (WSW) Agenda Why? What? Next step? 5

6 WHY? 6

7 INITIAL SITUATION Your workplaces are based on any kind of Client HW Client Hardware usually has a lifecycle of 3-5 years every 3-5 years there is a change Business users needs have changed and/or increased Available technology has changed as well The customer s question is: Are we just replacing boxes or do we adopt our client infrastructure to increase business value and reduce costs? 7

8 AND BECAUSE IT TAKES TIME... Month End of HW Lifecycle ± WSW Projekt Proposal HW Evaluation and Proposal Design / Concept Engineering / Implementation Workplace-Project Testing & Pilot Project- & Quality-Management Rollout 8... probably more than you thought!

9 WHAT? 9

10 ANSWERS TO YOUR RENEWAL QUESTIONS? What are our requirements? Licensing Where does our IT stand? What are the market trends? Client virtualization? Windows 7? etc. Where shall we go? Hardware Lifecycle 3 4 years Workplace Strategy Workshop 10

11 THE FOUR VIEWS AND ITS STAKEHOLDERS Business view Why do I want a new client infrastructure? Sponsor Functional view What features should the client provide? User Technical view How will the client be built? Architect Implementation view With what will the client be built? 11 Deployer

12 WSW OVERVIEW Month End of HW Lifecycle ± WSW Projekt Proposal HW Evaluation and Proposal Design / Workplace-Project Concept Engineering / Implementation Testing & Pilot Project- & Quality-Management Rollout What will we do in that Workplace Strategy Workshop? Current Infrastructure Requirements Principles Architectural Blueprint Together with you we answer client specific questions and propose the future client infrastructure based on the requirements and principles This results are summarized in a so-called architectural blueprint which is a high level design document 12

13 CURRENT INFRASTRUCTURE Current Infrastructure Requirements Principles Architectural Blueprint Questionnaire around the following topics Client Infrastructure: Number of devices, device variety, OS and Patch Levels, Installations process, Network Infrastructure, etc. Users: number of users, geographical distribution, user types, user profiles, users way of working, etc. Applications: Current portfolio, packaging, assignment and deployment, etc. Security: Standards and Policies, Access rights, Remote Access, etc. Processes: Order process for Hard- and Software, Patch- and Release- Mgmt, Inventory, Software-Licensing, etc. Interviews If required or necessary, HP interviews your IT staff responsible for infrastructural topics 13

14 REQUIREMENTS AND PRINCIPLES Current Infrastructure Requirements Principles Architectural Blueprint The HP Global Method for IT Strategy & Architecture (ITSA) is the proven HP methodology for gathering requirements and defining principles In workshops the new solution starts growing when discussing the requirements and creating principles with different stakeholders This will ensure the new solution meets the business needs and follows the IT strategy ITSA has a strong focus on effectiveness: doing the right things 14

15 ARCHITECTURAL BLUEPRINT Current Infrastructure Requirements Principles Architectural Blueprint Summary of the WSW containing the Month foundation for the project Rough content Introduction with goals, structure, etc. Current situation statement Requirements, assumptions and principles for the future solution Variants of the future solution including HPs recommendation Outlook and possible migration scenarios Detailed scope is subject of customer agreement End of HW Lifecycle ± WSW Projekt Proposal HW Evaluation and Proposal Design / Workplace-Project Concept Engineering / Implementation Testing & Pilot Project- & Quality-Management Rollout Example Table of Content 1. Management summary 2. Introdution 2.1. Why the project? 2.2. Input from IT Strategy 2.3. Goals of prestudy 2.4. Setup of the prestudy 3. Current situation 3.1. Client OS / HW 3.2. Client Base Apps 3.3. Client Business Apps 3.4. Software Distribution 3.5. Messaging / directories 3.6. Infrastructure Services 4. Working assumptions / principles 5. Future situation 5.1. Client OS / HW VDI Overview Possible Issues / Risks Contingency Plan Recommendation HP 5.2. Client OS 5.3. Client Base Apps 5.4. Client Business Apps 5.5. Software Distribution 5.6. Messaging / directories 5.7. Infrastructure Services 6. Roadmap 6.1. Migration tasks 6.2. Migration roadmaps and scenarios Scenario Scenario Recommendations 15

16 WSW NEXT STEP Introduction Meeting Explanation of details, principles and added value of the WSW Discuss your expectations with regard to content and scope Workplace Strategy Workshop Approx. 1-2 month duration 2 days onsite workshop Architectural Blueprint including short presentation Additional requirements will gladly be offered upon request 16

17 PLEASE CONTACT US FOR YOUR WSW IC Lead Solution Consultant Sales Manager EPG Technical Solution Professional

18 Thank you!