Explanation
Field Service Lightning Admin Permissions are required to set up new territories, define new schedule policies, and control settings on the Gantt chart. These permissions allow users to access and modify field service settings and objects.
References: https://help.salesforce.com/s/articleView?id=sf.fsl_permissions.htm&type=5

Explanation
The Exclude Technician from Geolocation Tracking permission allows disabling geolocation tracking for specific service resources by assigning them a permission set with this permission. Setting the Geolocation Update Frequency field to zero for contractors would not disable geolocation tracking, but would make it update less frequently. Unchecking the Geocoding field on the Contractor's profile or the Collect Service Resource Geolocation History field in Field Service Mobile Settings would not affect geolocation tracking, as these are not related settings. References:
https://help.salesforce.com/s/articleView?id=sf.fs_geolocation_tracking_permissions.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_geolocation_tracking_settings.htm&type=5

Explanation
Work types are used to define the standard duration and skills required for a specific type of work. By creating work types for similar site visits, the creation of work orders can be streamlined and standardized.
References:
https://trailhead.salesforce.com/en/content/learn/modules/field_service_basics/field_service_work_types

Explanation
Products consumed are records that track the products used during a service appointment[32]. A custom installation date field on products consumed would allow reporting on the volume of products installed within a specific timeframe by filtering on the installation date field values[33]. A work order related list on asset would show the work orders associated with an asset, but not the products installed. Field history tracking on asset would track field changes on an asset, but not the products installed. The standard installation date field on asset would show when an asset was installed, but not the products installed. References:
https://help.salesforce.com/s/articleView?id=sf.fs_products_consumed.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.reports_filter_date_fields.htm&type=5

Explanation
Frequency is a field on the Maintenance Plan object that defines how often work orders should be generated from maintenance plans such as daily, weekly, or monthly[228]. Generation Timeframe is a field on the Maintenance Plan object that defines how many work orders should be generated from maintenance plans at a time such as 1, 2, or 12[229]. Auto-generate work orders is a field on the Maintenance Plan object that enables or disables the automatic generation of work orders from maintenance plans[230]. Setting Frequency to 1 Month; Generation Timeframe of 12; uncheck Auto-generate work orders would allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit by creating maintenance plans that generate one work order per month for 12 months but do not generate them automatically until the customer calls[231]. Setting Frequency to 1 Month; Generation Timeframe of 1; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for one month and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 12; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for 12 months and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 1; uncheck Auto-generate work orders would not allow Universal Container