Compare commits
1 Commits
sprint/iss
...
sprint/iss
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
11d94d9dad |
@@ -1,137 +1,130 @@
|
||||
# Fleet Operator Incentives & Partner Program
|
||||
|
||||
## 1. Operator Role Definition
|
||||
> Implements Fleet Epic IV: Human Capital & Incentives (Issue #987)
|
||||
> Closes #1003
|
||||
|
||||
Fleet Operators are independent contractors responsible for managing a fleet of Timmy vehicles in their designated geographic zone. They serve as the local operations hub, ensuring vehicle availability, maintenance, and customer satisfaction.
|
||||
## Overview
|
||||
|
||||
**Key Responsibilities:**
|
||||
- Vehicle inventory management (15-25 vehicles per operator)
|
||||
- Daily inspection and preventive maintenance
|
||||
- Customer support escalation
|
||||
- Partner recruitment and onboarding
|
||||
- Quality control and safety compliance
|
||||
- Reporting and analytics
|
||||
This specification defines the incentive structures, certification pathways, and partner program mechanics for operating and maintaining Timmy Fleet nodes. The goal is to build a distributed network of reliable, skilled operators who run fleet infrastructure with >99.5% uptime while maintaining low churn (<10% annually) and grow partner-sourced leads to >30% of total.
|
||||
|
||||
**Required Qualifications:**
|
||||
- Valid driver's license + clean record
|
||||
- Basic mechanical aptitude
|
||||
- Organizational skills
|
||||
- 20+ hours/week availability
|
||||
- Home base with secure parking
|
||||
## Incentive Tiers
|
||||
|
||||
## 2. Compensation Model
|
||||
### Tier 1: Certified Operator (Entry)
|
||||
- **Eligibility**: Complete Operator Application, pass basic screening, attend training
|
||||
- **Compensation**:
|
||||
- Base stipend: $500/month per node
|
||||
- Uptime bonus: +$200/month for >99.5% fleet uptime
|
||||
- Response bonus: +$100/month for <15min average incident response
|
||||
- Churn rebate: -$250/month for early termination (first 6 months)
|
||||
- **Expectations**:
|
||||
- Monitor node health 24/7 via Timmy dashboard
|
||||
- Respond to alerts within 15 minutes
|
||||
- Perform weekly maintenance and monthly updates
|
||||
- Submit monthly ops report
|
||||
- **Benefits**: Access to operator community, training resources, priority support
|
||||
|
||||
### Base Pay
|
||||
- **$150/month** per managed vehicle (guaranteed minimum)
|
||||
- Paid bi-weekly via ACH
|
||||
### Tier 2: Senior Operator (Experienced)
|
||||
- **Eligibility**: 6+ months as Tier 1, >99.5% uptime average, zero major incidents
|
||||
- **Compensation**:
|
||||
- Base stipend: $800/month per node
|
||||
- Uptime bonus: +$400/month for >99.8% uptime
|
||||
- Mentorship stipend: +$150/month per junior operator mentored
|
||||
- Performance bonus: Quarterly bonus up to $500 based on metrics
|
||||
- **Expectations**:
|
||||
- Mentor 1-2 junior operators
|
||||
- Lead incident reviews
|
||||
- Contribute to runbook improvements
|
||||
- **Benefits**: Profit-sharing from referral bonuses, early access to new features
|
||||
|
||||
### Performance Bonuses
|
||||
| Metric | Target | Bonus |
|
||||
|--------|--------|-------|
|
||||
| Fleet Uptime | >99.5% | +$200/mo |
|
||||
| Customer Satisfaction (CSAT) | >4.5/5 | +$100/mo |
|
||||
| Safety Incidents | 0 (zero) | +$100/mo |
|
||||
| Partner Referrals | 3+ new partners | +$150/mo |
|
||||
### Tier 3: Fleet Lead (Expert)
|
||||
- **Eligibility**: 12+ months, >99.9% uptime, successfully mentored 3+ operators
|
||||
- **Compensation**:
|
||||
- Base stipend: $1,200/month per node
|
||||
- Uptime bonus: +$600/month for >99.9% uptime
|
||||
- Team lead bonus: +$300/month for team performance
|
||||
- Revenue share: 2% of partner program revenue from region
|
||||
- **Expectations**:
|
||||
- Own regional cluster of nodes
|
||||
- Coordinate multi-node deployments
|
||||
- Interface with Timmy core team on roadmap
|
||||
- **Benefits**: Equity eligibility, governance rights, speaking opportunities
|
||||
|
||||
**Earnings Potential:** $150 + bonuses = **$400-700/month per vehicle**
|
||||
## Partner Program
|
||||
|
||||
### Tier Certification
|
||||
- **Bronze** (0-6 mo): Base + uptime bonus
|
||||
- **Silver** (6-12 mo): Full bonuses + priority support
|
||||
- **Gold** (12+ mo): +10% base increase + profit sharing
|
||||
### Partner Tiers
|
||||
|
||||
## 3. Partner Program
|
||||
#### Bronze Partner (Referral)
|
||||
- Commission: 10% of first-year operator revenue from referred leads
|
||||
- Requirements:
|
||||
- Sign partner agreement
|
||||
- Refer 3+ qualified candidates annually
|
||||
- Maintain active engagement in partner channel
|
||||
|
||||
### Referral Commission Structure
|
||||
- **20% commission** on all earnings generated by referred partners
|
||||
- Paid quarterly, based on referred partner's net revenue
|
||||
- Multi-tier: 1st level (20%), 2nd level (5%)
|
||||
#### Silver Partner (Channel)
|
||||
- Commission: 15% of first-year operator revenue + 5% ongoing
|
||||
- Requirements:
|
||||
- Onboard and train at least 5 operators
|
||||
- Provide monthly partner report
|
||||
- Maintain >80% operator retention rate
|
||||
|
||||
#### Gold Partner (Strategic)
|
||||
- Commission: 20% first-year + 7% ongoing + co-marketing funds
|
||||
- Requirements:
|
||||
- Operate fleet of 10+ nodes
|
||||
- Contribute to product roadmap
|
||||
- Host local meetups/training sessions
|
||||
|
||||
### Partner Benefits
|
||||
- Access to exclusive vehicle allocations
|
||||
- Marketing co-op fund (up to $500/mo)
|
||||
- Priority vehicle upgrades
|
||||
- Training & certification discounts
|
||||
- Access to exclusive operator training materials
|
||||
- Early beta program participation
|
||||
- Co-marketing and case study opportunities
|
||||
- Dedicated partner portal and revenue dashboard
|
||||
|
||||
### Qualification
|
||||
- Minimum 3 months as certified operator
|
||||
- CSAT consistently >4.2
|
||||
- Clean safety record
|
||||
- Referral sales target: 2+ partners/quarter
|
||||
## Certification Pathway
|
||||
|
||||
## 4. Quality Standards
|
||||
### Stage 1: Application & Screening
|
||||
1. Submit Operator Application (see `templates/operator-application.md`)
|
||||
2. Technical interview (30 min)
|
||||
3. Infrastructure audit (existing hardware/network)
|
||||
4. Background check (optional but preferred)
|
||||
**Timeline**: 3-5 business days
|
||||
|
||||
### Vehicle Readiness
|
||||
- All vehicles must pass daily safety checklist
|
||||
- Cleanliness rating: 4/5 minimum
|
||||
- Fuel level >50% at all times
|
||||
- Tire pressure & battery health monitored weekly
|
||||
### Stage 2: Training & Onboarding
|
||||
1. Complete Fleet Ops 101 module (2 hours self-paced)
|
||||
2. Shadow a senior operator (2 weeks)
|
||||
3. Deploy test node (sandbox environment)
|
||||
4. Pass certification exam (90%+ score)
|
||||
**Timeline**: 2-3 weeks
|
||||
|
||||
### Service Level Agreements
|
||||
- Vehicle availability: 99.5% uptime
|
||||
- Customer support response: <15 minutes
|
||||
- Maintenance turnaround: <24 hours
|
||||
- Incident resolution: <4 hours
|
||||
### Stage 3: Active Operation
|
||||
- Deploy first production node
|
||||
- Maintain >99.5% uptime for first 30 days
|
||||
- Submit initial monthly ops report
|
||||
**Timeline**: 30 days probation
|
||||
|
||||
### Compliance
|
||||
- All local regulations followed
|
||||
- Insurance documentation current
|
||||
- Regular audits (quarterly)
|
||||
### Certification Renewal
|
||||
- Quarterly review of metrics
|
||||
- Annual recertification exam
|
||||
- Continuous training requirement (4 hours/month)
|
||||
|
||||
## 5. Onboarding & Certification (4-Phase)
|
||||
## Success Metrics (6-month targets)
|
||||
|
||||
### Phase 1: Application & Screening (Week 1)
|
||||
- Submit operator application form
|
||||
- Background check & driving record review
|
||||
- Interview with operations team
|
||||
- Equipment & space inspection
|
||||
| Metric | Target | Measurement |
|
||||
|--------|--------|-------------|
|
||||
| Active certified operators | 3-5 | Dashboard |
|
||||
| Operator churn | <10% annually | HR records |
|
||||
| Fleet uptime | >99.5% | Monitoring systems |
|
||||
| Partner channel leads | >30% of total | CRM data |
|
||||
|
||||
### Phase 2: Training & Shadowing (Weeks 2-3)
|
||||
- Complete online curriculum (8 modules)
|
||||
- Shadow an experienced operator (3 days)
|
||||
- Vehicle inspection certification
|
||||
- Customer service protocol training
|
||||
## Runbook
|
||||
|
||||
### Phase 3: Supervised Launch (Weeks 4-6)
|
||||
- Manage 5 vehicles under supervision
|
||||
- Daily check-ins with mentor
|
||||
- Gradual increase in responsibilities
|
||||
- Weekly performance reviews
|
||||
See companion document: `specs/fleet-ops-runbook.md` for operational procedures, escalation paths, and incident response protocols.
|
||||
|
||||
### Phase 4: Independent Operations (Week 7+)
|
||||
- Full certification exam
|
||||
- Assigned permanent fleet (15-25 vehicles)
|
||||
- Access to full partner program
|
||||
- Monthly performance bonus eligibility
|
||||
## Templates
|
||||
|
||||
**Certification requires:** 90%+ on exams, 95%+ checklist compliance, no safety incidents.
|
||||
- **Operator Application**: `templates/operator-application.md`
|
||||
- **Partner Report**: `templates/partner-report.md`
|
||||
|
||||
## 6. Exit & Transition Protocol
|
||||
## Revision History
|
||||
|
||||
### Voluntary Exit
|
||||
- 30-day notice required
|
||||
- Vehicle inventory reconciliation
|
||||
- Final compensation paid within 14 days
|
||||
- Exit interview conducted
|
||||
|
||||
### Performance-Based Termination
|
||||
- Written warnings for first 2 offenses
|
||||
- 30-day improvement plan
|
||||
- Immediate termination for safety violations
|
||||
- Equipment return within 7 days
|
||||
|
||||
### Emergency Transition
|
||||
- Company assumes control within 24 hours
|
||||
- Backup operator assigned
|
||||
- Vehicles redistributed to neighboring fleets
|
||||
|
||||
### Knowledge Transfer
|
||||
- All documentation handed over
|
||||
- Key contacts list provided
|
||||
- Outstanding issues documented
|
||||
- Final report submitted
|
||||
|
||||
---
|
||||
|
||||
*Last updated: 2025-01-20*
|
||||
*Owner: Fleet Operations Team*
|
||||
- 2025-05-02: Initial specification (implements #987, closes #1003)
|
||||
|
||||
@@ -1,147 +1,291 @@
|
||||
# Fleet Operations Runbook
|
||||
|
||||
## 1. Daily Checklist
|
||||
> Fleet Operator Incentives & Partner Program — Operational Procedures
|
||||
> Implements #987 | Closes #1003
|
||||
|
||||
### Morning (6:00 AM - 9:00 AM)
|
||||
- [ ] Check vehicle allocation dashboard
|
||||
- [ ] Review overnight alerts (low battery, damage reports)
|
||||
- [ ] Dispatch cleaning crews to high-priority vehicles
|
||||
- [ ] Verify fuel levels on all vehicles
|
||||
- [ ] Coordinate with partners for morning rush
|
||||
## Table of Contents
|
||||
|
||||
### Midday (11:00 AM - 2:00 PM)
|
||||
- [ ] Spot-check 20% of fleet for quality
|
||||
- [ ] Respond to customer support tickets (<15 min SLA)
|
||||
- [ ] Coordinate repositioning for high-demand areas
|
||||
- [ ] Verify compliance with local regulations
|
||||
|
||||
### Evening (6:00 PM - 9:00 PM)
|
||||
- [ ] Nightly vehicle inventory reconciliation
|
||||
- [ ] Schedule maintenance for flagged vehicles
|
||||
- [ ] Review daily performance metrics
|
||||
- [ ] Plan next day's operations
|
||||
|
||||
## 2. Weekly Checklist
|
||||
|
||||
### Monday
|
||||
- [ ] Weekly fleet health report
|
||||
- [ ] Safety incident review (if any)
|
||||
- [ ] Partner onboarding sessions
|
||||
- [ ] Review compensation & bonus eligibility
|
||||
|
||||
### Wednesday
|
||||
- [ ] Mid-week quality audit (10% random sample)
|
||||
- [ ] Partner performance reviews
|
||||
- [ ] Inventory planning for upcoming weekend
|
||||
- [ ] Training session for new operators
|
||||
|
||||
### Friday
|
||||
- [ ] Weekly summary report submission
|
||||
- [ ] Equipment maintenance scheduling
|
||||
- [ ] Customer feedback review
|
||||
- [ ] Weekend readiness assessment
|
||||
|
||||
## 3. Alert Response Procedures
|
||||
|
||||
### High Priority (Respond within 15 minutes)
|
||||
| Alert Type | Action | Escalation |
|
||||
|------------|--------|------------|
|
||||
| Vehicle Accident | 1. Contact customer<br>2. Document damage<br>3. Coordinate tow<br>4. Notify insurance | Fleet Manager |
|
||||
| Safety Incident | 1. Secure scene<br>2. Medical assistance if needed<br>3. Complete incident report<br>4. Notify compliance | Safety Team |
|
||||
| Vehicle Missing | 1. GPS tracking<br>2. Contact last user<br>3. Law enforcement if >2 hrs | Operations Director |
|
||||
|
||||
### Medium Priority (Respond within 1 hour)
|
||||
| Alert Type | Action |
|
||||
|------------|--------|
|
||||
| Low Battery | Schedule charging within 4 hours |
|
||||
| Maintenance Flag | Add to maintenance queue |
|
||||
| Quality Complaint | Contact customer, document, remediate |
|
||||
|
||||
### Low Priority (Respond within 24 hours)
|
||||
| Alert Type | Action |
|
||||
|------------|--------|
|
||||
| Cleaning Request | Schedule for next available slot |
|
||||
| Minor Cosmetic | Log for weekly maintenance |
|
||||
| Inventory Update | Adjust allocation |
|
||||
|
||||
## 4. Common Fixes & Quick Resolutions
|
||||
|
||||
### Vehicle Won't Start
|
||||
1. Check battery level (app dashboard)
|
||||
2. If <20%, request jump start/charge
|
||||
3. If battery healthy, check for error codes
|
||||
4. Dispatch technician if unresolved in 30 min
|
||||
|
||||
### GPS/Location Issues
|
||||
1. Verify vehicle connectivity
|
||||
2. Restart vehicle system (if safe)
|
||||
3. Report persistent issues to tech support
|
||||
|
||||
### Customer Complaints
|
||||
| Issue | Resolution |
|
||||
|-------|------------|
|
||||
| Dirty vehicle | Immediate cleaning + $10 credit |
|
||||
| Low fuel | Fuel up + $5 credit |
|
||||
| Mechanical issue | Swap vehicle + full refund |
|
||||
| Late pickup | Refund + $10 credit |
|
||||
|
||||
### Maintenance Coordination
|
||||
- Preventive: Schedule during off-peak hours (2-5 PM)
|
||||
- Emergency: Immediate dispatch, backup vehicle assignment
|
||||
- Recalls: 48-hour completion SLA
|
||||
|
||||
## 5. Reporting Requirements
|
||||
|
||||
### Daily (by 9:30 PM)
|
||||
- Fleet inventory status
|
||||
- Active incidents (<5 min read)
|
||||
- Next-day forecast
|
||||
|
||||
### Weekly (Monday 10 AM)
|
||||
- Quality metrics report
|
||||
- Partner performance
|
||||
- Uptime statistics
|
||||
- Cost analysis
|
||||
|
||||
### Monthly (5th of month)
|
||||
- Comprehensive operations report
|
||||
- Compensation calculations
|
||||
- Partner commission statements
|
||||
- Safety audit results
|
||||
|
||||
## 6. Emergency Procedures
|
||||
|
||||
### Power/Communication Outage
|
||||
- Activate backup hotspot (provided)
|
||||
- Manual vehicle tracking (paper logs)
|
||||
- Dispatch via radio/cell if possible
|
||||
- 2-hour check-in cadence
|
||||
|
||||
### Natural Disaster
|
||||
- Secure all vehicles in safe location
|
||||
- Suspend operations if hazardous
|
||||
- Notify all customers of suspension
|
||||
- Document all damage for insurance
|
||||
|
||||
### Pandemic/Health Crisis
|
||||
- Contactless vehicle handoff
|
||||
- Enhanced cleaning protocols
|
||||
- PPE provided to all operators
|
||||
- Virtual training & support
|
||||
|
||||
## 7. Tools & Resources
|
||||
|
||||
| Tool | Purpose | Access |
|
||||
|------|---------|--------|
|
||||
| Fleet Dashboard | Real-time vehicle tracking | ops@timmy.io |
|
||||
| Maintenance Portal | Work order management | service@timmy.io |
|
||||
| Customer Support | Ticket resolution | support@timmy.io |
|
||||
| Partner Portal | Commission tracking | partners.timmy.io |
|
||||
| Safety App | Incident reporting | safety.timmy.io |
|
||||
|
||||
**24/7 Hotline:** 1-800-TIMMY-OPS (846-6967)
|
||||
1. [Daily Ops Checklist](#daily-ops-checklist)
|
||||
2. [Weekly Maintenance](#weekly-maintenance)
|
||||
3. [Monthly Responsibilities](#monthly-responsibilities)
|
||||
4. [Incident Response](#incident-response)
|
||||
5. [Escalation Paths](#escalation-paths)
|
||||
6. [Communication Protocols](#communication-protocols)
|
||||
7. [Node Deployment](#node-deployment)
|
||||
8. [Compliance & Reporting](#compliance--reporting)
|
||||
|
||||
---
|
||||
|
||||
*Last updated: 2025-01-20*
|
||||
*Version: 1.0*
|
||||
## Daily Ops Checklist
|
||||
|
||||
### Health Monitoring
|
||||
- [ ] Review Timmy Dashboard for all owned nodes
|
||||
- [ ] Check alert feed (PagerDuty/OpsGenie) for any pending incidents
|
||||
- [ ] Verify node heartbeats (expect >99.5% uptime)
|
||||
- [ ] Confirm backup systems are running (if applicable)
|
||||
|
||||
### Incident Response (if alerts triggered)
|
||||
- See [Incident Response](#incident-response) section
|
||||
- Acknowledge alert within 15 minutes (Tier 1 SLA)
|
||||
- Begin triage within 30 minutes
|
||||
|
||||
### Logs Review
|
||||
- Scan error logs for recurring patterns
|
||||
- Flag any anomalies for weekly review
|
||||
|
||||
### Documentation Updates
|
||||
- Note any operational findings in daily log
|
||||
|
||||
---
|
||||
|
||||
## Weekly Maintenance
|
||||
|
||||
### Scheduled Tasks (Every Monday)
|
||||
1. **System Updates**
|
||||
- Apply security patches (critical only)
|
||||
- Review and schedule non-critical updates for maintenance window
|
||||
|
||||
2. **Performance Review**
|
||||
- Analyze resource utilization trends
|
||||
- Identify capacity constraints
|
||||
- Plan for scaling if needed
|
||||
|
||||
3. **Backup Verification**
|
||||
- Confirm latest backups completed successfully
|
||||
- Test restore from backup (monthly, see below)
|
||||
|
||||
4. **Runbook Updates**
|
||||
- Document any new procedures learned
|
||||
- Suggest runbook improvements to Fleet Lead
|
||||
|
||||
5. **Team Sync**
|
||||
- Attend weekly operator stand-up (30 min)
|
||||
- Share status, blockers, learnings
|
||||
|
||||
---
|
||||
|
||||
## Monthly Responsibilities
|
||||
|
||||
### Month-End Reporting
|
||||
Due by the 5th of each month for prior month:
|
||||
|
||||
1. **Ops Report** (use `templates/partner-report.md` format)
|
||||
- Uptime metrics per node
|
||||
- Incident summary and resolutions
|
||||
- Training completed
|
||||
- Recommendations
|
||||
|
||||
2. **Financial Reconciliation**
|
||||
- Verify incentive payments received
|
||||
- Report discrepancies to Finance
|
||||
|
||||
3. **Compliance Audit**
|
||||
- Confirm certification requirements met
|
||||
- Document any deviations and corrective actions
|
||||
|
||||
### Deep Maintenance
|
||||
- Full system backup and restore test
|
||||
- Security audit review
|
||||
- Hardware inspection (if physical nodes)
|
||||
- Training module completion (minimum 4 hours/month)
|
||||
|
||||
---
|
||||
|
||||
## Incident Response
|
||||
|
||||
### Severity Definitions
|
||||
|
||||
| Severity | Definition | Response Time | Resolution Target |
|
||||
|----------|------------|---------------|-------------------|
|
||||
| P0 | Fleet-wide outage, no nodes operational | 15 minutes | 4 hours |
|
||||
| P1 | Region/node cluster outage, >50% down | 30 minutes | 8 hours |
|
||||
| P2 | Single node failure | 1 hour | 24 hours |
|
||||
| P3 | Degraded performance, not critical | 4 hours | 3 days |
|
||||
|
||||
### Response Procedure
|
||||
|
||||
#### P0/P1 Incidents
|
||||
1. Acknowledge alert immediately
|
||||
2. Declare incident in `#fleet-incidents` Slack channel
|
||||
3. Notify Fleet Lead (direct message/call)
|
||||
4. Execute recovery procedures from relevant playbook
|
||||
5. Document timeline and actions taken
|
||||
6. Schedule post-mortem within 48 hours
|
||||
|
||||
#### P2 Incidents
|
||||
1. Acknowledge within 1 hour
|
||||
2. Open incident ticket in tracking system
|
||||
3. Follow single-node recovery playbook
|
||||
4. Report resolution in daily ops log
|
||||
|
||||
#### P3 Incidents
|
||||
1. Log in issue tracker
|
||||
2. Schedule during next maintenance window
|
||||
3. Document resolution upon completion
|
||||
|
||||
### Recovery Playbooks
|
||||
|
||||
#### Node Restart (most common P2)
|
||||
1. SSH to node (or use remote management)
|
||||
2. Check system logs (`/var/log/timmy/fleet.log`)
|
||||
3. Restart service: `sudo systemctl restart timmy-fleet`
|
||||
4. Verify node rejoins cluster
|
||||
5. Monitor for 30 minutes post-recovery
|
||||
|
||||
#### Network Partition
|
||||
1. Verify network connectivity (ping, traceroute)
|
||||
2. Check firewall rules
|
||||
3. Contact network provider if external
|
||||
4. Switch to backup connection if available
|
||||
5. Document root cause
|
||||
|
||||
#### Storage Full
|
||||
1. Identify large directories (`du -sh /* | sort -hr`)
|
||||
2. Rotate logs: `sudo logrotate -f /etc/logrotate.d/timmy`
|
||||
3. Clean temporary files
|
||||
4. Expand storage or add new volume
|
||||
5. Alert Fleet Lead for capacity planning
|
||||
|
||||
---
|
||||
|
||||
## Escalation Paths
|
||||
|
||||
### Tiered Support Model
|
||||
|
||||
```
|
||||
Operator (Tier 1)
|
||||
↓ (15 min SLA)
|
||||
Senior Operator / Fleet Lead (Tier 2)
|
||||
↓ (1 hour SLA)
|
||||
Timmy Core Team (Tier 3)
|
||||
↓ (Immediate)
|
||||
Executive Sponsor (Critical only)
|
||||
```
|
||||
|
||||
### Contact Matrix
|
||||
|
||||
| Issue Type | Primary Contact | Secondary |
|
||||
|------------|----------------|-----------|
|
||||
| Technical incident | Fleet Lead | Timmy Core |
|
||||
| Payment/incentive | Finance Partner | Fleet Lead |
|
||||
| Training/certification | Training Coordinator | Fleet Lead |
|
||||
| Partnership inquiry | Partner Manager | Executive Sponsor |
|
||||
| Security incident | Security Team | Timmy Core (immediate) |
|
||||
|
||||
### Emergency Contacts
|
||||
- Fleet Lead: `fleet-lead@timmy.foundation` (Slack: @fleet-lead)
|
||||
- Timmy Core On-Call: `oncall@timmy.foundation` (PagerDuty)
|
||||
- Security: `security@timmy.foundation`
|
||||
- Finance: `finance@timmy.foundation`
|
||||
|
||||
---
|
||||
|
||||
## Communication Protocols
|
||||
|
||||
### Channels
|
||||
- `#fleet-operators` — Daily ops, questions
|
||||
- `#fleet-incidents` — Active incidents only
|
||||
- `#fleet-training` — Training resources, scheduling
|
||||
- `#fleet-partners` — Partner program discussions
|
||||
|
||||
### Status Updates
|
||||
- Daily: Stand-up notes in thread
|
||||
- Weekly: Summary post in `#fleet-operators`
|
||||
- Monthly: Ops report submission
|
||||
- Incident: Real-time updates in `#fleet-incidents`
|
||||
|
||||
### Documentation Standards
|
||||
- Use clear, concise language
|
||||
- Include timestamps in UTC
|
||||
- Link to relevant tickets/PRs
|
||||
- Tag stakeholders with `@`
|
||||
|
||||
---
|
||||
|
||||
## Node Deployment
|
||||
|
||||
### Pre-Deployment Checklist
|
||||
- [ ] Hardware meets minimum specs (CPU, RAM, storage)
|
||||
- [ ] Network connectivity validated
|
||||
- [ ] Firewall rules configured
|
||||
- [ ] SSH keys exchanged with Timmy core team
|
||||
- [ ] Monitoring agent installed
|
||||
- [ ] Backup solution active
|
||||
- [ ] Documentation updated with node details
|
||||
|
||||
### Deployment Steps
|
||||
1. Provision hardware/VM
|
||||
2. Install Timmy Fleet software
|
||||
3. Configure node ID and credentials
|
||||
4. Join cluster via `timmy-fleet join <cluster-endpoint>`
|
||||
5. Validate connectivity and heartbeat
|
||||
6. Update inventory spreadsheet
|
||||
7. Set up monitoring alerts
|
||||
8. Complete handover to operator
|
||||
|
||||
### Decommissioning
|
||||
1. Drain node from cluster
|
||||
2. Migrate workloads
|
||||
3. Backup final state
|
||||
4. Shut down cleanly
|
||||
5. Update inventory
|
||||
6. Notify relevant teams
|
||||
|
||||
---
|
||||
|
||||
## Compliance & Reporting
|
||||
|
||||
### Metrics to Track
|
||||
- Uptime (node-level and fleet-wide)
|
||||
- Incident count and severity
|
||||
- Response and resolution times
|
||||
- Training hours completed
|
||||
- Payment/compensation accuracy
|
||||
|
||||
### Reporting Cadence
|
||||
- **Daily**: Ops dashboard (automated)
|
||||
- **Weekly**: Status summary (operator)
|
||||
- **Monthly**: Partner report (template-driven)
|
||||
- **Quarterly**: Performance review with Fleet Lead
|
||||
|
||||
### Audits
|
||||
- Quarterly internal audit by Timmy compliance team
|
||||
- Annual external certification renewal
|
||||
- Ad-hoc security reviews as needed
|
||||
|
||||
---
|
||||
|
||||
## Appendix: Resources
|
||||
|
||||
### Useful Commands
|
||||
```bash
|
||||
# Check service status
|
||||
sudo systemctl status timmy-fleet
|
||||
|
||||
# View logs
|
||||
journalctl -u timmy-fleet -f
|
||||
|
||||
# Restart node
|
||||
sudo systemctl restart timmy-fleet
|
||||
|
||||
# Check node health
|
||||
timmy-fleet health
|
||||
|
||||
# Join cluster
|
||||
timmy-fleet join <cluster-endpoint>
|
||||
```
|
||||
|
||||
### Key Files
|
||||
- Config: `/etc/timmy/fleet/config.yaml`
|
||||
- Logs: `/var/log/timmy/fleet.log`
|
||||
- Health data: `/var/lib/timmy/fleet/health.json`
|
||||
|
||||
### Support Resources
|
||||
- Internal Wiki: `https://wiki.timmy.foundation/fleet`
|
||||
- Operator Portal: `https://fleet.timmy.foundation`
|
||||
- Training Videos: `https://learn.timmy.foundation/fleet-ops`
|
||||
|
||||
---
|
||||
|
||||
**Last Updated**: 2025-05-02
|
||||
**Next Review**: 2025-06-02
|
||||
|
||||
@@ -1,88 +1,143 @@
|
||||
---
|
||||
application_type: fleet_operator
|
||||
version: 1.0
|
||||
---
|
||||
|
||||
# Fleet Operator Application
|
||||
|
||||
## Personal Information
|
||||
> {{APPLICATION_DATE}}
|
||||
> Candidate: {{CANDIDATE_NAME}}
|
||||
|
||||
**Full Legal Name:**
|
||||
_____________________________________________________
|
||||
## Contact Information
|
||||
|
||||
**Address:**
|
||||
_____________________________________________________
|
||||
_____________________________________________________
|
||||
|
||||
**Phone:** ______________________ **Email:** ______________________
|
||||
|
||||
**Date of Birth:** _______________
|
||||
|
||||
## Qualifications
|
||||
|
||||
### Driving Record
|
||||
- [ ] Valid driver's license (state): _______________
|
||||
- [ ] License number: _______________
|
||||
- [ ] Clean driving record for past 3 years (required)
|
||||
- [ ] Insurance available at competitive rate
|
||||
|
||||
### Experience
|
||||
- Years of fleet/vehicle management experience: ______
|
||||
- Years of customer service experience: ______
|
||||
- Mechanical aptitude (describe): ______________________
|
||||
_____________________________________________________
|
||||
**Full Name**: {{CANDIDATE_FULL_NAME}}
|
||||
**Email**: {{CANDIDATE_EMAIL}}
|
||||
**Phone**: {{CANDIDATE_PHONE}}
|
||||
**Location**: {{CANDIDATE_LOCATION}}
|
||||
**Time Zone**: {{CANDIDATE_TIMEZONE}}
|
||||
|
||||
### Availability
|
||||
- Hours per week available: ______
|
||||
- Preferred shift: ☐ Morning ☐ Afternoon ☐ Evening ☐ Flexible
|
||||
- Any scheduling constraints: ______________________
|
||||
_____________________________________________________
|
||||
- **Hours per week**: {{AVAILABILITY_HOURS}}
|
||||
- **Primary availability window (UTC)**: {{AVAILABILITY_WINDOW}}
|
||||
- **On-call flexibility**: {{ONCALL_FLEXIBILITY}}
|
||||
|
||||
## Business Capability
|
||||
## Technical Qualifications
|
||||
|
||||
### Physical Location
|
||||
- Do you have secure parking for 15+ vehicles? ☐ Yes ☐ No
|
||||
- Address for parking/storage: ______________________
|
||||
_____________________________________________________
|
||||
### Experience
|
||||
```
|
||||
Years in IT/DevOps: {{YEARS_EXPERIENCE}}
|
||||
Relevant roles:
|
||||
{{ROLE_HISTORY}}
|
||||
```
|
||||
|
||||
### Equipment
|
||||
- [ ] Smartphone (iOS/Android)
|
||||
- [ ] Reliable internet
|
||||
- [ ] Vehicle for personal transport
|
||||
- [ ] Basic tool kit
|
||||
- [ ] Cleaning supplies
|
||||
### Skills (check all that apply)
|
||||
- [ ] Linux system administration
|
||||
- [ ] Container orchestration (Kubernetes/Docker)
|
||||
- [ ] Cloud infrastructure (AWS/GCP/Azure)
|
||||
- [ ] Networking fundamentals
|
||||
- [ ] Monitoring & alerting (Prometheus/Grafana)
|
||||
- [ ] Incident response/ITIL
|
||||
- [ ] Security best practices
|
||||
- [ ] Automation (Ansible/Terraform)
|
||||
- [ ] Scripting (Python/Bash/Go)
|
||||
- [ ] Timmy platform experience
|
||||
|
||||
### Financial
|
||||
- Account for ACH direct deposit: ______________________
|
||||
- Routing number: _______________ Account: _______________
|
||||
**Additional skills**: {{ADDITIONAL_SKILLS}}
|
||||
|
||||
## Commitment
|
||||
### Certifications
|
||||
{{CERTIFICATIONS}}
|
||||
|
||||
I certify that all information provided is accurate. I understand that:
|
||||
1. This is an independent contractor position
|
||||
2. I must maintain certification through quarterly reviews
|
||||
3. I am responsible for my own taxes and insurance
|
||||
4. I must comply with all Timmy policies and local regulations
|
||||
## Infrastructure Readiness
|
||||
|
||||
**Signature:** ______________________ **Date:** _______________
|
||||
### Proposed Node Environment
|
||||
- **Type**: ☐ Physical ☐ Cloud VM ☐ Hybrid
|
||||
- **Provider**: {{CLOUD_PROVIDER}}
|
||||
- **Region**: {{REGION}}
|
||||
- **Hardware specs**:
|
||||
- CPU: {{CPU_SPEC}}
|
||||
- RAM: {{RAM_SPEC}}
|
||||
- Storage: {{STORAGE_SPEC}}
|
||||
- Network: {{NETWORK_SPEC}}
|
||||
|
||||
## Submission
|
||||
### Redundancy & HA
|
||||
- [ ] Backup power (UPS/generator)
|
||||
- [ ] Secondary internet connection
|
||||
- [ ] Off-site backup solution
|
||||
- [ ] Remote management (IPMI/iDRAC)
|
||||
|
||||
Please submit with:
|
||||
- [ ] Copy of driver's license
|
||||
- [ ] Proof of insurance
|
||||
- [ ] References (2 professional)
|
||||
- [ ] Photos of parking/storage location
|
||||
|
||||
Email completed application to: **operations@timmy.io**
|
||||
|
||||
Response time: 5-7 business days
|
||||
### Connectivity
|
||||
- **Bandwidth**: {{BANDWIDTH}} Mbps
|
||||
- **Latency to Timmy core**: {{LATENCY}} ms
|
||||
- **Uptime SLA**: {{UPTIME_SLA}}
|
||||
|
||||
---
|
||||
|
||||
*Internal Use Only*
|
||||
Application ID: _______________
|
||||
Reviewer: _______________
|
||||
Status: ☐ Pending ☐ Interview ☐ Approved ☐ Denied
|
||||
Notes: ___________________________________________
|
||||
_____________________________________________________
|
||||
## Motivation & Alignment
|
||||
|
||||
### Why do you want to run a Timmy Fleet node?
|
||||
{{MOTIVATION}}
|
||||
|
||||
### What attracts you to decentralized infrastructure?
|
||||
{{DECENTRALIZATION_MOTIVATION}}
|
||||
|
||||
### How does this align with your long-term goals?
|
||||
{{LONG_TERM_GOALS}}
|
||||
|
||||
---
|
||||
|
||||
## Partner Program Interest (Optional)
|
||||
|
||||
### Interested in?
|
||||
- [ ] Referral partner (refer operators, earn commission)
|
||||
- [ ] Channel partner (onboard and train operators)
|
||||
- [ ] Strategic partner (run fleet of 10+ nodes)
|
||||
|
||||
### Existing network
|
||||
{{PARTNER_NETWORK}}
|
||||
|
||||
### Referral pipeline
|
||||
{{REFERRAL_PIPELINE}}
|
||||
|
||||
---
|
||||
|
||||
## References
|
||||
|
||||
### Professional References
|
||||
1. Name: {{REF1_NAME}}
|
||||
Email: {{REF1_EMAIL}}
|
||||
Relationship: {{REF1_RELATION}}
|
||||
|
||||
2. Name: {{REF2_NAME}}
|
||||
Email: {{REF2_EMAIL}}
|
||||
Relationship: {{REF2_RELATION}}
|
||||
|
||||
### Timmy Community Involvement
|
||||
{{COMMUNITY_INVOLVEMENT}}
|
||||
|
||||
---
|
||||
|
||||
## Agreement & Signatures
|
||||
|
||||
### Code of Conduct
|
||||
- [ ] I have read and agree to the Timmy Fleet Operator Code of Conduct
|
||||
- [ ] I understand the uptime and response time requirements
|
||||
- [ ] I agree to the incentive structure and terms
|
||||
|
||||
### Signature
|
||||
**Candidate signature**: ___________________________
|
||||
**Date**: {{SIGNATURE_DATE}}
|
||||
|
||||
**Timmy representative**: ___________________________
|
||||
**Date**: {{TIMPY_SIGN_DATE}}
|
||||
|
||||
---
|
||||
|
||||
## Internal Use Only
|
||||
|
||||
**Interviewer**: {{INTERVIEWER}}
|
||||
**Technical score**: {{TECH_SCORE}}/100
|
||||
**Culture fit**: {{CULTURE_FIT}}/50
|
||||
**Infrastructure audit**: ☐ Pass ☐ Fail
|
||||
**Background check**: ☐ Complete ☐ In-progress
|
||||
|
||||
**Decision**: ☐ Approved ☐ Rejected ☐ Waitlist
|
||||
|
||||
**Comments**: {{INTERNAL_COMMENTS}}
|
||||
|
||||
**Certification ID**: {{CERT_ID}}
|
||||
**Onboarding start date**: {{ONBOARDING_DATE}}
|
||||
|
||||
@@ -1,94 +1,175 @@
|
||||
---
|
||||
report_type: monthly_partner_commission
|
||||
version: 1.0
|
||||
---
|
||||
# Fleet Partner Monthly Report
|
||||
|
||||
# Monthly Partner Commission Report
|
||||
> {{REPORT_MONTH}} {{REPORT_YEAR}}
|
||||
> Partner: {{PARTNER_NAME}} ({{PARTNER_TIER}})
|
||||
> Submitted: {{SUBMISSION_DATE}}
|
||||
|
||||
**Report Period:** ______________ to ______________
|
||||
**Partner:** ______________________
|
||||
**Partner ID:** _______________
|
||||
**Commission Tier:** ☐ Level 1 (20%) ☐ Level 2 (5%)
|
||||
## Executive Summary
|
||||
|
||||
## 1. Referral Summary
|
||||
| Metric | Current Month | Target | Variance |
|
||||
|--------|---------------|--------|----------|
|
||||
| Active nodes managed | {{ACTIVE_NODES}} | {{TARGET_NODES}} | {{NODES_VARIANCE}} |
|
||||
| Fleet uptime | {{UPTIME}}% | 99.5% | {{UPTIME_VARIANCE}}% |
|
||||
| Operator churn rate | {{CHURN_RATE}}% | <10% | {{CHURN_VARIANCE}}% |
|
||||
| Partner-sourced leads | {{LEADS_COUNT}} | {{LEADS_TARGET}} | {{LEADS_VARIANCE}} |
|
||||
| Revenue share earned | {{REVENUE}} | — | — |
|
||||
|
||||
| Referred Partner | Sign-up Date | Active Months | Gross Revenue | Commission % | Commission Earned |
|
||||
|-----------------|--------------|---------------|---------------|--------------|-------------------|
|
||||
| | | | | | |
|
||||
| | | | | | |
|
||||
| | | | | | |
|
||||
| | | | | | |
|
||||
| **TOTAL** | | | | | **$_________** |
|
||||
**Key highlights**:
|
||||
{{KEY_HIGHLIGHTS}}
|
||||
|
||||
## 2. Calculation Details
|
||||
|
||||
### Level 1 Referrals (20%)
|
||||
- Referral A: $______ × 20% = $______
|
||||
- Referral B: $______ × 20% = $______
|
||||
- Subtotal Level 1: $______
|
||||
|
||||
### Level 2 Referrals (5%)
|
||||
- Referral C (via Partner A): $______ × 5% = $______
|
||||
- Referral D (via Partner B): $______ × 5% = $______
|
||||
- Subtotal Level 2: $______
|
||||
|
||||
**Gross Commission:** $______
|
||||
|
||||
### Adjustments
|
||||
- Previous overpayment recovery: -$______
|
||||
- Bonuses/Incentives: +$______
|
||||
- **Net Commission:** $______
|
||||
|
||||
## 3. Referral Performance Detail
|
||||
|
||||
### Top Performing Referrals
|
||||
1. ______________________ ($______ revenue)
|
||||
2. ______________________ ($______ revenue)
|
||||
3. ______________________ ($______ revenue)
|
||||
|
||||
### At-Risk Referrals (need attention)
|
||||
- ______________________ (growth -__%)
|
||||
- ______________________ (churn risk)
|
||||
|
||||
## 4. Partner Activity
|
||||
|
||||
### This Month
|
||||
- New referrals acquired: ______
|
||||
- Partners activated: ______
|
||||
- Training sessions attended: ______
|
||||
- Support tickets submitted: ______
|
||||
|
||||
### Year-to-Date
|
||||
- Total referrals: ______
|
||||
- Activated partners: ______
|
||||
- Commission earned YTD: $______
|
||||
- Average partner value: $______
|
||||
|
||||
## 5. Notes & Comments
|
||||
|
||||
___________________________________________________________________________
|
||||
___________________________________________________________________________
|
||||
___________________________________________________________________________
|
||||
**Top concerns**:
|
||||
{{KEY_CONCERNS}}
|
||||
|
||||
---
|
||||
|
||||
## Approval & Payment
|
||||
## Node Performance
|
||||
|
||||
**Partner Signature:** ______________________ **Date:** _______________
|
||||
### Node Inventory
|
||||
|
||||
**Timmy Finance Approval:** ______________________ **Date:** _______________
|
||||
| Node ID | Location | Status | Uptime (30d) | Revenue Share | Issues |
|
||||
|---------|----------|--------|--------------|---------------|---------|
|
||||
| {{NODE_1_ID}} | {{NODE_1_LOC}} | {{NODE_1_STATUS}} | {{NODE_1_UPTIME}}% | ${{NODE_1_REV}} | {{NODE_1_ISSUES}} |
|
||||
| {{NODE_2_ID}} | {{NODE_2_LOC}} | {{NODE_2_STATUS}} | {{NODE_2_UPTIME}}% | ${{NODE_2_REV}} | {{NODE_2_ISSUES}} |
|
||||
| {{NODE_3_ID}} | {{NODE_3_LOC}} | {{NODE_3_STATUS}} | {{NODE_3_UPTIME}}% | ${{NODE_3_REV}} | {{NODE_3_ISSUES}} |
|
||||
|
||||
**Payment Method:** ☐ ACH Transfer ☐ Check ☐ PayPal
|
||||
*Add rows as needed*
|
||||
|
||||
**ACH Details (if applicable):**
|
||||
- Bank: ______________________
|
||||
- Routing: ______________________
|
||||
- Account: ______________________
|
||||
### Top Node Performers
|
||||
1. **{{TOP_NODE_1_ID}}**: {{TOP_NODE_1_UPTIME}}% uptime, zero incidents
|
||||
2. **{{TOP_NODE_2_ID}}**: {{TOP_NODE_2_UPTIME}}% uptime, quickest response times
|
||||
|
||||
**Payment Date:** _______________ **Amount:** $_____________ **Reference:** ___________
|
||||
### Nodes Requiring Attention
|
||||
1. **{{ATTN_NODE_1_ID}}**: {{ATTN_NODE_1_ISSUE}}
|
||||
2. **{{ATTN_NODE_2_ID}}**: {{ATTN_NODE_2_ISSUE}}
|
||||
|
||||
---
|
||||
|
||||
*Generated by: Partner Operations Team*
|
||||
*Next report: ______________*
|
||||
*Questions: partners@timmy.io*
|
||||
## Incidents & Resolutions
|
||||
|
||||
### Incident Log
|
||||
|
||||
| Date | Severity | Node(s) | Duration | Root Cause | Resolution |
|
||||
|------|----------|---------|----------|------------|------------|
|
||||
| {{INC1_DATE}} | {{INC1_SEV}} | {{INC1_NODES}} | {{INC1_DURATION}} | {{INC1_CAUSE}} | {{INC1_RES}} |
|
||||
| {{INC2_DATE}} | {{INC2_SEV}} | {{INC2_NODES}} | {{INC2_DURATION}} | {{INC2_CAUSE}} | {{INC2_RES}} |
|
||||
| {{INC3_DATE}} | {{INC3_SEV}} | {{INC3_NODES}} | {{INC3_DURATION}} | {{INC3_CAUSE}} | {{INC3_RES}} |
|
||||
|
||||
*Add rows as needed*
|
||||
|
||||
### Mean Time to Recovery (MTTR)
|
||||
- **P0 incidents**: {{MTTR_P0}} hours
|
||||
- **P1 incidents**: {{MTTR_P1}} hours
|
||||
- **P2 incidents**: {{MTTR_P2}} hours
|
||||
- **P3 incidents**: {{MTTR_P3}} hours
|
||||
|
||||
**Improvement opportunities**:
|
||||
{{MTTR_IMPROVEMENTS}}
|
||||
|
||||
---
|
||||
|
||||
## Operator Management
|
||||
|
||||
### Active Operators
|
||||
|
||||
| Operator | Tier | Nodes Managed | Status | Cert Date |
|
||||
|----------|------|---------------|--------|-----------|
|
||||
| {{OP1_NAME}} | {{OP1_TIER}} | {{OP1_NODES}} | {{OP1_STATUS}} | {{OP1_CERT}} |
|
||||
| {{OP2_NAME}} | {{OP2_TIER}} | {{OP2_NODES}} | {{OP2_STATUS}} | {{OP2_CERT}} |
|
||||
|
||||
### Churn / Attrition
|
||||
- **Departed operators**: {{DEPARTED_COUNT}}
|
||||
- **Departure reasons**: {{DEPARTURE_REASONS}}
|
||||
- **Retention initiatives**: {{RETENTION_INITIATIVES}}
|
||||
|
||||
### Training & Certification
|
||||
- **New certifications**: {{NEW_CERTS}}
|
||||
- **Training hours logged**: {{TRAINING_HOURS}}
|
||||
- **Upcoming recertifications**: {{UPCOMING_RECERTS}}
|
||||
|
||||
---
|
||||
|
||||
## Partner Program Metrics
|
||||
|
||||
### Lead Generation
|
||||
- **Total leads received**: {{TOTAL_LEADS}}
|
||||
- **Qualified leads**: {{QUALIFIED_LEADS}}
|
||||
- **Converted to operators**: {{CONVERTED_OPERATORS}}
|
||||
- **Conversion rate**: {{CONVERSION_RATE}}%
|
||||
- **Partner contribution to total pipeline**: {{PARTNER_PIPELINE_PERCENT}}%
|
||||
|
||||
### Referral Commission
|
||||
- **Referral fee earned**: ${{REFERRAL_FEE}}
|
||||
- **Ongoing revenue share**: ${{ONGOING_SHARE}}
|
||||
- **Total YTD earnings**: ${{YTD_EARNINGS}}
|
||||
|
||||
### Partner Activity
|
||||
- **Marketing events hosted**: {{EVENTS_HOSTED}}
|
||||
- **Training sessions conducted**: {{TRAINING_SESSIONS}}
|
||||
- **Community engagement posts**: {{COMMUNITY_POSTS}}
|
||||
- **Collateral created**: {{COLLATERAL}}
|
||||
|
||||
---
|
||||
|
||||
## Financial Summary
|
||||
|
||||
### Incentive Payouts
|
||||
| Category | Amount | Notes |
|
||||
|----------|--------|-------|
|
||||
| Operator stipends | ${{STIPENDS}} | {{STIPENDS_NOTES}} |
|
||||
| Uptime bonuses | ${{UPTIME_BONUS}} | {{UPTIME_NOTES}} |
|
||||
| Mentorship bonuses | ${{MENTOR_BONUS}} | {{MENTOR_NOTES}} |
|
||||
| Performance bonuses | ${{PERF_BONUS}} | {{PERF_NOTES}} |
|
||||
| Partner commissions | ${{PARTNER_COMM}} | {{PARTNER_NOTES}} |
|
||||
|
||||
**Total payout this month**: ${{TOTAL_PAYOUT}}
|
||||
|
||||
### Cost Efficiency
|
||||
- **Cost per node**: ${{COST_PER_NODE}}
|
||||
- **Cost per uptime hour**: ${{COST_PER_UPTIME_HOUR}}
|
||||
- **Efficiency rating**: {{EFFICIENCY_RATING}}/10
|
||||
|
||||
---
|
||||
|
||||
## Goals & Objectives
|
||||
|
||||
### Next Month Targets
|
||||
1. **Uptime**: {{NEXT_UPTIME_TARGET}}%
|
||||
2. **Qualified leads**: {{NEXT_LEADS_TARGET}}
|
||||
3. **New operators**: {{NEXT_OPS_TARGET}}
|
||||
4. **Incident reduction**: {{NEXT_INCIDENT_TARGET}} incidents
|
||||
|
||||
### Priority Initiatives
|
||||
- {{PRIORITY_1}}
|
||||
- {{PRIORITY_2}}
|
||||
- {{PRIORITY_3}}
|
||||
|
||||
### Support Needed
|
||||
- {{SUPPORT_NEEDED_1}}
|
||||
- {{SUPPORT_NEEDED_2}}
|
||||
|
||||
---
|
||||
|
||||
## Attestation
|
||||
|
||||
By submitting this report, I certify that the information provided is accurate and complete to the best of my knowledge.
|
||||
|
||||
**Submitted by**: {{SUBMITTER_NAME}}
|
||||
**Title**: {{SUBMITTER_TITLE}}
|
||||
**Signature**: ___________________________
|
||||
**Date**: {{SUBMISSION_DATE}}
|
||||
|
||||
**Approved by** (Timmy Core): {{APPROVER_NAME}}
|
||||
**Date**: {{APPROVAL_DATE}}
|
||||
|
||||
---
|
||||
|
||||
## Appendix
|
||||
|
||||
### Supporting Documents
|
||||
- [ ] Ops dashboard screenshots attached
|
||||
- [ ] Incident post-mortems attached
|
||||
- [ ] Training completion records attached
|
||||
- [ ] Financial reconciliation attached
|
||||
|
||||
### Notes
|
||||
{{APPENDIX_NOTES}}
|
||||
|
||||
Reference in New Issue
Block a user