Author: Christian Stoupe

Antero work template intervals can trigger on calendar days OR equipment meter readings like hours or miles. Set up PM schedules that say “30 days OR 3,000 miles, whichever comes first”—just like an oil change reminder.

Operator10’s mini preview in the chart properties window lets you experiment with colors, formulas, and layouts safely. See changes in real-time without overwriting your saved chart until you’re satisfied and click Finish.

Antero labor types let you track regular time, overtime, and double time with automatic cost multipliers. Set labor rates for each user or role, then record hours on work orders to calculate true maintenance costs for budget tracking and reporting.

Run a date-range received report, produce billing reports per hauler, and export to PDF. Add them to a report set for one-click month-end.

Not every operator works the same way. Operator10 lets you save multiple versions of the same DataView with different layouts, so each person can open the view that matches their workflow without affecting anyone else.

Antero’s work request module is a lightweight client for non-Antero users to submit maintenance requests with equipment details and descriptions. Supervisors see requests in Antero and create work orders or mark them resolved.

Set Operator10 DataViews to display a 7-day period starting on Sunday, with the current week as the default. Operators see this week’s data every time they open the view, and navigation jumps one week at a time.

Antero’s distribution feature lets you select 10 work orders and assign them all to one maintenance group, print them as a batch, or email them to specific users—all in one action instead of opening each work order individually.

Antero maintenance groups let you assign work orders to a team instead of a specific person. Create groups for electrical, HVAC, or shift-based teams, then let operators grab work from their group’s queue without micromanaging assignments.

Operator10 lets you rename column headers in any DataView without affecting the database. Add group headers to bundle related parameters like “Aeration Basins” so your team sees clean, organized labels instead of long technical names.