Repeatability
High
The task runs daily with the same 8 vendors, same output schema, and same logic for flagging delays. Layout drift across vendors is the main structural variable, but it's bounded and manageable with per-vendor parsing templates.
Ambiguity Tolerance
Medium
Output format (CSV with standardized part numbers and delay flags) is well-defined, but success depends on a complete and maintained part-number mapping table. Gaps in that mapping create silent errors that are hard to detect automatically.
Data & Tool Availability
Medium
PDFs are available daily, and tools like pdfplumber, Camelot, or LLM-assisted extraction can handle most table layouts. However, portal access automation and maintaining the SKU-to-internal-code mapping table require upfront setup and ongoing maintenance.
Error Cost
Medium
A missed delay flag or wrong quantity could cause a production line disruption, which is a real operational cost. However, the CSV output is reviewable before acting on it, and a daily human spot-check of flagged rows keeps risk manageable.
Human Judgment Required
Low
Delay flagging and data normalization are rule-based once the mapping and thresholds are defined. Novel part numbers or ambiguous status codes are the only cases that genuinely need human input, and those can be routed to a review queue.