For new server installations, AW Computing uses a work order with two line items: one...

The requirement is best implemented with one Service Appointment per Work Order Line Item with bulk scheduling. Each server-installation step has independent skill requirements, so each line item should have its own appointment. Bulk scheduling can then assign the same or different resources according to qualification and availability.

In scheduling design, it is important to distinguish eligibility from preference. Work Rules filter candidates that do not satisfy hard constraints such as territory, availability, skills, or boolean conditions, while Service Objectives rank the remaining options. Dispatcher Console actions then use that policy logic to place, move, or dispatch appointments in a controlled way.

The alternatives address different parts of the Field Service model. A single Work Order-level appointment would force both tasks into one scheduling unit, while a Same Start dependency introduces a simultaneity requirement that the scenario does not state.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Work Order Line Item appointments; bulk scheduling; skill-based assignment.