The full PM flow: download the template, collect it back, upload, review and approve — approval is what creates the tickets.

1. 1

   Download the template

   Go to Asset Care, then Upload Schedule, and press Download Template. Share it with the team by email or SharePoint for them to fill in for their sites.

2. 2

   Get the columns right

   The first six columns are required: site_code (must match an existing site code), asset_label (use "general" for whole-site PPM, or a device name or serial number), fse_email (must be an active field user), scheduled_date as YYYY-MM-DD, sla_hours as a whole number between 1 and 720, and task_description. A priority column is optional.

3. 3

   Upload the completed file

   Back on Upload Schedule, upload the filled file. The system validates every row as it goes and flags anything it cannot match — an unknown site code, an email that is not an active field user, or a device that does not exist on that site.

4. 4

   Review the batch per engineer

   Review & Approve groups the entries by engineer, with counts for Total entries, Approved, Pending and Rejected. Rows that could not be matched are grouped under Unresolved FSE or Unmatched. Approve stays disabled on those until the site and engineer resolve — the tooltip reads Resolve site/FSE first.

5. 5

   Approve — this is what creates the tickets

   Nothing is created until you approve. Approving a single entry creates one preventive ticket and emails that engineer. Approve all for this FSE creates them in bulk and sends one digest email covering all of them. Approved entries then appear in the engineer's mobile app.

6. 6

   Fix or reject anything wrong first

   Edit lets you change the engineer, date, SLA hours and task before approving. You cannot change the site — delete the entry and re-upload instead, because too much downstream depends on it. Rejecting requires a reason. Once approved, an entry is locked: reschedule via the ticket instead.