Job Resources

An Operations Manager can plan a job in FieldFX and add the resources needed for a job. The purpose is that after planning the job, there is enough inventory in the warehouse to commit the inventory for the job.

When a job is create or planned, it is done in Back Office. Mobile Users can see these resources in the FieldFX Mobile App so they know what or who is assigned. The resources are tracked in job logs or tickets for time, usage, and billing information.

For types of resources, see Resource Examples.

Each Job Resource record links to a resource like a person, piece of equipment, or inventory item. The record tells FieldFX what is needed, when, how much and for what purpose.

Object Schema

Job Resources use the FX5__Job Resource__c object.

These objects and fields are typical for a Job Log object. Depending on your org’s setup and workflow, not all objects and fields may appear or as named below.
Job Resource Schema
Figure 1. Job Resource Object
Table 1. Typical Job Resource Objects and Fields
Category Object Description

Auto Number

The name of the resource

Checkboxes

Checkbox to indicate if this is a parent bundle

Currency

The price of the resource

External ID

An automatically generated unique ID, up to 36 characters, for that job resource across devices and environments

Formula

Text of the Equipment Name

Serial Number of the Equipment

Lookup

User Lookup

Catalog Item Lookup

Equipment Lookup

Job Lookup

Override Lookup

Price Book Item Lookup

Quote Item Lookup

The user who last modified the resource

Owner

Owners of the Job Resource

Number

The quantity consumed

The remaining quantity

The returned quantity

The shipped quantity

A soft quantity for a committed resource

Picklist

The job resource’s status

The Unit of Measure of the resource

Text

Text(255)

On Site Quantity Custom Field

In Job Resource Object, the On Site Quantity Custom Field Formula Options were changed to the following formula:

CASE( Text(FX5__Catalog_Item__r.FX5__ffx_Item_Type__c) ,
"bulk consumables", FX5__Qty_Delivered__c - FX5__Qty_Consumed__c - FX5__Qty_To_Be_Returned - FX5__Qty_Returned__c ,
"bulk asset", FX5__Qty_Delivered__c - FX5__Qty_To_Be_Returned -  FX5__Qty_Returned__c ,
"serialized asset", FX5__Qty_Delivered__c - FX5__Qty_To_Be_Returned - FX5__Qty_Returned__c,
"serialized consumable", FX5__Qty_Delivered__c - FX5__Qty_Consumed__c - FX5__Qty_To_Be_Returned -  FX5__Qty_Returned__c,
"service", FX5__Quantity__c - FX5__Qty_Consumed__c,
"labor", FX5__Quantity__c ,
0
)

Resource Examples

The types of resources that can be added to a job:

Type Example Definition

Bulk Assets

Drill Pipe

The customer needs to ship a quantity of this item, but there is no tracking of each individual item (such as each individual segment of pipe).

It is not consumed on site, but gets utilized and eventually returned in its entirety.

Bulk Consumables

Sand

The customer needs to ship a quantity of this item, but not track each individual item (track each bag of sand).

At the end of the job, if any quantity is not consumed, it will get returned, but the assumption is that all of it is consumed on the job.

Labor

Engineer

The customer needs to send this type of item on site and track its utilization (i.e. days worked while on site) for billing.

This type of item is not shipped (on a truck) and does not get returned or consumed.

Serialized Asset

Cargo Basket

The customer needs to send this type of item on site to be utilized. The item is not consumed and needs to be returned at the end of the job.

These are high value items and need to be tracked individually.

Serialized Consumables

Explosive Charge

The custom sends out this type of item on site and the item is consumed. They need to be tracked individually for regulatory purposes.

If the item is not consumed, it gets returned, but the assumption is that it will get consumed in its entirety by the end of the job.

Service

Per Diem

The customer charges his customer for this type of item but this item is not shipped or returned at the end of the job.

Record Types

Job Resources utilizes these three specific record types:

Type Description

Return

Used to indicate a return ticket.

Delivery

Used to indicate a delivery ticket.

Field

Used to indicate a field ticket.

How Job Resources Work

  1. The system admin (or dispatcher or planner) adds the job resource to a job while in Back Office,
    The admin sets up the resource types. They add personnel, equipment, and inventory as job resource records.

  2. The system admin add the resources to the job in Back Office by going to the Job Resource Related List and add the needed resources. They set the dates, roles, quantities, and notes for each resource.

  3. When the mobile user syncs, the job resources are synced from back office. They see these job resources when they access the job

  4. Use the job resources in the field.
    Field users can log actual usage (hours, equipment used, the amount of material used).

  5. Job resources data can be used for billing and payroll.
    Resources data feeds into invoices, payroll reports (if configured), and job costing.

How Delivery/Return Tickets Work

These are digital records for documenting and managing delivery of materials, equipment, or services to a job site. They are proof of delivery and helps tracks what was delivery, when, by whom, and under job or work order.

How They Work in the FieldFX Mobile App

Inventory Movement Examples

The movement of Job Resources is different in the Delivery/Return Tickets and Manual Status Change flow.

These are examples of how job resources in inventory could move through statuses. Specific movements and statuses are dependent on how your org is configured and operates.

Delivery/Return Tickets

These Delivery and/or Return Ticket example tables show the changes for each type of job resource and its quantities as it’s stepped through the different stages in being used. These stages and statuses shown may be different depending on your org’s configuration and workflow.

The types are shown in rows with the states shown in columns.

Table 2. Delivery/Return Ticket Job Resource by Type

Type

Initial State

Delivery
Ticket
Created

Delivery
Ticket
Received

Field Ticket
Created

Return Ticket 1
Created

Return Ticket 2
Created

Return Ticket 1
Marked Return

Return Ticket 2
Marked Return

Job Status
Changed to
Complete

Bulk Consumable

New

In Transit

On Site

In Transit

Returned

Job Complete

Serialized
Asset

New

In Transit

On Site

In Transit

Returned

n/a

Job Complete

Bulk Asset

New

In Transit

On Site

In Transit

n/a

Returned

n/a

Job Complete

Serialized
Consumable

New

In Transit

On Site

Can’t Return, Nothing to return

Job Complete

Labor

On Site

Service

On Site

Manual Status Change

These Manual Status Change example tables show each type of job resource and it’s quantities as it’s stepped through the different stages in being used. These stages and statuses shown may be different depending on your org’s configuration and workflow.

The types are shown in rows with the status in columns.

Table 3. Manual State Change Job Resource by Type

Type

Initial State

Delivery
Ticket
Created

Delivery
Ticket
Received

Field Ticket
Created

Return Qty
Updated

Job Status
Changed to
Complete

Bulk Consumable

New

In Transit

On Site

Returned

Job Complete

Serialized
Asset

New

In Transit

On Site

Returned

Job Complete

Bulk Asset

New

In Transit

On Site

Returned

Job Complete

Serialized
Consumable

New

On Site

Job Complete

Labor

On Site

Job Complete

Service

On Site

Job Complete

Setup and Use

See Job Resources Setup for steps on setting up job resources.

See Job Resources Use for steps on using job resources.