The document outlines six strategies for crisis avoidance in IT management, focusing on decision support metrics, architecture ownership, training, problem management, application development optimization, and business-technology integration. It emphasizes the importance of documentation, collaborative design, and implementing best practices to enhance system performance and resource allocation. The services provided aim to identify existing problems and prevent future issues within an organization by ensuring all technologists operate consistently and effectively.

1. Crisis Avoidance:
Six Things You Can Do
Bill Alderson
bill@apalytics.com

3. Bill Alderson
Executive Analyst & Founder
 Lockheed Missiles & Space Company
QA Technologist & Communications Engineer
 Network General (Sniffer Analyzer)
Mgr. Secure Systems & Volume Sales
 Founded Pine Mountain Group, Inc. (PMG)
Licensed Sniffer Training to Network General
Created Certified NetAnalyst ® Program
 Provided Critical Problem Resolution Services and Training to 75% of Fortune 100
 Trained 50,000 technologists in 22 countries
 Certified 3,000 Certified Network Forensic Professionals
 PMG sold to NetQoS (2005) NetQoS Technology Officer
 NetQoS sold to CA Technologies (2009)
 Founded Apalytics Corporation (2010)

4. Six Things You Can Do

6. Decision Support Metrics
Delivers a collaborative, cross-silo system management
capability capable of validating individual application capacity
and identifying budget and resource allocation priorities.
• Requirements analysis to suit the metrics system to the
application owners and their customer’s performance.
• Application data flow & dependencies
• Test / Instrumentation points
• Scalable while accommodating compartmentalization
• Expertly configure monitoring to validate dependencies and
performance for each major application and user group:
• Mission critical applications
• Exchange
• Internet
• Repurpose unused Monitoring Tools to expert productive use
• Recoup Monitoring Tool ROI
• Enables Operations to deliver the most needed IT Services
• Assesses quality of “user” performance experience
• Integrates with Problem Management & Root Cause Diagnosis
• Integrates with Architecture Ownership Documentation

8. Architecture Ownership Components
1.) Rapid Network Rendering (RNR)
2.) Client Brand Training & Certification
Ensures system documentation creation and maintenance program is an
enduring capability that will survive personnel, budget, and management
turnover
Routers/Switches, communications links, network segments, data centers,
and application flow will be entered into a central CMDB database
Documentation spans multiple security zones and globally scalable
• Reverse-engineer and document current systems
• Service enabling topology-mapping software
• Create processes to accurately document the existing IT infrastructure
• Up-to-date schematic diagrams empower all technologists
• Customer “owns” their Technical Architecture despite changing contracts

9. Architecture Ownership Components
1.) Rapid Network Rendering (RNR)
2.) Customer Brand Training & Certification
Training indoctrinates every technologist in architectural specific
implementations of technology to ensure all participants maintain systems
consistently across all technical silos and locations.
Provides expert training in deep packet inspection and definitive problem
identification curriculum based on end user’s real-world performance
problems.
Provides expert training on existing underutilized monitoring tools operation
to identify bottlenecks, diagnose problems and capacity plan.
Leverages the Rapid Network Rendering (RNR) and Critical Problem
Resolution processes.
A branded “Client Branded Certification” promotes professional
development, provides a common technical language and basis for
advancement.

11. Problem/Change Management
Critical Problem Resolution
• Problem Statement
• Reverse-Engineer
System Documentation
• Micro- and Macro-
Analysis
• Instrumentation
• Hypothesis
• Findings
• Recommendations
• Test
• Implementation
• Validation
• Reports
Emergency action service: features
• Rapid-response remote assistance and
• Immediate resource for onsite analysis.
1. Apply the instrumentation necessary to deliver a
definitive root-cause diagnosis, accompanied by
incontrovertible forensic evidence.
2. Present recommendations.
3. Assist your staff in the implementation of corrective
measures.
4. Perform additional instrumentation to validate the
success of your newly configured environment; and
5. Provide a summation of the activities undertaken
during the engagement.

13. Application Development Optimization
Components
vPlatforms
Databases
Web
SAN
Cloud
Middleware
Load Balancers
Firewalls
Applying the CPR Methodology to the Application
Development process….
• Early and iterative performance analysis
• Embedded performance Analyst
• IDs issues with Flow, Hardware, Network
Components, db Query and Code
Latency Analysis
 Process
 Serialization
 Transmission
 Switch / Router Decision
 Queue
Highlights:
 Identify sub-system
Dependencies
 Macro- and micro-
level
instrumentation
 Root Cause
Analysis
 Iterative
Optimization
 Assist with iterative
code rewrites

15. Business / Technology Integration
Instills into the operational culture a “Collaborative Design” mentality that will take
into account the needs of disparate IT organizations and business Silos, enabling
the development of an IT Master Plan that will enable client technologists to deliver
results in alignment with their goals.
Collaborative Design:
• System design executed with the interests if diverse operating groups in mind
• Detailed, cross-silo schematic documentation is available to all budgetary /
operating groups
• Standardize documentation granularity (level of detail) across business units
• Change Control standardization
Master Plan Development:
• Prerequisite for Collaborative Design
• Facilitates management of cross-vendor solutions
• Provides continuity-of care for your end-user community
• Understanding the current environment allows Orgs to plan for the future

16. Cross-Silo Collaboration Model
Organizational Silos
• Desktop
• Network
• Security
• Platform
• Application
• Cloud & Mobile
• Other locations

18. Technical Systemization©
 Architecture Ownership
 Documentation
 Training & Certification
 Decision Support Metrics
 Identify Performance Bottlenecks
 Pinpoint Resource Allocation
 Business / Technology Integration
 Cross Silo Master Plan
 Cross Silo Optimization
 Problem / Change Management
 Root Cause Analysis
 Change Drives Optimization
 Application Development Optimization
 Early Dev Performance Analysis.
Things You Can Do

19. Apalytics is dedicated to Crisis Avoidance
through the integration of best practices
in our clients’ organizations.
Technical Services assist
clients with existing
problems.
Assessment Services
identify systemization risks
and recommend mitigation
strategies.
Cornerstone Services
obviate problems through
the expert integration of Best
Practices.

20. Bill Alderson
bill@apalytics.com
Thank you for your participation in this month’s WebEx:
Crisis Avoidance: Six Thing You Can Do.