Compare commits
1 Commits
sprint/iss
...
sprint/iss
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
afff1750dc |
67
specs/fleet-operator-incentives.md
Normal file
67
specs/fleet-operator-incentives.md
Normal file
@@ -0,0 +1,67 @@
|
||||
# Fleet Operator Incentives & Partner Program
|
||||
|
||||
## Overview
|
||||
|
||||
This document defines the incentive structure, certification pathway, and operational framework for Fleet Operators within the Timmy ecosystem. It implements Fleet Epic IV - Human Capital & Incentives.
|
||||
|
||||
## Objectives
|
||||
|
||||
- Attract and retain high-quality fleet operators
|
||||
- Ensure fleet uptime >99.5%
|
||||
- Maintain operator churn <10% annually
|
||||
- Build sustainable partner channel driving >30% of leads
|
||||
|
||||
## Operator Tiers & Compensation
|
||||
|
||||
### Tier 1: Certified Operator
|
||||
- Requirements: Complete 100-hour training, pass certification exam, maintain 99.5% uptime for 30 days
|
||||
- Base rate: $X/hour + performance bonuses
|
||||
- Benefits: Health stipend, equipment allowance, priority support
|
||||
|
||||
### Tier 2: Senior Operator
|
||||
- Requirements: 6+ months as Certified, 99.8% uptime, mentor 2+ new operators
|
||||
- Base rate: Tier 1 + 25% premium
|
||||
- Benefits: Profit sharing, leadership opportunities, advanced training
|
||||
|
||||
### Tier 3: Master Operator
|
||||
- Requirements: 2+ years service, 99.9% uptime, develop 3+ successful operators
|
||||
- Base rate: Tier 2 + 35% premium
|
||||
- Benefits: Equity participation, strategic input, conference attendance
|
||||
|
||||
## Performance Bonuses
|
||||
|
||||
- Uptime Bonus: +5% for >99.8% monthly uptime
|
||||
- Efficiency Bonus: +3% for completing >110% of target tasks
|
||||
- Quality Bonus: +2% for zero critical incidents monthly
|
||||
- Referral Bonus: $500 for each successful operator referral
|
||||
|
||||
## Partner Program
|
||||
|
||||
### Partner Tiers
|
||||
|
||||
#### Bronze Partner
|
||||
- Referral target: 1-3 operators/quarter
|
||||
- Benefits: 5% rev-share on referred operator revenue
|
||||
|
||||
#### Silver Partner
|
||||
- Referral target: 4-10 operators/quarter
|
||||
- Benefits: 8% rev-share + co-marketing support
|
||||
|
||||
#### Gold Partner
|
||||
- Referral target: 11+ operators/quarter
|
||||
- Benefits: 12% rev-share + strategic partnership agreement
|
||||
|
||||
## Certification Pathway
|
||||
|
||||
1. **Application** → Submit through operator-application.md template
|
||||
2. **Screening** → Background check, technical assessment
|
||||
3. **Training** → Complete 100-hour Fleet Ops curriculum
|
||||
4. **Certification Exam** → Written + practical components
|
||||
5. **Onboarding** → Shadowing, gradual ramp-up
|
||||
6. **Production** → Full operator status after 30-day probation
|
||||
|
||||
## Success Metrics (6-month targets)
|
||||
- 3-5 active certified operators
|
||||
- Operator churn <10% annually
|
||||
- Fleet uptime >99.5%
|
||||
- Partner channel >30% of leads
|
||||
101
specs/fleet-ops-runbook.md
Normal file
101
specs/fleet-ops-runbook.md
Normal file
@@ -0,0 +1,101 @@
|
||||
# Fleet Operations Runbook
|
||||
|
||||
## Purpose
|
||||
|
||||
Standard operating procedures for Fleet Operators to ensure consistent, high-quality service delivery.
|
||||
|
||||
## Daily Operations
|
||||
|
||||
### 1. Morning Startup (06:00-07:00)
|
||||
- [ ] Check system dashboards for overnight alerts
|
||||
- [ ] Review priority task queue
|
||||
- [ ] Ensure all equipment is online and calibrated
|
||||
- [ ] Attend 15-minute standup with operations lead
|
||||
|
||||
### 2. Core Operations (07:00-16:00)
|
||||
- [ ] Process assigned task batches
|
||||
- [ ] Log all actions with timestamps
|
||||
- [ ] Report anomalies immediately
|
||||
- [ ] Maintain >99.5% uptime SLAs
|
||||
|
||||
### 3. Evening Shutdown (16:00-17:00)
|
||||
- [ ] Complete all in-flight tasks
|
||||
- [ ] Generate daily summary report
|
||||
- [ ] Document any issues or process improvements
|
||||
- [ ] Handoff to night shift (if applicable)
|
||||
|
||||
## Incident Response
|
||||
|
||||
### Severity 1 (System Down)
|
||||
- Notify ops lead immediately
|
||||
- Follow recovery playbook
|
||||
- Document root cause
|
||||
- Escalate if unresolved in 15 minutes
|
||||
|
||||
### Severity 2 (Degraded Performance)
|
||||
- Log incident in tracking system
|
||||
- Begin troubleshooting
|
||||
- Update status every 30 minutes
|
||||
- Resolve within 4 hours
|
||||
|
||||
### Severity 3 (Minor Issue)
|
||||
- Document and schedule for next maintenance window
|
||||
- No immediate escalation required
|
||||
|
||||
## Escalation Matrix
|
||||
|
||||
| Issue Type | First Escalation | Second Escalation | SLA |
|
||||
|------------|-----------------|------------------|-----|
|
||||
| Technical | Senior Operator | Operations Lead | 30 min |
|
||||
| Process | Team Lead | Fleet Manager | 2 hr |
|
||||
| Customer | Support Lead | Fleet Manager | 15 min |
|
||||
|
||||
## Communication Channels
|
||||
|
||||
- **Daily Standup**: Zoom 06:45-07:00
|
||||
- **Incidents**: #fleet-ops-alerts (Slack)
|
||||
- **Questions**: #fleet-ops-general (Slack)
|
||||
- **Reports**: Submit via partner-report.md template daily
|
||||
|
||||
## Quality Standards
|
||||
|
||||
- Task completion accuracy: >99%
|
||||
- Response time to alerts: <5 minutes
|
||||
- Documentation completeness: 100%
|
||||
- Safety incident rate: 0
|
||||
|
||||
## Training & Certification
|
||||
|
||||
See certification pathway in fleet-operator-incentives.md. Operators must maintain certification through quarterly requalification.
|
||||
|
||||
## Schedule & Availability
|
||||
|
||||
- Standard shift: 6 hours/day, 5 days/week
|
||||
- On-call rotation: 1 week per month
|
||||
- PTO request: 2 weeks minimum notice
|
||||
- Emergency leave: Notify ops lead immediately
|
||||
|
||||
## Equipment & Resources
|
||||
|
||||
- Primary workstation: Maintained by IT
|
||||
- Backup systems: Test monthly
|
||||
- Software tools: Latest approved versions only
|
||||
- Documentation: Always accessible via internal wiki
|
||||
|
||||
## Metrics & Reporting
|
||||
|
||||
Daily metrics submitted via partner-report.md:
|
||||
- Tasks completed
|
||||
- Uptime percentage
|
||||
- Incidents logged
|
||||
- Quality scores
|
||||
- Process improvement suggestions
|
||||
|
||||
Weekly review with Fleet Manager every Monday 10:00-10:30.
|
||||
|
||||
## Appendix
|
||||
|
||||
- A: System Architecture Overview
|
||||
- B: Troubleshooting Playbooks
|
||||
- C: Contact Directory
|
||||
- D: Compliance Requirements
|
||||
65
specs/templates/operator-application.md
Normal file
65
specs/templates/operator-application.md
Normal file
@@ -0,0 +1,65 @@
|
||||
---
|
||||
# Fleet Operator Application
|
||||
application_date: YYYY-MM-DD
|
||||
candidate_name:
|
||||
---
|
||||
|
||||
## Personal Information
|
||||
|
||||
- Full Name:
|
||||
- Email:
|
||||
- Phone:
|
||||
- Location (City/State/Country):
|
||||
- Time Zone:
|
||||
|
||||
## Professional Background
|
||||
|
||||
### Relevant Experience
|
||||
- Years in operations/technical roles:
|
||||
- Fleet management experience:
|
||||
- Previous certifications:
|
||||
- Equipment familiarity:
|
||||
|
||||
### Technical Skills
|
||||
- [ ] System monitoring
|
||||
- [ ] Incident response
|
||||
- [ ] Documentation
|
||||
- [ ] Team collaboration
|
||||
- [ ] Other (specify):
|
||||
|
||||
## Availability
|
||||
|
||||
- Start date available:
|
||||
- Weekly hours sought:
|
||||
- On-call willingness: [ ] Yes [ ] No
|
||||
- Remote work preference: [ ] Fully remote [ ] Hybrid [ ] On-site
|
||||
|
||||
## Compensation Expectations
|
||||
|
||||
- Desired hourly rate:
|
||||
- Minimum acceptable rate:
|
||||
|
||||
## Why Timmy?
|
||||
|
||||
*(Describe your interest in joining the Timmy Fleet)*
|
||||
|
||||
## Additional Information
|
||||
|
||||
- References (2-3):
|
||||
- Portfolio/Projects:
|
||||
- GitHub/LinkedIn:
|
||||
|
||||
## Certification Path
|
||||
|
||||
- Have you reviewed the Fleet Operator Incentives document? [ ] Yes [ ] No
|
||||
- Are you willing to complete the 100-hour training program? [ ] Yes [ ] No
|
||||
|
||||
---
|
||||
|
||||
**Application Process:**
|
||||
1. Submit this form
|
||||
2. Technical screening (phone)
|
||||
3. Background check
|
||||
4. Training enrollment
|
||||
5. Certification exam
|
||||
6. Probation period (30 days)
|
||||
69
specs/templates/partner-report.md
Normal file
69
specs/templates/partner-report.md
Normal file
@@ -0,0 +1,69 @@
|
||||
---
|
||||
# Fleet Partner Report
|
||||
reporting_period:
|
||||
partner_name:
|
||||
partner_tier:
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
- Period:
|
||||
- Total referred operators this period:
|
||||
- Active operators from referrals:
|
||||
- Revenue generated from referrals:
|
||||
- Status: [ ] On Track [ ] At Risk [ ] Exceeding Target
|
||||
|
||||
## Referral Activity
|
||||
|
||||
| Referral Name | Application Date | Status | Revenue Impact |
|
||||
|---------------|-----------------|--------|----------------|
|
||||
| | | | |
|
||||
| | | | |
|
||||
|
||||
**Total referrals:**
|
||||
**Converted to active operators:**
|
||||
**Conversion rate:**
|
||||
|
||||
## Financial Summary
|
||||
|
||||
- Referral fees earned this period:
|
||||
- Cumulative referral fees:
|
||||
- Revenue share percentage:
|
||||
- Projected next period revenue:
|
||||
|
||||
## Partner Performance Metrics
|
||||
|
||||
| Metric | Target | Actual | Variance |
|
||||
|--------|--------|--------|----------|
|
||||
| Referrals/quarter | | | |
|
||||
| Conversion rate | >50% | | |
|
||||
| Revenue contribution | >30% leads | | |
|
||||
| Partner NPS | >50 | | |
|
||||
|
||||
## Challenges & Blockers
|
||||
|
||||
*(Describe any issues affecting partner performance)*
|
||||
|
||||
## Support Needed
|
||||
|
||||
*(List any resources or support needed from Timmy to improve performance)*
|
||||
|
||||
## Goals for Next Period
|
||||
|
||||
1.
|
||||
2.
|
||||
3.
|
||||
|
||||
## Additional Notes
|
||||
|
||||
---
|
||||
|
||||
**Report Submission Instructions:**
|
||||
- Submit weekly via email to fleet-partners@timmy.io
|
||||
- Copy your Partner Success Manager
|
||||
- Attach any supporting documentation
|
||||
|
||||
**Review Process:**
|
||||
- Weekly review: Partner Success Team
|
||||
- Monthly review: Fleet Leadership
|
||||
- Quarterly review: Executive Team
|
||||
@@ -5,7 +5,7 @@ import sys
|
||||
import os
|
||||
import json
|
||||
|
||||
sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", "..", "src"))
|
||||
sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", "src"))
|
||||
|
||||
from timmy.claim_annotator import ClaimAnnotator, AnnotatedResponse
|
||||
|
||||
|
||||
Reference in New Issue
Block a user