The 7 days at “x” Revised May

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

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

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

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

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

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

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

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

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

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

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

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

3: Add Novell Novell NT Novell downlevel, needed to apply maintenance

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

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

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

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

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

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