Please enable JavaScript.
Coggle requires JavaScript to display documents.
Uber/Apple (Quality (First QC is from the partner (Apple QC Apple/Uber QC…
Uber/Apple
Quality
-
-
-
-
Does feedback get back to editors, project instructions, etc.
-
-
Engineering (BM)
-
-
POCs (BM/KR)
-
MS Indoor/Outdoor
-
-
-
Need to be able to see probe/MoMa data, imagery, source data
-
-
-
-
Metrics/Reporting
Tableau
-
-
-
We don't own it, reliant on MCP support & priority
-
-
-
-
Map Change Submission
Import Tools
ACI ~ MIT API
-
Actions: Stats on how many actually are closed, is it still running. (Michelle to send email to Prischant)
-
-
-
Volume/Counts
Apple
-
-
Actions: Ask new Apple guy if they have any processes running along TT, to ensure there's no negative impact based on changes we make. We also want to see their processes, to see if they can be used for other partners
Uber
**Actions:
- Duplicate tasks - Compare spatially the tickets to see how many tickets duplicate across all submission types.
- Spatial clustering of current edits to work through them in a more streamlined process - Saul/Tarun**
Initial categorization - Filter what can be worked by Uber vs. not first
Is there an issue here? Can it be fixed? Multiple issues? (Microjobber potential)
-
Migration to tools
Iris Projects
Build projects ourselves, then give them access to add the tickets & own project
-
-
-
-
-
Iris - What's needed
-
Need to review current active projects:
- Stop populating Uber-specific projects
- Review project that have multi-client IDs and remove Uber capability
Understand feedback loop - What goes back to editors, what gets incorporated into training/example books
-
-
MEP - Local Checklist
NSM, NDE and Needs Revisit --> Project instruction changes?
-
-
-