Configuring Schedule Costs
The Costs module lets your organization set an expected cost for each kind of equipment maintenance, have operators record what the work actually cost, and export the comparison. "Cost" here means two things at once: money spent, and production lost while the equipment was down.
It is scoped to equipment schedules. Nothing in this module connects to Job costs, Field Tickets, task costs, or Misc Item rates, even though all of those also use the word cost.
Configuration has three parts:
- Switching the module on and granting the permissions
- Deciding who can edit projections
- Setting the projections themselves on the Projected Costs Configuration page
In Organization Settings → Modules, tick Costs.
Then grant the role permissions. There are two, and they are independent:
| Permission | What it allows |
|---|---|
| Costs | Recording actual costs on schedules, and opening the Projected Costs Configuration page |
| Projected Cost Report | Running the Projected Costs Report |
Both only appear in the role editor once the Costs organization setting is on. Someone who needs to run the report but never touches a schedule needs only the second.
With the module off, the Add Cost buttons disappear from schedules, the menu links are hidden, and devices stop downloading projected costs on sync.
Part 2 — Deciding Who Can Edit ProjectionsBeing able to open the configuration page is not the same as being able to change anything on it. Editing projections needs a separate flag, and there are two ways to grant it.
Organization-wide — On the user's settings, tick Costs Admin. This allows the user to edit projected costs across the entire organization, including the schedule-type defaults that apply everywhere. The checkbox only appears when the Costs module is on.
Per area — On the user's location assignments there is a Costs Admin column. Ticking it for a plant, well, or field lets that user modify projections for items in that area only, without giving them the organization-wide defaults.
A user with the Costs permission but neither flag can open the page and read it — every field is greyed out.
This split is the useful part of the design. A regional supervisor can be trusted with the costs for their own plants without being able to shift the numbers everyone else is measured against.
Part 3 — Setting ProjectionsGo to Reports → Rotating Equipment → Projected Costs. On a phone or tablet the menu groups these under a Costs heading instead. The page is titled Projected Costs Configuration.
Expand the Schedules panel. Rows are grouped by schedule category, and Filter by schedule type narrows a long list.
The three levels
This is the core concept, and the thing most likely to be misunderstood. Each schedule type can carry a projection at three levels of specificity:
- Schedule type — the default, applying everywhere in the organization
- Location — a plant, well, or PSV, overriding the type default for that site
- Equipment — a specific unit, overriding both
Expand a schedule type row to see its locations, and expand a location to see its equipment. The most specific projection wins. When an operator records a cost, EZ Ops looks for a projection on that exact piece of equipment first, then falls back to the location, then to the schedule type default. If none exists at any level, the operator sees N/A.
Set the type-level default first and only add location or equipment rows where the real figure genuinely differs. A projection at every level for every unit is a maintenance burden with no benefit.
What you set on each row
| Column | What it holds |
|---|---|
| Cost ($) | The expected dollar cost of doing this job once |
| NGL Lost (m³) | Expected natural gas liquids not produced during the work |
| Condy Lost (m³) | Expected condensate not produced |
| Gas Lost (e3m³) | Expected gas not produced |
| Personnel | Who is expected to do the job — types come from your task personnel list |
| Personnel Time (m) | Expected minutes of that person's time |
| Personnel Cost ($) | Expected cost of that person's time |
Use Add + in the Personnel column to attach a personnel type, and the X beside a row to remove it. More than one personnel type can be attached to a single projection, so a job needing an operator and a contractor can carry both.
Personnel Cost is locked to zero for the Operator type. Operator time is treated as already accounted for rather than billed against the job, so the field is disabled rather than simply defaulting to zero.
Saving and undoing
Editing any field reveals three buttons in the Undo/Save/Delete column. Undo reverts your unsaved change, Save commits it, and Delete removes the projection entirely — confirming with Are you sure you wish to delete this projection?
Deleting a projection does not leave a gap so much as fall back a level. Remove an equipment-level projection and that unit starts inheriting its location's figure.
Every row with a saved projection also has a History button, opening Projected Costs History with the schedule type, location, and equipment it applies to, and a row per change showing the old figures, the action, the user, and the date. Use this when a number has drifted and nobody remembers why.
Part 4 — The Projected Costs ReportReports → Rotating Equipment → Projected Costs Report exports to Excel. There is no on-screen result — the page is a set of options and an Export to Excel button.
Limit by Plant selects which plants are included, with Select All and Unselect All.
Then choose how to model equipment uptime, which is what turns a schedule frequency into a count of expected occurrences over the period:
- Overall % — one Estimated uptime of all equipment figure applied to everything. Quick, and fine for a first look
- Custom Run Times — a per-unit table showing Location, Unit, Historical Run Time (last 365 days), and an Override column. Leave a unit alone to use its historical figure, or type an override percentage where you know next year will differ
Set Start Date and End Date. The end date is disabled until a start date is picked, and an inverted range warns Start date must be before End Date.
Reading the export
The spreadsheet carries organizational columns (CGU, region, area, plant, field, well, equipment) alongside the schedule details, and then three sets of figures:
- Projected cost and losses — what was configured
- Actual cost and losses — what an operator recorded, where they did
- Applied cost and losses — the actual figure where one exists, otherwise the projected one
A Cost Applied column tells you which of the two each row used, reading actual or projected. This is the column that makes the report trustworthy: a total made mostly of projections is a forecast, and one made mostly of actuals is a record. Where both exist, the export also gives you the difference between them.
"A user can see the Projected Costs page but everything is greyed out"
- They have the Costs role permission but neither the organization-wide Costs Admin flag nor Costs Admin on the relevant location assignment
"The Costs Admin checkbox isn't on the user's settings"
- The Costs organization setting is off. Switch on the module first
"Operators say the projected cost shows N/A"
- No projection exists at any of the three levels for that schedule. Set the schedule type default and it will apply everywhere that has no more specific figure
"I set a projection but a specific unit still shows the old number"
- A more specific projection is overriding yours. Check whether that piece of equipment, or its location, carries its own row
"Personnel Cost won't accept a number"
- The personnel type is Operator, for which the field is deliberately locked to zero
"The report total looks too low"
- Check the Cost Applied column. Rows using a projection reflect what was configured, not what happened, and an organization that has configured few projections will produce a thin report
- Check the uptime model. A low Estimated uptime of all equipment produces fewer expected occurrences and therefore a smaller total
"Field crews can't set up projections on their tablets"
- Configuration and the report are online-only. Recording actual costs is the only part of this module that works offline
- Set schedule-type defaults before anything else - One default per schedule type covers the whole organization immediately. Location and equipment rows are for the genuine exceptions, and an organization that starts at the equipment level ends up maintaining hundreds of numbers
- Grant Costs Admin per area rather than organization-wide where you can - It lets a plant supervisor own their own figures without being able to move the baseline everyone is compared against
- Check Cost Applied before quoting a total - A report built mostly from projections is a forecast, however precise the number looks
- Use the History button before changing a figure someone else set - It shows who set it and when, which is usually enough to work out why
- Fill in the loss fields, not just the dollars - Lost production is typically the larger share of what downtime costs, and a projection with zeros in those columns will make every actual cost look like an overrun