When the optimization engine can’t find a feasible improvement, it can’t produce a better route for the tasks. In such a case, the system leaves the current route as is and doesn’t push a new, optimized plan. That’s why the outcome described is that the task route cannot be optimized—the route remains unchanged because no better arrangement could be found within the given constraints. The other options imply actions that only occur if optimization succeeds or if an intervention is triggered separately (like a manual assignment or cancellation). Recalculating and dispatching would be a result of a successful optimization, manual assignment isn’t automatic just because optimization isn’t possible, and cancellation is not the standard response to an unoptimizable route.

Maturity Level 1 - Modernize focuses on strengthening the way field work is executed on the ground. It aims to make field operations more efficient by improving how tasks are managed for field agents, using geolocation to better track and assign work, and automating scheduling to reduce delays and optimize who does what and when. This foundational shift is about making everyday field activities smoother and more reliable. That’s why improving Field Agent task management, geolocation, and automated scheduling best fits Level 1 Modernize. The other options point to capabilities more aligned with higher maturity stages or unrelated areas: trend analysis and IoT automation imply advanced analytics and device integration; Transform refers to a later maturity level; and the option about “Company” doesn’t describe a focused field-service capability.

The key idea is the per-task association of skills through a dedicated mapping between tasks and skills. The Task Skills (task_m2m_skill) table is a many-to-many bridge that links each task (including work order tasks) to the Skill records. This is what lets you declare exactly which skills are required for a given task and, if supported, the level of proficiency needed. With this mapping, both a work order and its tasks can use the same task-skill definitions for skill-based assignment and validation. If skills were attached only at the work order level, you’d lose per-task granularity, since different tasks on the same work order can require different skills. The Skill Matrix table handles broader cross-skill relationships rather than the direct task-to-skill link. The Task Skill Levels table stores level values for a task-skill pair but relies on the existence of the task-skill association itself.

Transforming data at import time is the approach used when the incoming data is inconsistent or needs normalization. Source Transformation lets you apply rules to the incoming data in the Import Set’s Transform Map, transforming the source values before they are mapped to the target fields. This is ideal for problematic data because you can standardize formats, clean up typos, convert date formats, map aliases, or derive correct values without writing scripts. The result is data that already fits the target schema as it enters the system, reducing the need for post-import fixes. The alternative of Fix Scripts would require writing custom code to adjust data during the transform, which is more maintenance-heavy. The other options relate to FSM workflows or case handling and aren’t about transforming data during import.