Using Field Service Lightning for heavy equipment manufacturing

The fitter was still on the machine at dusk. The next customer had been promised that same person after lunch, because the appointment was an hour. The hour came from a template someone had built for a different product. The crate of parts was still in a planner's inbox. The serial number was on the work order. The job was not.

People still search for Field Service Lightning. For a heavy equipment maker, the product is Agentforce Field Service and Operations, formerly Field Service. The help page is plain about the two objects this work depends on.

"Create maintenance plans and templates to standardize your field service tasks." And: "Schedule one-time or recurring work orders for customers, and add details about worker preferences, required skills, and parts." Standardise is the point. A serial number is not a reason to redesign the job.

#The asset, the parts, the time

A commissioning visit, a major service, or a failed hydraulic assembly is not a short domestic call. The technician needs the right skill, often more than one, and the parts on site before they start. Those details belong on the work order. If the parts are still a note in someone's inbox, the appointment is a guess and the machine stays down while the van goes back.

The asset is the thing the work is about. Its family, its serial number, and the site it sits on change who may touch it and what must be on the truck. A work order that names a customer and a suburb, and not the asset, will be staffed like a generic visit. Heavy equipment does not survive that. The skill is often the product family. The part is often specific to that serial range. Lose the asset and you lose both.

Duration has to come from jobs you have watched on that class of machine. A default of one hour, copied from a template someone made for a different product, will fill a day with work that cannot finish. The scheduler will believe the hour. The fitter will still be on the machine at dusk, and the next customer will be waiting on a promise the duration invented.

Say which skills are required. A generic technician skill will pass anyone in the territory. Heavy equipment usually needs a narrower ticket: the product family, the high-voltage isolation, the height, the welding. Put that on the work type and on the work order. If two tickets are genuinely required at the same time, both go on the job, and you accept that fewer people will match. If they are sequential, they are two steps, not one appointment with a stack of requirements nobody holds. A stack that nobody holds does not make the job safer. It makes the job unschedulable, and someone will delete the skills to clear the board.

Preferences matter when the customer site only receives deliveries in a morning window, or requires an induction before tools come out. A quarry and a plant do not have the same access. Leave the site rule on the work order as a preference. Do not bake one customer's gate into the task list for the whole fleet.

#Maintenance plans, not a fresh design each time

A maintenance plan is how the same service happens on every serial number of that type. The template holds the tasks, the skills, the parts, and the duration. The plan says which asset, and how often, if the work truly recurs. A breakdown is a one-time work order. It should still start from the template for that failure mode, not from a blank page, so the parts list is the one engineering already agreed.

Do not build a template per customer unless the task itself is different. Customers vary in site rules. Those are preferences. The torque sequence and the filter kit are the template. Mixing them means the next engineer "improves" a safety step for one account and the rest of the fleet never gets it. You then have fifty procedures and no procedure. The crew follows the one they remember, which is the one from the last site, and a safety step drifts out of the job that still needs it.

When a new machine family ships, write the template before the first unit is installed in the field. The first five installs are how you correct the duration and the parts. They are a bad time to invent the task list from the cab. Engineering, the person who will do the work, and the planner who will schedule it should be able to read the template aloud and agree what one visit is. A definition that does not survive being read aloud will be rewritten on every serial number.

Keep the template on the failure mode, not on the customer complaint. "Machine will not lift" can be three different jobs. The template starts when you know which assembly you are there to touch. If the first visit is only to find that out, that inspection is its own template, with its own skill, its own short duration, and an explicit next step. Do not pretend the inspection and the rebuild are one hour.

#More than one day

Major work often spans days. Treat that as one job with an order: inspect and identify, then parts, then completion. If you book it as separate one-hour appointments with no link, each one can be moved without the others, and day two arrives before the part from day one. The scheduling optimizer is free to prefer the travel and the skill on Thursday over the sequence the machine needs. It is being consistent with unrelated appointments. You created the unrelated appointments.

Leave the later days movable. Day one often finds a failed component the template did not list. The work order can gain a part. The rest of the booking has to be allowed to shift. A frozen week of appointments, made to look busy on a board, will be rewritten by phone anyway. The phone version will not match the board, and the customer will still be holding the first promise.

Tell the customer which day is firm and which day is held. The inspection can be a window you will keep. The completion cannot be a window until the part is on site. A reminder for a day you do not have creates the angry call. Appointment Assistant is the tool the help page names for that message. Send it when the window is real. The way a multi-day job should stay one sequence, with later days allowed to move, is set out in multi-day scheduling. Use that pattern. Do not invent a second one for the factory fleet.

If two people are required for the fit, both are part of the dependency. Moving the fitter and not the second trade, because the second trade was a separate appointment with no link, is the same failure as doing the fit before the inspection. The work order should show both requirements before anyone is promised.

#What the template holds, and what the visit adds

Recurring plans fit true services, the ones that happen every so many operating hours or months. They are the wrong tool for a one-off rebuild. Use a one-time work order, started from the template, and keep the plan for the work that should come back on a calendar. A rebuild forced into a recurrence will come back next interval as if the machine needed the same crisis again. It does not. The plan will create the job anyway, and someone will spend a morning cancelling it.

#After the first five

When a family is new, treat the first installs as corrections, not as heroics. After each one, write what the template lacked: a part, a step, a skill, a duration that was short. If the same gap appears three times, it belongs on the template. If it was one machine, leave it on that work order. This is how the known half gets bigger without pretending the cab can see the future.

In-flight jobs keep the list they started with, unless you deliberately update them. New work gets the corrected template. Editing a live appointment because engineering changed a torque value, without telling the fitter who already left, is how the record and the spanner disagree. Change the template. Tell the people already on site. Do not assume the phone in their pocket has fetched a silent edit, especially where there is no signal. The mobile app is offline-first. The briefing they drove away with is the briefing they have.

Warranty work and billable work can share a template when the tasks are the same. The commercial treatment is not a second task list. A torque sequence does not change because the invoice does. If you clone the template to put a price on it, the safety steps will diverge the first time one copy is corrected. Keep the price off the template. Keep the tasks on it.

A specialist who covers a wide area on purpose is a territory decision, not a duration decision. They may be a member of several child patches because they are the only person with the ticket. That travel is real. It should not be used as a reason to put every fitter on the parent territory. Ordinary services stay in the patch. The wide membership is for the skill that is actually scarce. Otherwise the optimizer will send a local fitter's neighbour on a two-day rebuild simply because the parent made them eligible and the hour-long duration made the job look small.

Heavy equipment work is the asset, the parts, and often more than one day. Agentforce Field Service and Operations can hold that, under the name people still search as Field Service Lightning, only if the template is the job and the appointment is the visit. A one-hour slot borrowed from another trade will keep lying, and the fitter will still be on the machine at dusk.