Empower

Empower Your Team¶

Stage 5 of the PRIME Framework¶

"The best automation is the automation your team can maintain and extend. The Empower stage ensures long-term success through knowledge transfer and capability building."

graph LR
    A[🏛️ Training] --> B[📚 Documentation]
    B --> C[🔧 Practice]
    C --> D[🎓 Prime Capability]
    D -->|Independent| E[🚀 Scale]

    style A fill:#FF6B9D
    style B fill:#FF7BAD
    style C fill:#FF8BBD
    style D fill:#FF9BCD
    style E fill:#FFABDD

Prime Terminology Used: Prime Capability achievement, Prime Workflows extension, Prime Agents maintenance

🎯 Objective¶

Transfer knowledge and build internal capability so your team can maintain, troubleshoot, and extend automation without ongoing external dependency.

🚀 What Happens During Empower¶

1. Knowledge Transfer Sessions¶

Comprehensive handoff of developed automation:

Session 1: Architecture Overview (2 hours)¶

Topics Covered:

• Project Goals Review: What problem does this solve?
• Workflow Design: How does data flow through the automation?
• Component Architecture: What libraries/tools are used and why?
• File Structure: Where to find code, configs, templates, outputs
• Integration Points: External systems (DNS, IPAM, ticketing)

Deliverable: Architecture diagram with narrative documentation

Session 2: Code Walkthrough (2-3 hours)¶

Topics Covered:

• Main execution flow: Step-by-step through the code
• Key functions: Purpose and parameters for each
• Configuration files: What settings can be changed
• Templates: How to modify Jinja2 configs for new scenarios
• Error handling: What each exception handles and why

Format: Live screen share with Q&A, recorded for reference

Example Walkthrough:

```python
# START: Main execution
def main():
    """
    WHY THIS EXISTS:
    Entry point for VLAN provisioning automation.

    WHAT IT DOES:
    1. Loads device inventory from CSV
    2. Connects to each device
    3. Applies VLAN config with validation
    4. Generates Excel report

    HOW TO MODIFY:
    - Change inventory source: Edit load_device_inventory()
    - Add validation steps: Modify verify_vlan_creation()
    - Change report format: Edit generate_report()
    """
    logger.info("=== VLAN Provisioning Started ===")

    # STEP 1: Load devices
    # WHY: CSV allows non-Python staff to manage inventory
    # HOW TO CHANGE: Swap to Netbox API in load_device_inventory()
    devices = load_device_inventory("inventory.csv")
```

Session 3: Operations & Troubleshooting (2 hours)¶

Topics Covered:

• How to run the automation: Command-line arguments, config files
• How to read the logs: What INFO/WARNING/ERROR mean
• Common failure scenarios: Device unreachable, auth failure, config rejected
• How to troubleshoot: Enabling debug mode, reading stack traces
• How to rollback: Manual rollback procedures if auto-rollback fails

Hands-On Exercise:

Team members run automation in lab environment with deliberately introduced failures:

• Device with wrong IP (unreachable)
• Device with wrong credentials (auth failure)
• Device with conflicting VLAN ID (config validation failure)

Practice reading logs and identifying root cause.

Session 4: Modification & Extension (2-3 hours)¶

Topics Covered:

• Making common changes: Add new device types, modify templates
• Adding new features: Example walkthrough of small enhancement
• Testing changes: How to test in lab before production
• Git workflow: Branching, committing, merging (if using source control)
• When to ask for help: Complexity boundaries

Hands-On Exercise:

Modify automation for new use case:

• Example: "Add capability to remove VLANs (not just create)"
• Walk through: Update template, add validation, test in lab

2. Documentation Package¶

Comprehensive written materials for long-term reference:

User Guide¶

Target Audience: Network engineers who will run the automation

Contents:

```markdown
# VLAN Provisioning Automation - User Guide

## Quick Start
1. Copy `inventory_template.csv` and add your devices
2. Run: `python provision_vlan.py --vlan 150 --name "Guest_WiFi"`
3. Check `outputs/` folder for Excel report

## Detailed Usage
### Command-Line Arguments

- `--vlan` : VLAN ID to create (required)
- `--name` : VLAN name (required)
- `--inventory` : Path to device CSV (default: inventory.csv)
- `--dry-run` : Validate without applying changes

### Example Commands
```bash
# Normal execution
python provision_vlan.py --vlan 150 --name "Guest_WiFi"

# Dry-run (validation only)
python provision_vlan.py --vlan 150 --name "Guest_WiFi" --dry-run

# Custom inventory file
python provision_vlan.py --vlan 150 --name "Guest_WiFi" --inventory devices_dc1.csv
```

Understanding the Output¶

Log Files¶

• vlan_provisioning.log : Detailed execution log
  • INFO: Normal operations
  • WARNING: Devices skipped (with reason)
  • ERROR: Failures requiring attention

Excel Reports¶

Generated in outputs/vlan_provisioning_TIMESTAMP.xlsx

Columns:

• Device: Switch hostname
• IP: Management IP
• Status: success/failed
• Duration: Seconds to process
• Error: Reason if failed

Technical Reference¶

Target Audience: Engineers who will modify/extend the automation

Contents:

• Code architecture: Component diagram w/ descriptions
• Function reference: Purpose, parameters, return values for each function
• Configuration files: What each setting controls
• Template syntax: How to modify Jinja2 templates
• Adding new device types: Step-by-step guide
• Testing procedures: Lab setup, test cases
• Troubleshooting guide: Common issues & solutions

Runbook¶

Target Audience: Operations team for incident response

Contents:

```markdown
# VLAN Provisioning Automation - Runbook

## Emergency Procedures

### Automation Failed Mid-Execution
**Symptoms:** Some devices configured, others not
**Resolution:**
1. Check log file for last successful device
2. Update inventory.csv to include only failed devices
3. Re-run automation with updated inventory

### All Devices Failing with Auth Error
**Symptoms:** "Authentication failed" for all devices
**Resolution:**
1. Verify credentials in `.env` file unchanged
2. Test manual SSH to one device
3. Check account lockout in authentication system
4. If credential rotation, update `.env` file

### VLAN Created but Validation Failed
**Symptoms:** Config applied but post-flight check failed
**Resolution:**
1. Manual verification: ssh to device, `show vlan brief`
2. If VLAN exists: False alarm, check parsing logic
3. If VLAN missing: Check `show running-config` for rejected config
```

3. Self-Service Resources¶

We provide pathways for continued learning:

Curated Learning Path:

1. Start Here: Nautomation Prime Beginner Tutorials
2. Next Steps: Intermediate Topics
3. Advanced: Expert-Level Patterns
4. Deep Dives: Real-World Scripts

External Resources:

• Recommended books (Python for network engineers)
• Online courses (Udemy, Pluralsight, CBT Nuggets)
• Community forums (Network to Code Slack, Reddit r/networking)
• Vendor documentation (Netmiko, Nornir, NAPALM)

4. Ongoing Support Transition¶

A structured handoff from supported to self-sufficient, with every commitment defined up front.

Included: 8 Weeks of Transition Support¶

Starts after the final knowledge transfer session.

• Email questions about the delivered automation, answered within one UK business day
• Four fortnightly 30-minute office-hours calls
• Troubleshooting assistance for defects in the delivered automation
• Guidance and review as your team makes its first changes

Optional: Extended Guided Transition (Months 3-6)¶

Quoted separately, for teams that want a longer runway:

• Monthly office-hours calls
• Code review of your team's changes
• Architecture guidance for major extensions

After That: Self-Sufficient¶

• Your team operates and extends the automation independently
• An optional retainer is available for complex enhancements

What Counts as Additional Work¶

Transition support is advisory. We answer questions, fix defects in what we delivered, and review your team's changes. The following are quoted separately and only go ahead with your written approval:

• New features or workflows
• Support for new device types or platforms
• Changes that alter the agreed scope
• Additional training cohorts
• Support beyond the included period

Support runs in UK business hours. It is not an on-call or incident-response service; production incidents go through your own incident process.

5. Community of Practice¶

We help establish internal momentum:

Automation Guild (Optional)¶

For organisations with multiple network engineers:

Structure:

• Monthly 1-hour meeting
• Demo recent automations
• Share lessons learned
• Collaborate on new use cases
• Review code together

Benefits:

• Cross-pollination of ideas
• Peer learning
• Consistent code standards
• Shared troubleshooting knowledge

6. Success Metrics for Empowerment¶

We measure knowledge transfer effectiveness:

Capability Milestones¶

Knowledge Retention Assessment¶

At 30, 60, 90 days post-handoff:

Quick Survey:

1. How confident are you running this automation? (1-5)
2. How confident troubleshooting issues? (1-5)
3. How confident making modifications? (1-5)
4. What additional training would be helpful?

Goal: Average 4+ on all questions by day 90

📊 Deliverable: Empowered Team¶

At the end of the Empower stage, your team has:

1. Knowledge Transfer Complete¶

• ✅ Architecture understanding
• ✅ Code walkthrough completed
• ✅ Operational procedures trained
• ✅ Modification/extension demonstrated

2. Comprehensive Documentation¶

• ✅ User guide (how to run)
• ✅ Technical reference (how it works)
• ✅ Runbook (how to troubleshoot)
• ✅ Modification guide (how to extend)

3. Self-Sufficiency¶

• ✅ Team operating automation independently
• ✅ Troubleshooting issues without escalation
• ✅ Making modifications confidently
• ✅ Building new automations using established patterns

💡 Why Empower Matters¶

Sustainability¶

Without empowerment:

• ❌ Vendor lock-in (can't change code without consultant)
• ❌ Fragility (breaks when engineer leaves)
• ❌ Stagnation (automation doesn't evolve with needs)

With empowerment:

• ✅ Team autonomy (independent capability)
• ✅ Resilience (knowledge distributed across team)
• ✅ Evolution (automation grows with the organisation)

ROI Multiplication¶

Empowered teams:

• Build additional automations using patterns learned (5x ROI)
• optimise existing automations continuously (ongoing value)
• Respond faster to changes (no waiting for external help)
• Transfer knowledge to new team members (sustainable)

🚀 Beyond PRIME: What's Next¶

After completing all five stages:

Automation Capability Model¶

Capability is not the same as effort. This ladder describes what your automation can safely do, and what has to be true at each level for it to stay safe.

Post-PRIME, you're at Level 2–3.

Levels 4 and 5 are a governance problem before they are a technology problem. See Governed AI for Network Operations for what has to be true before an agent touches your estate.

What Happens After Empower¶

PRIME ends when your team owns the automation. The automation does not end there — it runs for years, accumulates dependencies, and eventually should be switched off.

That is a separate discipline from delivery, and skipping it is how organisations end up with a portfolio nobody can inventory: scheduled jobs whose purpose is unclear, services whose owner has left, credentials belonging to scripts that stopped being useful two years ago.

The Automation Service Lifecycle covers what to put in place: three named owners per service rather than "the automation team", decision gates before you build and after you ship, a minimum service record, and a retirement path.

If you adopt one thing from it, adopt the three owners. It takes an afternoon and it is what makes team ownership survive a resignation.

Scaling Automation¶

Next Automations:

• Refer back to Pinpoint roadmap (#2, #3 priorities)
• Team can now implement independently or with advisory support
• Reuse patterns from first automation

Building Automation Portfolio:

• Consistent code standards (established)
• Shared libraries (extract common functions)
• Git repository organisation
• CI/CD for testing (advanced)

📋 Empower Checklist¶

Ensure knowledge transfer success:

• All knowledge transfer sessions completed
• Documentation reviewed and understood
• Team has run automation in lab independently
• Team has troubleshot simulated failure scenarios
• Team has made successful modification
• Support transition plan agreed
• Learning resources provided
• 30-day check-in scheduled
• Success metrics baseline captured

💼 Engagement Options¶

Empower as Part of Full PRIME Engagement¶

Included as Stage 5 when you engage for the complete framework. Typically 2-4 weeks of knowledge transfer sessions, followed by 8 weeks of transition support.

Standalone Empowerment Service¶

For organisations with existing automation needing knowledge transfer:

Fixed Fee: £4,000 - £7,500 (depending on complexity)

Includes:

• 4 remote knowledge transfer sessions of up to 3 hours each, for up to 8 participants
• Complete documentation package
• 8 weeks of transition support (email within one UK business day, plus four fortnightly 30-minute office-hours calls)
• 90-day success check-in

Anything outside this is additional work, quoted separately.

🎓 Learn More¶

• PRIME Framework Overview — See how all five stages work together
• Previous Stage: Measure — Proving the value we've delivered
• Beginner Tutorials — Start building Python skills
• Services — Explore engagement options
• Request Discovery Call — Discuss your automation needs

🎉 Congratulations¶

By completing the PRIME Framework—Pinpoint, Re-engineer, Implement, Measure, Empower—your organisation has:

✅ Identified high-value automation opportunities (Pinpoint)
✅ Designed optimised, scalable workflows (Re-engineer)
✅ Built production-ready, maintainable automation (Implement)
✅ Proven ROI and demonstrated value (Measure)
✅ Built internal capability for sustained success (Empower)

You're now equipped to scale automation across your network operations.

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: Measure | Back to PRIME Framework | View All Services →