WEBVTT

00:00:00.029 --> 00:00:05.130
In Workforce, open Resource costs, then select Add resource profile.

00:00:05.530 --> 00:00:09.729
Choose Unit as the Subject type and select the fictional community van.

00:00:10.170 --> 00:00:14.270
Give the profile a clear Name and check its Effective and Expires dates.

00:00:14.560 --> 00:00:18.649
The saved example covers October through November and uses U S D.

00:00:18.649 --> 00:00:24.190
A resource profile prices the selected unit, asset or external resource class.

00:00:24.430 --> 00:00:28.219
Check that subject before applying rates to an operational resource.

00:00:28.390 --> 00:00:32.930
In Depreciation, the example enters an Acquisition cost of ten thousand

00:00:33.160 --> 00:00:35.189
and a Salvage value of one thousand.

00:00:35.649 --> 00:00:39.450
Choose Per operating hour as the Allocation basis and enter

00:00:39.450 --> 00:00:41.530
nine hundred Useful life units.

00:00:41.920 --> 00:00:47.020
The form gives the straight-line formula: cost minus salvage, divided by life.

00:00:47.379 --> 00:00:50.570
These fictional inputs produce ten per operating hour.

00:00:50.949 --> 00:00:53.699
Expected annual utilization is six hundred.

00:00:54.170 --> 00:00:58.190
Use units that match the chosen basis; this software example does

00:00:58.190 --> 00:01:00.160
not prescribe an accounting policy.

00:01:00.349 --> 00:01:03.369
Add a Cost components row for Fuel or energy.

00:01:03.800 --> 00:01:07.850
Use the operating-hour basis, Consumption of two and Unit price

00:01:07.850 --> 00:01:10.250
of four, with Manual as the Source.

00:01:10.630 --> 00:01:13.609
That combination produces eight per operating hour.

00:01:14.019 --> 00:01:18.229
Mark the fictional component and profile Approved, then select Save.

00:01:18.629 --> 00:01:22.740
The saved profile row shows depreciation of ten and one component.

00:01:23.139 --> 00:01:27.539
Reopening lets you check the subject, dates, approval and component inputs

00:01:27.600 --> 00:01:29.799
instead of relying on an unsaved form.

00:01:30.070 --> 00:01:33.430
Open Work entries and add the fictional worker’s two Regular

00:01:33.430 --> 00:01:34.969
hours on November second.

00:01:35.510 --> 00:01:40.000
Enter the exercise call number, fifty-one thousand and one, in Call number.

00:01:40.380 --> 00:01:43.840
Keep the chosen establishment, identify the fictional source,

00:01:44.069 --> 00:01:46.229
and review Approved before Save.

00:01:46.680 --> 00:01:50.700
The saved row shows two hours, the call context and Yes.

00:01:51.120 --> 00:01:55.290
Associating hours with the correct call is essential: an approved work

00:01:55.290 --> 00:01:59.329
entry without that call relationship would not be the same call-cost input.

00:01:59.590 --> 00:02:03.809
Open Cost runs and find Call number with Calculate call cost.

00:02:04.259 --> 00:02:08.179
This control uses work entries and resource usage recorded against

00:02:08.179 --> 00:02:10.259
that call and supplies no revenue.

00:02:10.740 --> 00:02:14.669
The recording retains a before-and-after comparison from this exercise.

00:02:15.049 --> 00:02:19.489
Its first successful result shows fifty-four in Personnel, zero in

00:02:19.489 --> 00:02:21.739
Resources and fifty-four total.

00:02:22.140 --> 00:02:25.290
Two hours at the configured loaded estimate of twenty-seven

00:02:25.339 --> 00:02:26.819
explain the personnel amount.

00:02:27.229 --> 00:02:31.670
A zero resource result does not prove the vehicle cost nothing; first

00:02:31.769 --> 00:02:33.479
check whether usage was recorded.

00:02:33.680 --> 00:02:37.509
From the cost result, open Resource usage and add a reading.

00:02:37.980 --> 00:02:41.959
Select the same community van, the exercise date, Incident as the

00:02:41.959 --> 00:02:44.180
Phase and Manual as the Source.

00:02:44.549 --> 00:02:48.400
Enter two Operating hours, then review Approved and Save.

00:02:48.770 --> 00:02:51.930
The saved usage row confirms two operating hours.

00:02:52.339 --> 00:02:56.829
This exercise uses operating hours, so it leaves odometer, engine-hour

00:02:56.880 --> 00:02:58.800
and fuel-quantity inputs empty.

00:02:59.180 --> 00:03:02.520
Match the recorded measurement to the allocation basis rather

00:03:02.520 --> 00:03:06.069
than entering the same work into several unrelated meter fields.

00:03:06.269 --> 00:03:08.880
Recalculate the call after saving its usage.

00:03:09.279 --> 00:03:13.710
The recorded result now shows Personnel of fifty-four, Resources

00:03:13.710 --> 00:03:16.199
of thirty-six and a total of ninety.

00:03:16.590 --> 00:03:19.849
The resource contribution is twenty in depreciation plus

00:03:19.849 --> 00:03:24.619
sixteen in fuel or energy: two hours multiplied by ten and eight.

00:03:25.129 --> 00:03:28.110
Compare the input quantities and saved result together.

00:03:28.520 --> 00:03:32.440
A configured resource profile needs corresponding usage before this

00:03:32.440 --> 00:03:34.469
example contributes a resource amount.

00:03:34.619 --> 00:03:39.099
Return to the same work entry and enter forty in Approved payroll cost,

00:03:39.340 --> 00:03:41.630
retaining a clearly fictional source.

00:03:42.099 --> 00:03:45.950
Save and verify forty on the work-entry row, then recalculate.

00:03:46.379 --> 00:03:50.320
Personnel becomes forty, Resources stays thirty-six and

00:03:50.320 --> 00:03:52.209
the total becomes seventy-six.

00:03:52.580 --> 00:03:56.639
The form explains that this approved payroll input replaces the estimate.

00:03:56.969 --> 00:03:58.879
No payroll system was contacted.

00:03:59.359 --> 00:04:02.980
The saved result still has one Missing input and is not Frozen;

00:04:03.340 --> 00:04:05.320
its index says Needs review.

00:04:05.699 --> 00:04:09.449
Inspect that state before using a total as a finished cost report.

00:04:09.659 --> 00:04:13.960
These controls can support security patrols, search and rescue, wildland

00:04:13.960 --> 00:04:19.039
contractors, industrial emergency teams, community paramedicine or mental health

00:04:19.039 --> 00:04:21.990
response, and fire or E M S operations.

00:04:22.570 --> 00:04:27.520
Use a resource, measurement basis and call context that fit your organization.

00:04:28.059 --> 00:04:32.509
Verify saved inputs, recalculate after changes, and resolve review

00:04:32.509 --> 00:04:34.620
items before relying on the result.

00:04:35.110 --> 00:04:39.259
All amounts here are fictional software inputs, with no external payment,

00:04:39.370 --> 00:04:41.479
invoice or real payroll import.
