docs/8.0/ayanova/docs/svc-pms.md

@@ -4,11 +4,11 @@ A Preventive Maintenance or "PM" order is a "template" work order used to automa
 
 This is used to implement a preventive maintenance program.
 
-A PM is mostly identical to a Service Work order but has some additional fields in it's header area used to set the schedule for generating Service Work orders.
+A PM is mostly identical to a [Service Work order](svc-workorders.md) but has some additional fields in it's header area used to set the schedule for generating Service Work orders.
 
-We won't document the identical fields here, only the fields that are different on a PM from a service work order.
+We won't document the identical features here, only the features that are different on a PM from a service work order.
 
-See the [Work order](svc-workorders.md) documentation page for all other fields and details.
+See the [Work order](svc-workorders.md) documentation page for all other features and details.
 
 ## Authorization Roles required
 
@@ -54,7 +54,7 @@ When a PM is turned into a work order the server directly copies the correspondi
 
 #### Date fields
 
-When a work order is generated from a PM the PM is then updated to move all the relevant date fields forward for the _next_ work order generation. 
+When a work order is generated from a PM the PM is then updated to move all the relevant date fields forward for the _next_ work order generation.
 
 The following date fields are automatically moved forward:
 
@@ -81,7 +81,7 @@ Once the new Work order is successfully generated the source PM is updated so th
 
 #### New service date calculated
 
-A new Service Date is calculated by taking the current Service Date that was just used and adding to it the duration specified in the [Repeat interval](#repeat-interval) field set on the PM header. 
+A new Service Date is calculated by taking the current Service Date that was just used and adding to it the duration specified in the [Repeat interval](#repeat-interval) field set on the PM header.
 
 It then checks the [Exclude days of week](#exclude-days-of-week) setting in the PM header and if the new service date falls on an excluded day it moves the date forward until it reaches a day of the week that is not excluded. _This_ is now the new Service date and is set on the PM.
 
@@ -97,7 +97,7 @@ If the stop generating date will not be reached then the server continues to mod
 
 #### PM dates moved forward
 
-The server calculates the exact time span between the current Service date just used to create a work order and the [new service date](#new-service-date) that was just calculated. This time span is then used to adjust all the PM's [date fields](#date-fields) forward so they all fall on the same relative day and time from each other.
+The server calculates the exact time span between the current Service date just used to create a work order and the [new service date](#new-service-date-calculated) that was just calculated. This time span is then used to adjust all the PM's [date fields](#date-fields) forward so they all fall on the same relative day and time from each other.
 
 At this point the PM is saved with it's new settings for the next time and generation for the PM is completed.
 
@@ -125,7 +125,7 @@ This is a Tag filterable notification so the notification subscription can have
 
 #### Preventive maintenance generation failure
 
-Notification that there was an error or issue of some kind related to generating a work order from a PM. The error message will be provided and if it's unclear what the problem is, there maybe more information available in the AyaNova server operations log. 
+Notification that there was an error or issue of some kind related to generating a work order from a PM. The error message will be provided and if it's unclear what the problem is, there maybe more information available in the AyaNova server operations log.
 
 PM's with temporary issues preventing generation of a work order will try again the next time the PM generation job runs at the server which is every 5 minutes. If the same error arises it will not be sent in a notification to the User for another 12 hours in order to prevent flooding the User with identical notifications.
 
@@ -147,36 +147,34 @@ This notification will be sent once only every 90 days per subscription as it re
 
 This is a Tag filterable notification so the notification subscription can have tags set so that only PM's with matching tags are checked for insufficient inventory.
 
-
 ## PM edit form unique fields
 
 The PM edit form provides all the [standard edit form](ay-start-edit-forms.md) functionality and the following fields that are not found on a [service work order](svc-workorders.md)
 
-
 #### Repeat interval
 
 This field is used to set the length of time between service work orders being generated from the PM by selecting a time period and quantity.
-This value *must* be larger than the Generate before field value to pass validation when saved.
+This value _must_ be larger than the Generate before field value to pass validation when saved.
 
 So, for example, if you wish to service a customer once per year then the Repeat interval should be set to 1 year.
 
 #### Generate beforehand
 
-This field is used to set how far in advance of the Service date the service work order should be created. This value *must* be smaller than the duration set for Repeat interval or the server will not allow the record to be saved. 
+This field is used to set how far in advance of the Service date the service work order should be created. This value _must_ be smaller than the duration set for Repeat interval or the server will not allow the record to be saved.
 
-This should be set taking into consideration how much advance notice is required to ensure sufficient inventory and scheduling before service needs to be performed. There is no harm in setting this earlier than you expect to need, it will appear in the schedule for the appropriate time and gives staff time to be ready for service. 
+This should be set taking into consideration how much advance notice is required to ensure sufficient inventory and scheduling before service needs to be performed. There is no harm in setting this earlier than you expect to need, it will appear in the schedule for the appropriate time and gives staff time to be ready for service.
 
 #### Exclude days of week
 
-Here you can control which day of the week you **don't** want the next service date to fall when it is calculated.  AyaNova will automatically advance the next service date it calculates one day at a time until it hits on a day that is *not* excluded.  Selecting all days of the week is not valid here or nothing would be generated.  Typically this is used to exclude weekends.
+Here you can control which day of the week you **don't** want the next service date to fall when it is calculated. AyaNova will automatically advance the next service date it calculates one day at a time until it hits on a day that is _not_ excluded. Selecting all days of the week is not valid here or nothing would be generated. Typically this is used to exclude weekends.
 
 #### Next service date
 
-When you first create a PM this is the date that will first be used to set the service work order's Service date field.  Subsequently the AyaNova server will [automatically advance this date](#pm-dates-moved-forward) for you each time it generates a new service work order.
+When you first create a PM this is the date that will first be used to set the service work order's Service date field. Subsequently the AyaNova server will [automatically advance this date](#pm-dates-moved-forward) for you each time it generates a new service work order.
 
 #### Stop generating date
 
-This optional field is used to set a limit to how long this PM will generate work orders.  When it detects that a new work order would be generated beyond this date it automatically sets the PM to inactive and stops processing it.
+This optional field is used to set a limit to how long this PM will generate work orders. When it detects that a new work order would be generated beyond this date it automatically sets the PM to inactive and stops processing it.
 
 #### Copy wiki
 
@@ -188,4 +186,22 @@ When checked the PM will copy any PM header section attached files over to the s
 
 #### Active
 
-On a PM the Active field controls whether the PM will be considered for generating service work orders.  Unchecking Active is a quick way to turn off a PM from generation.
+On a PM the Active field controls whether the PM will be considered for generating service work orders. Unchecking Active is a quick way to turn off a PM from generation.
+
+
+### Menu options
+
+In addition to the [common edit form menu options](ay-start-edit-forms.md#common-edit-form-menu-options) and the same options shared with and documented on the [work order help page](svc-workorders.md#menu-options), the Preventive Maintenance edit form also has these unique options:
+
+#### Duplicate to Work order
+
+This menu option makes a service work order by copying the shared fields from the PM to a new service Work order. This is and "on demand" way to turn a PM into a service work order manually; outside the normal automated Preventive maintenance scheduled work order generation system.  This is a direct copy of the PM fields you see, dates are not adjusted here.
+
+#### Duplicate to Quote
+
+This menu option makes a [Quote](svc-quotes.md) by copying the shared fields from the PM to a new Quote. Use this feature if an existing PM is nearly identical to a Quote that needs to be made to save typing or to re-quote an existing PM schedule that's nearing it's end of term.
+
+#### Quote status list
+
+This is a link to edit the Quote states available. See the [Quote status help page](svc-quote-status.md) for more details.
+