1 / 20

The 7 days at “x”

The 7 days at “x”. Revised May 12 2002. The 7 “Days” at “X” A Real POC. This is a real story with the name(s) changed to protect the innocent Each step required only one or two technical people The plan changed during the work - this is real life and you must allow for it

dagan
Download Presentation

The 7 days at “x”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The 7 days at “x” Revised May 12 2002

  2. The 7 “Days” at “X”A Real POC • This is a real story with the name(s) changed to protect the innocent • Each step required only one or two technical people • The plan changed during the work - this is real life and you must allow for it • Planning for Problems Prevents Problems

  3. Mission at “X” • Business Objectives: • Reduce MTTR and Operations Staff • Focal Point Console with Ability to Zoom to Specific Systems • Cross platform Scheduling • Improve Competitive Position Thru New Services • Online Services Availability Impacting Competitive Position • Detect Network Faults Early and in the context of the Business/Enterprise • SAP Rollout Quality Impacting Business • Manage SAP as a Whole • Failed Audit • Need single Security Image Across MVS, Unix, NT

  4. Mission at “X” • Business Objectives: • Focal Point Console with Ability to Zoom to Specific Systems – eliminate consolitis, improve MTTR • Detect Network Faults Early and in the context of the Enterprise – improve MTTR • Manage SAP as a Whole – focus on mission critical application as a process • Single Security Image Across MVS, Unix, NT – reduced admin, enhanced security • Cross platform Scheduling – reduced admin/errors

  5. Technical Deliverables • Unicenter TNG 2d and 3d Workstations • Enterprise Management Event Focal point console • SSO Server on Unix • Unicenter 1.1 and 1.5 on Unix • Unicenter 2.x on NT • Unicenter v1 on Novell • Polycenter on VMS

  6. 5 4 1 Automation Point MVS Polycenter DEC UNIX 2 NT 2D HP UNIX AIX NT SQL SUN Solaris 3 NT Agent OS/2 6 NT SAP UNIX SAP/R3 Novell Novell Novell

  7. Hardware to manage • 4 Unix servers • 4 NT servers • 3 Novell LANs • VMS systems • MVS SAP R2 • SAP R3 on Unix

  8. Before We Start • Verify kits received • Verify correct media • Scan (again) for key customer issues • Check STARTRAK for fixes and test fixes • Verify licenses are available • Wrong Unix release, no OS on main server, wrong media shipped, needed patches

  9. Milestones and Process • Stepwise Implementation with Deliverables • Daily CA Internal Show and Tell • Nightly Meetings to Adjust Staffing/Plan

  10. The 7 Step POC at “X” • Unix Focal Point Event Console • NT Control + Event • Novell LAN Integrator + Event • Polycenter VMS Integration • Cross Platform Scheduling with Mainframe • SAP/R3 • Demo

  11. Discover Customer Network • Connect to TCP/IP Network • Needed Community Name for Router • DNS Address • Determine Subnets to Discover • DNS synch issues, bad WINS, no one knew community name, lab could not see network originally, IP address changed during project

  12. DEC UNIX AIX HP UNIX SUN Solaris 1: UNIX Focal Point Event Console Focal Point Console • Unix sysadmin would not give root acess

  13. 2: Add NT; Use NT As Console NT 2D AIX SQL NT NT • Wins and /etc/hosts did not match

  14. 3: Add Novell NT Novell Novell • Novell downlevel, needed to apply maintenance

  15. 4: Add Polycenter DEC VAX NT • Trouble finding client contact with VAX access

  16. 5: Add MVS OPS/MVS + Cross Platform Scheduling NT Automation Point MVS • MVS change control process added delay

  17. 6: SAP/R3 NT SAP/R3 UNIX • SAP guru needed resold on solution

  18. 7: Demo • 1: Unix Focal Point Event Console • 2: NT Control + Event • 3: Novell LAN Integrator + Event • 4: Polycenter Integrator • 5: Cross Platform Scheduling with Mainframe • 6: SAP/R3 • 7: Demo

  19. Automation Point MVS Polycenter DEC UNIX NT 2D HP UNIX AIX NT SQL SUN Solaris NT Agent OS/2 NT SAP UNIX SAP/R3 Novell Novell Novell 5 4 1 2 3 6

  20. The 7 “Days” at “X”A Real POC • Did steps as islands to extent possible • Each step required only one or two technical people • The plan changed during the project - this is real life and you must allow for it • Build on success • System integration testing – do not forget and do not underestimate problem potential • Client had changed the environment as we went so day 1 and 2 stuff stopped working - twice

More Related