Operations

_________________

Data Annotation

Purpose: To create and modify systems to create clear workflows, systems and standards for the team. These systems must be rigidly followed but can be instantly modified should the need arise. The entire team is invited to test every system at any time and make suggestions to improve our overall effectiveness.

Client Intake (with Client Engineers/Quality Assurance)

• Email

• Meeting

  • Scope of Project - What’s the application?

  • Training/Production of Data Set (API Key/File)

  • Tooling - internal, etc

  • Average Handling Time

  • QA Process/Metrics

  • Feedback Loop and Channel

  • Completion Date

Data Collection & Ingestion

• Collection the data

Annotation

• Team Alignment (Look at Guidelines Together, training on tool) 

• Daily Sync (30 min) 

• Annotation Production 

• Check-in (Team Lead) 

• QA Audit` 

• Feedback (quality metrics) (Team Lead and QA) 

• Escalation (to clients) whole project 

• Recalibration Meetings (Team Lead) 

• Weekly Business Meetings (Report to Client from Team Lead) 

Final Delivery

• Format to the ML (Recommended to the client) YOLO 8, 9, 11

Post-Project Report

• Internal Analysis

• External Analysis (Client Review)