Measure

Measure Performance¶

Stage 4 of the PRIME Framework¶

"What gets measured gets improved. The Measure stage proves automation value and identifies opportunities for optimisation."

graph TD
    A[📊 Baseline] --> B[🔍 Monitor]
    B --> C[📊 Track KPIs]
    C --> D[💰 Calculate ROI]
    D --> E[📈 Report]
    E -->|Continuous| B

    style A fill:#FFB347
    style B fill:#FFBD57
    style C fill:#FFC767
    style D fill:#FFD177
    style E fill:#FFDB87

Prime Terminology Used: Prime Overwatch™ monitoring, Prime Automation™ metrics

🎯 Objective¶

Quantify the impact of automation through systematic metrics collection, ROI tracking, and performance analysis to demonstrate value and guide future investment.

📊 What Happens During Measure¶

1. Baseline Metrics (Before Automation)¶

Before deploying automation, we capture baseline performance:

Time Metrics¶

Quality Metrics¶

Business Impact¶

Baseline Documentation:

Task: VLAN Provisioning (Pre-Automation)
─────────────────────────────────────────
Frequency:           40 changes/month
Duration:            15 minutes/change
Annual Volume:       480 changes
Annual Time:         120 hours
Error Rate:          12% (58 failures/year)
Rework Time:         43 hours/year
Total Time Cost:     163 hours/year
Labour Cost (fully loaded): £8,150/year @ £50/hour

2. Instrumentation (During Implementation)¶

We build metrics collection into every automation:

Execution Metrics¶

import time
import logging

def measure_execution(func):
    """Decorator to track execution time."""
    def wrapper(*args, **kwargs):
        start_time = time.time()
        logger.info(f"Starting {func.__name__}")

        try:
            result = func(*args, **kwargs)
            duration = time.time() - start_time
            logger.info(f"✓ {func.__name__} completed in {duration:.2f}s")

            # Log to metrics database/file
            record_metric(
                task=func.__name__,
                duration=duration,
                status="success",
                timestamp=datetime.now()
            )

            return result

        except Exception as e:
            duration = time.time() - start_time
            logger.error(f"✗ {func.__name__} failed after {duration:.2f}s: {e}")

            record_metric(
                task=func.__name__,
                duration=duration,
                status="failure",
                error=str(e),
                timestamp=datetime.now()
            )
            raise

    return wrapper

@measure_execution
def provision_vlan(devices, vlan_id, vlan_name):
    """VLAN provisioning with automatic metrics tracking."""
    results = []
    for device in devices:
        result = process_device(device, vlan_id, vlan_name)
        results.append(result)
    return results

Outcome Tracking¶

def generate_execution_report(results):
    """Create detailed metrics report."""
    metrics = {
        "timestamp": datetime.now().isoformat(),
        "total_devices": len(results),
        "successful": sum(1 for r in results if r['status'] == 'success'),
        "failed": sum(1 for r in results if r['status'] == 'failure'),
        "total_duration": sum(r['duration'] for r in results),
        "average_duration": statistics.mean(r['duration'] for r in results),
        "error_types": Counter(r.get('error_type') for r in results if r['status'] == 'failure')
    }

    # Append to metrics log (CSV for easy analysis)
    append_to_metrics_log("vlan_provisioning_metrics.csv", metrics)

    return metrics

3. Performance Monitoring (Post-Deployment)¶

After automation goes live, we track:

Daily Task Execution¶

Metrics Captured:

• Execution count
• Success/failure rate
• Duration (total and per-device)
• Error types and frequencies
• User who triggered (if applicable)

Sample Metrics Log:

Date,Task,Devices,Successful,Failed,Duration_Sec,Triggered_By
2024-01-15,provision_vlan,12,12,0,47.3,jsmith
2024-01-16,provision_vlan,5,5,0,18.9,automated
2024-01-17,provision_vlan,8,7,1,41.2,mjones
2024-01-18,provision_vlan,15,14,1,63.1,jsmith

Weekly Summary Reports¶

Generated automatically:

VLAN Provisioning - Week of 2024-01-15
════════════════════════════════════════
Executions:       18 times
Total Devices:    156 devices
Success Rate:     97.4% (152/156)
Avg Duration:     38.2 seconds
Time Saved:       37.2 hours (vs 40 hours manual)
Est Labor Cost:   £660 saved vs £2,000 manual
Failures:         4 devices (3× auth timeout, 1× config rollback)

4. ROI Calculation¶

We prove value with concrete numbers.

Time Savings¶

Manual Process (Baseline):

40 changes/month × 15 min/change = 600 min/month = 10 hours/month
Annual: 10 hours/month × 12 = 120 hours/year

Automated Process (Measured):

40 executions/month × 0.6 min/execution = 24 min/month = 0.4 hours/month
Annual: 0.4 hours/month × 12 = 4.8 hours/year

Time Saved: 120 - 4.8 = 115.2 hours/year (96% reduction)

Error Reduction¶

Manual Error Rate: 12% (58 failures/year, 43 hours rework) Automated Error Rate: ~2-3% with auto-rollback (12 failures/year); rework typically ≤10% of baseline rework time (4.3 hours/year)

Rework Hours Saved: 43 - 4.3 = 38.7 hours/year (conservative estimate accounting for investigation and retries)

Total Financial Impact¶

Time Savings:             115.2 hours × £50/hour = £5,760
Error Reduction:          38.7 hours × £50/hour  = £1,935
─────────────────────────────────────────────────────
Total Annual Savings:                             £7,695

Implementation Cost:      £6,000 (one-time)
Ongoing Cost (annual):    £1,200 (maintenance, monitoring, platform)

Net Annual Benefit (Year 1):    £7,695 - £6,000 - £1,200 = £495
Net Annual Benefit (Steady-state): £7,695 - £1,200 = £6,495

Year-1 ROI:              (£495) ÷ (£6,000 + £1,200) × 100 = 6.9%
Steady-state ROI:        (£6,495) ÷ (£1,200) × 100 = 541%

Payback Period:          9.3 months (assuming £659 monthly net benefit)
                        (With £1,200/yr maintenance included)

Sensitivity Analysis¶

ROI varies based on key inputs. Here's how different scenarios affect returns:

Key Insight: ROI is most sensitive to labour rates and change volume. Higher wage environments and busier teams see faster payback.

5. Continuous Improvement Analysis¶

Metrics reveal optimisation opportunities:

Performance Bottlenecks¶

Analysis of Execution Times:

Device Connection:     22 seconds (58% of total time)
Config Application:    8 seconds (21%)
Validation:           7 seconds (18%)
Reporting:            1 second (3%)

Improvement Opportunity: Connection pooling could reduce device connection time by 60%

Projected Impact: 22s × 0.6 = 13.2s saved per execution
40 executions/month × 13.2s = 528 seconds = 8.8 minutes/month

Error Pattern Analysis¶

Failure Analysis (90 days):

Auth Timeouts:        8 occurrences (67%)
Config Rejected:      3 occurrences (25%)
Device Unreachable:   1 occurrence (8%)

Root Cause Investigation:
Auth timeouts concentrated on IOS-XE devices during peak CPU times (backup window).

Remediation:
Add pre-flight CPU check, defer if CPU >80%.

Expected Impact:
Reduce auth timeout failures by 75% (8 → 2 annually).

6. Stakeholder Reporting¶

We create reports tailored to different audiences:

Executive Summary (Leadership)¶

Format: One-page dashboard

AUTOMATION PERFORMANCE - Q1 2024
================================

VLAN Provisioning Automation
────────────────────────────
✓ 480 changes executed (100% of volume automated)
✓ 97.5% success rate (467 successful, 13 failed)
✓ 115 hours saved vs manual process
✓ £7,695 annual cost avoidance
✓ ROI: 6.9% (Year-1), 100%+ steady-state (depending on ongoing cost)

Network Audit Automation
────────────────────────
✓ 12 audits completed (monthly)
✓ 600 devices per audit
✓ 30 hours saved vs manual
✓ £18,000 cost avoidance
✓ 23 security findings identified

Portfolio Summary
─────────────────
Total Time Saved:      248 hours (6.2 weeks)
Total Cost Avoidance:  £37,500
Total Investment:      £24,000
Portfolio ROI:         56% (Year 1)

Technical Report (Engineering)¶

Format: Detailed metrics with trends

• Execution time trends (weekly)
• Error rate by device platform
• Success rate by time of day
• Performance vs. SLA targets
• Failure root cause analysis
• optimisation recommendations

Operations Report (NetOps Team)¶

Format: Actionable insights

• Tasks automated this period
• Time saved per team member
• Errors requiring manual intervention
• Upcoming automation releases
• Feedback/enhancement requests

📊 Deliverable: Performance Dashboard & Reports¶

At the end of the Measure stage, you receive:

1. Metrics Collection System¶

• Python logging integrated into automations
• CSV/database for metrics storage
• Automated report generation scripts

2. Monthly Performance Reports¶

• Execution statistics
• Success/failure trends
• Time savings quantification
• ROI calculation
• Improvement recommendations

3. Executive Dashboards¶

• One-page KPI summary
• Portfolio-level ROI
• Strategic recommendations for next automations

4. Continuous Improvement Plan¶

• Identified bottlenecks
• optimisation roadmap
• Enhancement backlog

💡 Why Measure Matters¶

Proves Business Value¶

Without measurement:

• ❌ "Automation saves time" (vague claim)
• ❌ Leadership questions investment
• ❌ Future projects harder to justify

With measurement:

• ✅ "VLAN automation saved 115 hours and £7,910 in Q1" (concrete proof)
• ✅ Leadership sees ROI
• ✅ Easier to secure budget for next automation

Drives Improvement¶

Metrics reveal:

• Which automations deliver most value (prioritise similar projects)
• Where optimisation is worthwhile (focus effort)
• What's working well (replicate success patterns)

🚀 What Happens Next¶

After establishing measurement, proceed to Stage 5: Empower to transfer knowledge and build team capability.

📋 Measure Checklist¶

Ensure measurement success:

• Baseline metrics captured before automation
• Metrics collection built into automation code
• Automated report generation configured
• ROI calculation documented and validated
• Stakeholder reports tailored to audience
• Monthly review cadence established
• Continuous improvement process defined
• Success criteria for next automations defined

💼 Engagement Options¶

Measurement as Part of Full PRIME Engagement¶

Included as Stage 4 when you engage for the complete framework. Typically ongoing over 3-6 months post-deployment.

Standalone Measurement Service¶

For Organisations with existing automation needing ROI proof:

Fixed Fee: £2,000 - £3,500

Includes:

• Baseline metrics reconstruction
• Instrumentation added to existing scripts
• 3 months of performance tracking
• Executive summary report
• ROI calculation

🎓 Learn More¶

• PRIME Framework Overview — See how all five stages work together
• Previous Stage: Implement — Building the automation we're now measuring
• Next Stage: Empower — Knowledge transfer and capability building
• Request Discovery Call — Discuss your automation needs

Mission: To empower network engineers through the PRIME Framework—delivering automation with measurable ROI, production-grade quality, and sustainable team capability built on the PRIME Philosophy of transparency, measurability, ownership, safety, and empowerment.

← Previous: Implement | Back to PRIME Framework | Next: Empower →