Skip to main content
Share / Export

Generating SM PM Work Orders

SM Generate PM Work Orders creates preventative maintenance work orders for services defined on an agreement. Search filters due services; Search fills the grid; Process queues generation (SQL Agent). Trimble spelling on help pages is “preventative.”

Menu: Service Management → Programs → SM Generate PM Work Orders.

Before you start​

  • No formal prerequisites list. Implied: services on an agreement with a recurring pattern (SM Work Schedule, Schedule tab).
  • Optional: Generate Agreement WO Time and Next Work Order Number in SM Company Parameters.
  • Agreement Separate Scope Per Service Item; service Separate Work Order.
  • Auto-trip only if Assigned Tech (SM Service) is Active in SM Technicians and PR Employees.

Steps​

  1. Open SM Generate PM Work Orders.
  2. Set search criteria (any combination): Service Center, Customer, Service Site, Agreement Type. Field defs also include Division (blank = not filtering by division); the procedure omits Division.
  3. Enter Due Within the Next ___ days (procedure default 30; field defs only say enter the number of days).
  4. Click Search. Grid = services due in that window that match filters. Services with Separate Work Order unchecked that share criteria (service site, schedule date, pricing method, and so on) can show together in Service Name (for example “Service #1, Service #2”) and group on one work order/scope.
  5. Check Create (or Check All). Optionally check Skip.
  6. Optionally use View Skipped Work Orders (field defs): checked + Search shows only skipped services; unchecked shows only non-skipped.
  7. Click Process → confirm message with count to generate and/or skip → Yes.
  8. SQL Agent job runs. Summary form/grid shows ID, Status Requested, Requested Time. If Generate Agreement WO Time is set, held until that time; else starts within about a minute. Multiple requests run in Requested Time order. When done, status = Complete.

What Create / Skip / neither do​

  • Create: one PM work order in SM Work Orders and one scope for that service/due date (subject to grouping rules below).
  • Skip: flags that due-date instance as skipped and unavailable later. Future due dates stay.
  • Leave both unchecked: exclude this session only.

How WOs and scopes are built​

  • Service Center match is service-level (SM Work Schedule) or site-level (SM Service Sites). Customer filters agreements/services for that SM customer.
  • If Separate Scope Per Service Item is selected: one scope per serviceable item on class maintenance tasks; else items with matching criteria group on one scope.
  • If Separate Work Order is selected: separate work order with a single scope; else services join an existing matching work order only if status is New, otherwise a new work order.
  • If both apply: separate work order for each service flagged Separate Work Order; remaining services one work order with separate scopes per service item.
  • Assigned Tech becomes the single trip tech and Lead Tech; trip has no description, details, date, time, or duration.
  • WO numbers come from Next Work Order Number.

Scope due type/date (from SM Work Schedule)​

  • Due On → Due type 0-By, due-on date from pattern.
  • Due By → Due type 0-By, due-by date (same pattern example as Due On in Trimble help).
  • Due Within → Due type 1-Within, range from due-within days plus pattern.

Hard rules​

  • Selections are not saved. Changing filter criteria before Process clears every Create checkbox.
  • Grid omits a service that already has a work order for a due date inside the window, but still lists other frequency dates in the window.
  • Skip only if you will never perform that instance. Do not Skip if you will generate later. Skip does not remove future instances.
  • Will not generate out of sequence unless the prior due date is Skipped.
  • One SQL Agent job per SM company; later requests in the same company join that job. Queue starts with the earliest Requested Time.

Notes​

  • Related: SM Agreements; SM Service; SM Work Orders; Remove the Skip Status on Agreement Services; About Creating/Skipping Work Orders; SM Company Parameters; SM Service Centers; SM Service Sites; SM Agreement Types; SM Work Schedule; SM Technicians; PR Employees; SM Generate Work Order Summary (process page also says “PM Generate Work Order Summary”).