Why track parts changes?

Manual inventory tracking using spreadsheets or paper logs is prone to errors, omissions, and intentional misreporting. Someone might adjust quantities without noting it, or a transfer might not get recorded. Parts audit trail automates this logging: every time inventory changes in Antero—through work order usage, stock adjustments, transfers, or receipts—Antero records the change with full context. This creates an unbroken chain of custody for parts.

What the audit trail records

The parts audit trail captures: Date Recorded (when the system logged the change), Usage Date (when the part was actually used or adjusted), Source (where the change came from: work order, stock adjustment, transfer, receipt), Part and Description, Warehouse and Area (location at the time of change), Quantity Change (positive or negative amount), and User (who made the change). This complete record answers “who, what, when, where, how much” for every inventory movement.

Access the parts audit

Go to the Parts section, select a specific part, and click the Audit or History tab at the bottom of the part details panel. This shows all recorded changes for that part: every work order that consumed it, every stock adjustment, every transfer between locations, every receipt from suppliers. Scroll through chronologically to see the part’s complete usage history. If current quantity doesn’t match expectations, the audit trail reveals where discrepancies occurred.

Investigate inventory discrepancies

If a part shows 10 units in the system but physical count finds only 7, the parts audit trail helps reconcile. Review recent changes: were 3 units used on a work order but not recorded? Did someone perform a stock adjustment? Was there a transfer to another location that didn’t process correctly? The audit trail narrows down when and how the discrepancy occurred, guiding corrective action.

Track usage by user

The User field in the audit trail shows who recorded each change. If inventory adjustments happen without proper authorization, you can see which user made them and when. This accountability discourages casual or unauthorized adjustments and helps managers enforce inventory control policies. It also helps training: if one user frequently makes errors, targeted coaching can fix the issue.

Distinguish date recorded from usage date

Parts audit trail separates Date Recorded (when someone entered the change into Antero) from Usage Date (when the part was actually consumed or adjusted). These often differ. A work order might be completed Friday (usage date) but not entered into Antero until Monday (date recorded). This distinction is important for audit and compliance purposes, showing both system timestamps and real-world activity dates.

Monitor transfers between locations

When parts move between warehouses, storerooms, or job sites, the parts audit trail logs both the source and destination. If 5 units transferred from Warehouse A to Warehouse B on Tuesday, the audit shows a -5 change for Warehouse A and a +5 change for Warehouse B, both linked to the same transfer transaction. This dual logging prevents parts from vanishing during transfers due to incomplete recording.

Support compliance and audits

Regulatory audits or financial audits often require proving parts expenditures and inventory levels. The parts audit trail provides auditor-ready documentation: here’s every part used, when, by whom, on which work orders. Auditors can trace high-value or controlled parts from purchase through usage through disposal with complete accountability. This transparency satisfies audit requirements without scrambling to reconstruct history.

Combine with full Antero audit trail

The parts-specific audit is part of Antero’s broader audit trail system (available as an add-on in Antero 7). The full audit trail logs changes across all Antero modules: equipment edits, work order modifications, user permission changes, and more. Go to Audit Trail (top right) to see system-wide changes with filtering options. This comprehensive logging creates a complete activity record for the entire CMMS, not just parts.

Filter audit data for reporting

The audit trail section includes filtering tools. Filter by date range to see changes during a specific period. Filter by user to see one person’s actions. Then Filter by action type (e.g., only stock adjustments or only work order usage). These filters help you quickly isolate relevant data when investigating issues or preparing reports without scrolling through thousands of records.

Audit trail is read-only

The parts audit trail displays information automatically captured by Antero; users cannot edit or delete audit records. This immutability is critical for accountability. Even administrators can’t retroactively alter the audit trail to hide mistakes or misconduct. The record is permanent, ensuring trust in the data for investigations, audits, and management reviews.

Why accountability matters

Parts are expensive assets. Losing track of them costs money. Parts audit trail ensures every part movement is documented and traceable, which reduces theft, prevents errors, and supports informed decisions about inventory management. When everyone knows their actions are logged, accountability drives better behavior and more accurate record-keeping.

Next Steps: Enable Antero parts audit trail for full accountability →

The post Parts Audit Trail in Antero: Track Quantity Changes & Transfers appeared first on AllMax Software.

What is a NetDMR copy of record?

After submitting a DMR through your state’s NetDMR system, you can download a copy of record—a detailed PDF or document listing every parameter you reported, every code used, every permit limit, and every monitoring location. This official record shows what the state expects to see in your electronic submissions. When setting up Operator10’s NetDMR feature, this document is your reference guide. Every value in Operator10 must align with this copy of record, or uploads will fail validation.

Download copy of record from NetDMR system

Log into your state’s NetDMR portal (the web-based system where you currently submit DMRs manually). After submitting a DMR, look for “Download Copy of Record,” “View Submission,” or similar options. Download the file and save it. Ideally, download copies for an entire year (12 months) because some permits have seasonal variations—different limits in summer vs winter, quarterly parameters that only appear certain months, or annual metals testing. Reviewing all 12 months reveals these variations upfront.

What the copy of record shows

The NetDMR copy of record includes: Permit Number and Discharge Number (critical identifiers that link your submission to your facility), Parameter Store Codes (unique numeric codes for each parameter like 50050 for flow, 00310 for BOD), Monitoring Location Codes (usually 1, 2, or 3 indicating effluent, influent, or other sample points), Permit Limits (monthly average, daily max, etc.), Units (mg/L, MGD, lbs/day with unit codes like 19 for mg/L, 03 for MGD), Frequency and Sample Type (3/week, continuous, composite, grab), and Season Codes (if limits change by season). This complete picture ensures nothing is missed when building Operator10 reports.

Match Operator10 setup to copy of record

When creating a NetDMR report in Operator10, open the copy of record alongside the software. For each parameter on the copy of record, add the same parameter to Operator10. Enter the Parameter Store Code exactly as shown (50050, not 5005 or 50500). Enter the Monitoring Location Code (usually 1). Set Permit Limits to match monthly average and daily max values from the copy of record. Choose the correct Unit Code from Operator10’s dropdown, matching the numeric code on the copy of record. Enter Frequency (999 for continuous, 3 for 3/week, etc.) and Sample Type(TM for totalizer, CP for composite, GR for grab). Every field matters.

Identify seasonal variations

Compare copies of record from multiple months. If ammonia limits are 5.0 mg/L January–March but 2.5 mg/L April–October, you’ll need to account for this in Operator10. Some plants create separate NetDMR reports for different seasons with different permit limits. Others use Operator10’s date-based limit features. The copy of record reveals these variations that aren’t always obvious from permit documents alone, which might describe limits in regulatory language rather than showing month-by-month reality.

Verify quarterly and annual parameters

Some parameters only appear quarterly or annually: toxicity tests, metals scans, priority pollutants. Check copies of record from those months to see these parameters’ codes, limits, and frequencies. If you only look at monthly copies, you’ll miss them. When setting up Operator10, include these parameters with appropriate notes indicating they’re quarterly or annual, so operators don’t wonder why they’re on the report form.

Compare permit documents to copy of record

Permit documents (the official regulatory permit issued by EPA or state) sometimes differ from the NetDMR copy of record. Permits might have outdated limits if they haven’t been renewed recently, or they might list parameters that aren’t actually reported electronically. The copy of record is gospel—it reflects what the state’s NetDMR system actually expects. If your permit says one thing but the copy of record shows another, follow the copy of record and contact the state to clarify the discrepancy.

Use copy of record for troubleshooting

If Operator10 generates a NetDMR file and the upload to the state system fails, the error message often references codes or values. Open the copy of record and compare to what Operator10 exported. Is the parameter code correct? Is the monitoring location code right? Did you use the wrong unit code? The copy of record is the answer key for troubleshooting. Most upload failures stem from code mismatches, and the copy of record reveals exactly what the state expects.

Update Operator10 when permits change

When your facility receives a new permit or permit modification, download a fresh NetDMR copy of record after your first submission under the new permit. Compare it to your previous copies. Identify new parameters, changed limits, or removed parameters. Update your Operator10 NetDMR report to match. Without checking the copy of record, you might continue reporting old limits or miss new requirements, causing compliance issues or upload failures.

Keep copies for historical reference

Save NetDMR copies of record in a dedicated folder organized by month and year: “2024-01-NetDMR-CopyOfRecord.pdf,” “2024-02-NetDMR-CopyOfRecord.pdf,” etc. These serve as compliance documentation proving what you reported and when. During audits or regulatory reviews, copies of record show the state what they received from you. They’re also useful training materials for new staff learning the NetDMR setup process.

Why this document is essential

Setting up NetDMR in Operator10 without a copy of record is like building furniture without instructions—you might get close, but critical details will be wrong. The copy of record eliminates guesswork, ensures accuracy, and prevents upload failures. It’s the single most important document for successful electronic DMR reporting.

Next Steps: Set up NetDMR reporting in Operator10 →

The post NetDMR Copy of Record: The Blueprint for Setting Up Operator10 Reports appeared first on AllMax Software.

Why use default addresses?

Most POs ship to the same location: your plant or facility. Most bills go to the same accounting department. Manually entering these addresses on every PO is repetitive busywork that doesn’t add value. Default shipping and billing addresses eliminate this: configure defaults once, and Antero fills them in automatically. You only intervene when a PO needs a different address—like shipping to a satellite location or billing a different department for project-specific purchases.

How to set default addresses

Go to Ordering > Address List in Antero. You’ll see a list of all saved addresses. Create or select your primary shipping address (plant location) and billing address (accounting department or main office). Check the Default Shipping or Default Billing boxes next to the appropriate addresses. Save the changes. From now on, every new purchase order auto-populates with these defaults.

Addresses populate on new POs

When you create a new purchase order, Antero fills the Shipping Address and Billing Address fields with your defaults automatically. You can review them to ensure they’re correct, but in most cases you leave them as-is and proceed to adding parts. This saves 30-60 seconds per PO—time that compounds when creating dozens of POs monthly.

Override defaults when needed

Default shipping and billing addresses are starting points, not restrictions. If a specific PO needs to ship to a different location—maybe a remote pump station or a contractor’s site—click the address field dropdown and select a different saved address, or manually edit the address for that PO only. The override doesn’t change the default; it only affects the current PO. Future POs still use the default unless you override them too.

Manage multiple addresses

In the Address List, add as many addresses as needed: main plant, water treatment facility, pump stations, office building, contractor sites, etc. Label each clearly: “Main Plant Shipping,” “South Station Shipping,” “Accounting Dept Billing.” When creating a PO, if you need an address other than the default, select it from the dropdown. This is faster than typing addresses from scratch and prevents typos.

Use for multi-site organizations

Organizations with multiple facilities can set different defaults depending on who creates POs. If the main plant’s maintenance supervisor creates most POs, set their plant address as default. If the water treatment facility supervisor also creates POs, they might set a different default on their workstation. Antero allows user-specific or database-wide defaults (depending on configuration), so each location can optimize their workflow.

Update defaults when relocating or reorganizing

If your plant moves or you restructure departments, update the default addresses once in the Address List. All future POs reflect the new default. Past POs remain unchanged (they used the old default at the time they were created), but new POs automatically use updated addresses. This one-time update prevents having to remember to change addresses on every PO during transition periods.

Billing address for cost tracking

The billing address isn’t just for where invoices go—it can indicate which cost center or department pays for the order. Some organizations create multiple billing addresses representing different budget accounts: “Operations Budget,” “Capital Projects Budget,” “Emergency Repairs Budget.” Selecting the appropriate billing address when creating a PO links that order to the correct financial account for reporting and reconciliation.

Print shipping labels from POs

If your suppliers ship directly to you, the shipping address on the PO becomes the shipping label info. Accurate default shipping addresses ensure suppliers ship to the correct location without confusion. If an address is wrong, shipments go to old facilities, closed buildings, or incorrect departments, causing delays and rework. Setting correct defaults prevents these costly mistakes.

Audit old addresses periodically

Over time, the Address List accumulates obsolete entries: old contractors, closed facilities, retired cost centers. Periodically review and delete unused addresses to keep the list clean. This makes it easier to find the right address when creating POs and reduces the chance of accidentally selecting an outdated address. Keep the list to 5-10 active addresses unless you truly need more.

Why automation matters here too

Small time savings compound. Saving 30 seconds per PO × 50 POs per month = 25 minutes per month = 5 hours per year. Multiply across multiple users creating POs, and default shipping and billing addresses save significant collective time annually while also reducing address-related errors that cause shipment delays or billing issues.

Next Steps: Optimize Antero purchasing workflows with defaults →

The post Default Shipping and Billing Addresses in Antero: Auto-Populate Purchase Orders appeared first on AllMax Software.

Why use month summary for chemical tracking?

Daily chemical usage data is useful for process control, but budget planning requires monthly totals. How many pounds of chlorine did we use in October? What was the average daily polymer dose in September? How does this year’s alum usage compare to last year? Month summary DataViews answer these questions by aggregating daily values into monthly summaries, so you see one row (or column) per month instead of 28–31 rows.

How to create a month summary DataView

When creating a new DataView in Operator10, the top of the dialog box has a View Type dropdown that defaults to Daily. Change it to Month Summary. Then filter and select the location parameters you want to track: chemical feed rates, total pounds used, calculated costs, etc. When you click OK, Operator10 displays the DataView as a 12-month grid, with each column (or row) representing one month. Summary values like Sum, Average, Min, or Max appear for each month.

Choose the right summary type

For chemical usage, Sum is the most common summary type because you want to know total pounds used per month. For chemical feed rates, Average might be more useful because it shows the typical daily dose. You can display both by adding the same parameter twice: once with Sum summary type, once with Average summary type. For example, create columns for “Total Chlorine Used (Sum)” and “Avg Daily Chlorine Dose (Average)” so you see both metrics side by side.

Add calculated cost columns

If your Operator10 database includes chemical cost per pound or gallon, you can create calculated parameters that multiply usage by cost and display total monthly expenditure. For example, if polymer feed rate is stored in pounds per day and you have a “Polymer Cost per Pound” parameter, create a formula that multiplies feed rate × cost. Add that calculated parameter to your month summary DataView with a Sum summary type, and you’ll see total monthly cost for polymer. Repeat for each chemical to build a complete cost tracking view.

Set a useful date range

Month summary DataViews default to showing the current calendar year (12 months). To compare multiple years, click the date range dropdown and select Custom. Set the start date to January 1 of the earliest year you want to review and the end date to the current month. The DataView expands to show every month in that range, grouped by year. This is useful for multi-year budget analysis or spotting seasonal usage patterns that repeat annually.

Use for council meetings and budget reviews

Many plants print or export their month summary DataView for chemical costs at the end of each month and present it at council meetings, budget hearings, or internal management reviews. The 12-month layout provides a clear year-to-date snapshot of spending. If alum costs spiked in July, the council sees it immediately. If chlorine usage has been dropping over the year, the trend is obvious. No need to build a separate report—just open the DataView, adjust the date range if needed, and export to Excel or print to PDF.

Track multiple chemicals in one view

A well-designed month summary DataView for chemical costs includes all major chemicals your plant uses: chlorine, alum, polymer, ferric chloride, sodium hydroxide, etc. Each chemical gets two columns: one for total pounds used (Sum) and one for total cost (Sum of calculated cost parameter). Add a column for total monthly flow (Sum) so you can see usage relative to treatment volume. Supervisors can review the entire chemical program’s performance and costs in one screen.

Combine with custom column headers

Long parameter names like “Chlorine Feed Pump Station 1 Total Pounds Used” clutter the month summary DataView. Use custom column headers (see that blog post) to shorten them: “Cl2 Pounds,” “Cl2 Cost,” “Alum Pounds,” “Alum Cost.” Keep headers concise so the 12-month grid fits on one screen or one printed page without scrolling or resizing.

Update and review monthly

Set a recurring task to open your chemical cost month summary DataView on the first of each month. Review the previous month’s totals, compare to budget targets, and check for unusual spikes or drops. Export the updated view to Excel or save a PDF snapshot for your records. Over time, you’ll build a historical archive of monthly chemical costs that supports long-term planning and capital improvement decisions.

Why this matters for plant management

Budget justification requires data, not guesses. When a council member asks, “Why did we spend $12,000 on polymer last quarter?” you can open your month summary DataView and show exactly how much was used each month, what the average daily dose was, and how that compares to the same quarter last year. When you need to forecast next year’s chemical budget, you have historical monthly totals to base your projections on. Month summary DataViews turn daily operational data into strategic management information.

Next Steps: Track operational costs with Operator10 →

The post Month Summary DataViews for Chemical Cost Tracking in Operator10 appeared first on AllMax Software.

Why allow partial receipts?

If a PO includes 10 different parts and only 7 arrive in the first shipment, you need those 7 in inventory immediately for work orders scheduled this week. The other 3 might arrive next week or next month. Partial receipts let you receive the 7 now, update inventory, and flag the remaining 3 as pending. This keeps inventory accurate and prevents holding up work waiting for complete orders.

How to record partial receipts

Open the purchase order in the Ordering section. Click Receive Parts. A receipt dialog appears showing all parts on the PO with fields for Quantity Expected and Quantity Received. If you’re receiving only some parts, enter quantities only for what arrived. Leave the rest at zero or blank. Enter the Date Received for the current shipment. Add an Employee (who received the shipment) and optional Invoice Number. Click Save. Antero adds the received quantities to inventory and marks those parts as partially received.

Track what’s still pending

After recording a partial receipt, the PO remains open with a status showing which parts are complete and which are pending. Return to the same PO next week when more parts arrive and record another partial receipt. Each receipt updates inventory and the PO status independently. The PO only closes (marked complete) when all parts are fully received—meaning quantity received equals quantity expected for every line item.

Add comments to explain delays

The Receive Parts dialog includes a comments field. Use it to note why receipts are partial: “Supplier backordered 3 units, expects delivery next Monday.” These comments appear in the PO history and help future users understand what happened. If a coworker asks “Why is this PO still open?” they read the comments and see “Partial receipt, 3 units pending backorder.” Context prevents confusion.

Multiple shipments, multiple receipts

A PO for 20 filters might arrive in three shipments: 10 today, 7 tomorrow, 3 next week. Record three separate partial receipts. First receipt: Quantity Received = 10, Date = today. Second receipt: Quantity Received = 7, Date = tomorrow. Third receipt: Quantity Received = 3, Date = next week. Antero tallies the total (10+7+3 = 20) and marks the PO complete after the third receipt. Inventory increases incrementally at each step.

Inventory updates immediately

Each partial receipt adjusts inventory in real-time. After receiving 10 filters, those 10 are available for work orders immediately. The remaining 10 expected filters don’t appear in inventory until you receive and record them. This accuracy is critical: if you show 20 filters in stock before receiving them all, work orders might consume parts that aren’t physically available, causing confusion and delays.

Close POs manually if orders are incomplete

Sometimes orders never fully arrive—supplier discontinues a part, you find an alternative, or you cancel the remaining items. If a PO has partial receipts but will never be complete, you can manually close it. Select the PO, click Close Order, and confirm. Antero marks it complete even though some quantities weren’t received. Add a comment explaining why (“Remaining 5 units cancelled, switched to alternative part”). This prevents old incomplete POs from cluttering the open orders list forever.

Track transaction history

Each partial receipt creates a transaction record in the Transactions section. View the full history to see all receipts for a PO: dates, quantities, employees, and invoice numbers. This audit trail is valuable for reconciling invoices against receipts or investigating discrepancies. If an invoice charges for 20 parts but you only received 17, the transaction history proves what you actually got.

Invoice matching with partial receipts

Suppliers often invoice when they ship, not when you receive. With partial receipts, you might receive an invoice for 20 parts but only have 15 in hand. Record the partial receipt for the 15 you have, note the invoice number in the comments, and hold payment until the remaining 5 arrive and are received. This matching process prevents paying for parts you haven’t yet received, protecting against supplier errors or shipment losses.

Partial receipts for large or expensive orders

Capital equipment orders with long lead times often arrive in stages: major components first, accessories later. Using partial receipts, you can put the major components into service while waiting for accessories. Inventory and cost tracking remain accurate at each stage. For expensive parts, this also helps with budget tracking—you can see exactly how much has been spent (received and invoiced) versus what’s still pending.

Why incremental receiving beats lump-sum updates

Waiting to receive entire orders before updating inventory creates multi-week gaps where inventory doesn’t reflect reality. Partial receipts keep inventory synchronized with physical stock daily, so operators see accurate quantities when planning work and supervisors make better reorder decisions based on current, not stale, data.

Next Steps: Manage Antero inventory with partial receipt tracking →

The post Partial Receipts in Antero: Record Parts as They Arrive appeared first on AllMax Software.

Why insert charts into custom reports?

Manual report assembly is tedious: export charts, open Word, paste images, resize them, add captions, check formatting, repeat next month. Insert charts into custom reports eliminates repetition by embedding charts in report templates. When you generate the report next month, Operator10 pulls fresh data and renders updated charts automatically. Same layout, new data, zero manual chart handling.

How to access custom reports

From the Operator10 main screen, go to Reports and look for Custom Reports or Report Designer (terminology varies by version). This opens the custom report interface where you can create new templates or edit existing ones. Custom reports use a programming-style interface (XML or similar markup), which may look intimidating initially but follows predictable patterns. AllMax Software provides support and templates to simplify this process.

Import charts into the report template

To embed a chart, you first need to import it as a data source. In the custom report designer, look for an Import or Insert > Data Graph option. This opens a dialog showing all saved charts in your Operator10 database. Select the chart(s) you want to include in the report. Operator10 adds them to the report’s data index, making them available for insertion into the template layout.

Insert data graph elements

After importing charts, place them in the report template using Insert > Data Graph commands. Position the cursor where you want the chart to appear (e.g., after the “Water Quality Trends” section header), insert the data graph placeholder, and configure its size and alignment. The report template now includes a reference to the chart. When you generate the report, Operator10 replaces the placeholder with the actual chart image rendered from current data.

Format chart size and position

Custom report templates let you specify chart dimensions and positioning. Set width and height to match your report layout (e.g., 6 inches wide by 4 inches tall for a full-width chart on a portrait page). Align charts left, center, or right. Add margins or spacing around the chart to prevent text from crowding it. These formatting settings persist in the template, so every generated report has consistent chart sizing and placement.

Combine multiple charts in one report

A typical monthly operations report might include 5-10 charts: influent flow trends, effluent BOD compliance, chemical usage, solids handling, and energy consumption. Import all relevant charts and insert them at appropriate sections of the report template. Each chart updates independently when the report generates, so you get a comprehensive visual summary of plant performance without manually exporting and pasting each one.

Add narrative sections around charts

Custom reports aren’t just charts—they include narrative text, tables, summaries, and analysis. Structure your template with section headers, introductory paragraphs, chart insertions, and follow-up commentary. For example: “Section 3: Effluent Quality Trends” → narrative intro → chart insert → bullet points summarizing key observations. The chart updates with fresh data each month, while narrative sections remain static (unless you edit them).

Generate the report monthly

After building the template, generating the report is simple. Open the custom report, set the date range for the current reporting period (e.g., January 1–31, 2025), and click Generate or Run Report. Operator10 queries the database, renders all charts with current data, populates tables, and assembles the complete report. Export the final report as PDF for distribution or print it directly for meetings.

Update charts in the template as needed

If you improve a chart over time—add constant lines, change palettes, adjust formulas—the updated chart automatically appears in future report generations. The template references the chart by name; when you regenerate the report, Operator10 pulls the latest version of that chart. This keeps reports current without manually updating template references every time you tweak a chart.

Templates reduce training time

New staff tasked with monthly reporting can generate professional reports immediately using pre-built templates. They don’t need to know how to create charts, format Word documents, or understand report structure—the template handles all of that. They just set the date range, click generate, and review the output. This speeds onboarding and ensures consistency even when different staff generate reports over time.

Use for regulatory submissions

Many regulatory reports require specific sections, charts, and data tables. Build a custom report template matching the regulator’s format requirements, insert required charts, and regenerate it each reporting period. The template ensures you never forget a required chart or section, and the automated generation reduces errors caused by manual copy-paste workflows. Submit PDFs generated directly from the template for fast, compliant reporting.

Why automation beats manual assembly

Manual report creation: 2-3 hours per month. Automated custom reports with inserted charts: 15 minutes per month to generate and review. Over a year, that’s 20-30 hours saved. More importantly, automated reports are consistent, error-free, and don’t suffer from “forgot to update Chart 3” issues that plague manual workflows.

Next Steps: Automate Operator10 reporting with custom report templates →

The post Insert Operator10 Charts into Custom Reports for Automated Reporting appeared first on AllMax Software.

Name things for users, not software

Pick discharge type names that match how your team talks: “Domestic” and “Industrial” are common anchors. If you need more, add specific categories you’ll actually use.

Capture addresses for hauler

Add addresses when you create haulers so billing reports print complete letters without manual edits. You only do it once, and you benefit every month.

Build a starter list of discharge accounts

Add high-volume pickup locations in advance. It shortens entry time and improves filtering later. You can still add new accounts on the fly as trucks show up.

Keep intake minimal but consistent

Record the core fields every time: date/time, hauler, discharge account, type, driver, receiving operator, and gallons. If pH and conductivity are part of your screening, enter them the same way for each load.

Use the right output for the audience

Need a quick status? Print the grid. Need a formal handoff? Run the received report with totals. Need invoices? Use billing reports per hauler and export to PDF.

Close the loop monthly

Put all hauler billing reports into a report set and run them together. You’ll cut clicks and reduce the risk of missing someone.

Result

With these habits, Operator10 septic hauling becomes a light-weight intake tool that still meets audit and billing needs—clean data in, clean reports out.



Next Steps: Want a walkthrough of the septic hauling feature in Operator10? →

The post Operator10 Septic Hauling Best Practices: Clean Data In, Clean Reports Out appeared first on AllMax Software.

Why filter when creating DataViews?

Large databases mean long lists. If your plant tracks 50 aeration basins, 20 clarifiers, 30 lab parameters, and 40 chemical feeds, the full location parameter list has 140+ entries. Finding “Influent Flow” at the top, then scrolling to “Effluent Flow” near the bottom, then scrolling back to “Aeration Basin 1 TSS” in the middle wastes time and increases the chance of missing a parameter or selecting the wrong one. Filtering location parameters shrinks the list to only what you’re looking for, so you build DataViews faster and more accurately.

How to filter location parameters

When creating a new DataView in Operator10, you’ll see a dialog box with a list of all available location parameters. At the top of that list, there’s a Filter text box. Click inside the box and type a keyword related to the parameters you want to include. As you type, the list updates in real time, showing only parameters that contain your keyword. For example, type “TSS” and the list shows only parameters with “TSS” in the name: Influent TSS, Effluent TSS, Aeration Basin 1 TSS, etc.

Use broad or specific filters

Start with broad keywords like “flow” or “TSS” to see all related parameters at once. If the filtered list is still too long, add a second keyword like “influent” or “basin” to narrow it further. For example, typing “TSS basin” shows only TSS parameters that include the word “basin” in their name, filtering out influent and effluent TSS. You can clear the filter at any time by deleting the text in the filter box, which restores the full list.

Filter by treatment stage

If you want to create a DataView focused on one treatment stage—like all aeration basin parameters or all clarifier parameters—type the stage name in the filter box. Typing “aeration” shows every parameter associated with aeration basins. Typing “clarifier” or “effluent” shows those groups. This is especially useful when building process-specific DataViews for operators who only work in certain areas of the plant.

Filter by parameter type

To create a lab-focused DataView, filter by parameter type: “BOD,” “TSS,” “ammonia,” “phosphorus.” The filtered list shows every location that tracks that parameter, so you can select influent BOD, effluent BOD, and any intermediate sample points in one pass. This is faster than scrolling through the full list trying to remember which locations track BOD.

Combine filtering with multi-select

After filtering, you can select multiple parameters at once using Ctrl+Click or Shift+Click. For example, filter by “TSS,” then hold Ctrl and click Influent TSS, Aeration Basin 1 TSS, Aeration Basin 2 TSS, and Effluent TSS. All four get added to your DataView. Clear the filter, type “flow,” and select all the flow parameters you need. This workflow lets you build a multi-parameter DataView in seconds instead of minutes.

Save time during setup

When setting up a new plant database or building DataViews for a new operator, filtering location parametersdramatically speeds up the process. Instead of explaining to the operator how to scroll and find parameters, just tell them to type the keyword and select what appears. New users can build their own custom DataViews without assistance, which reduces training time and increases adoption.

Keep parameter names filter-friendly

When naming location parameters in your database setup, include keywords that operators will naturally search for. Instead of naming a parameter “AB1-SS,” name it “Aeration Basin 1 Solids TSS” so it appears when filtering by “aeration,” “basin,” “solids,” or “TSS.” Descriptive names make filtering more effective, which makes DataView creation faster for everyone.

Why this feature matters

Small databases with 20-30 parameters don’t need filtering—the full list is manageable. But plants with 100+ parameters quickly become unwieldy. Filter location parameters turns a 10-minute DataView setup into a 2-minute setup, and it reduces errors by ensuring operators select the correct parameters instead of guessing from a long, confusing list.

Next Steps: Build better Operator10 DataViews for your team →

The post Filter Location Parameters When Creating Operator10 DataViews appeared first on AllMax Software.

Why use reorder parts flagging?

Manual inventory checks are time-consuming and error-prone. Walking the storeroom counting parts weekly doesn’t scale, and by the time you notice a shortage, you’ve already missed the reorder window. Reorder parts flaggingautomates this: set thresholds once, and Antero continuously monitors inventory. When a part drops below minimum, it flags automatically. No manual checks, no surprises.

Set minimum and maximum quantities

For each part in Antero, go to the Parts section and open the part details. Enter a Minimum Quantity (the lowest acceptable stock level before reorder) and Maximum Quantity (the target stock level after reorder). For example, a fuel filter might have Minimum: 5, Maximum: 20. These thresholds reflect your reorder point and order-up-to level, balancing carrying costs against stockout risk.

Red flag when below minimum

When a part’s current quantity drops below its minimum, Antero displays it with a red background or red text in the parts grid. This visual flag is immediate: open the parts list, scan for red, and you know which parts need attention. No sorting, no filtering—the red flag jumps out. This works even if you’re browsing parts for other reasons; you’ll spot low-stock items incidentally.

Reorder parts list consolidates flagged items

Instead of scrolling through hundreds of parts looking for red flags, go to Ordering > Reorder Parts. This dedicated view shows only parts currently below minimum quantity. The list includes part name, current quantity, minimum quantity, and maximum quantity. Everything you need to decide what to reorder is in one place. Click on a part to see additional details like supplier, last order date, or usage history.

Generate purchase orders from reorder list

The reorder parts list isn’t just informational—it’s actionable. Select parts from the list and click Create Purchase Order. Antero pre-populates the order with those parts and automatically calculates order quantities based on maximum values. If a part has 4 units in stock, a minimum of 5, and a maximum of 20, Antero suggests ordering 16 units (20 – 4 = 16). You can adjust the suggested quantity if needed, then submit the order to the supplier.

Prevent stockouts proactively

By checking the reorder parts list weekly or monthly (depending on usage rates), you catch shortages before they impact work orders. If a critical bearing is flagged with 2 units remaining and minimum is 3, you order more immediately. The bearing doesn’t reach zero, so the next pump maintenance job proceeds on schedule without delays. This proactive approach is the entire value of reorder parts flagging—preventing problems instead of reacting to them.

Adjust thresholds based on usage patterns

After using reorder parts flagging for a few months, review whether your minimum and maximum quantities are correct. If a part constantly flags for reorder but never actually runs out, the minimum might be too high—lower it to reduce excess inventory. If a part reaches zero before flagging, the minimum is too low—raise it to create more buffer. Antero helps you tune thresholds over time for optimal inventory levels.

Seasonal or project-based adjustments

Some parts have variable demand. Filters might get used more in summer (higher flows). Project-specific parts might spike during capital improvements. Temporarily adjust minimum quantities upward before high-demand periods to ensure reorder parts flagging triggers earlier, giving you more lead time to order. After the period ends, lower minimums back to normal to avoid overstocking.

Combine with vendor lead times

Set minimum quantities based on how long it takes to receive parts from suppliers. If a part takes 2 weeks to arrive and you use 5 per month, your minimum should be at least 3-4 (enough to last until the order arrives). Reorder parts flagging then triggers with enough time to order and receive before you run out. This alignment between reorder points and lead times is critical for effective inventory management.

Alert multiple users if needed

Larger organizations can have multiple people responsible for ordering. Make checking the reorder parts list part of a weekly routine—assign it to the storeroom manager, purchasing coordinator, or maintenance supervisor. Some plants set calendar reminders: “Every Monday at 9 AM, check reorder parts list and place orders.” This ensures someone consistently acts on the flags, so flagged parts don’t languish unordered.

Why automated flagging beats manual tracking

Manual inventory management means someone physically checks stock, notes shortages on paper or spreadsheets, and remembers to order. That person gets sick, goes on vacation, or gets busy, and parts run out. Reorder parts flaggingnever forgets, never takes vacation, and works 24/7. It’s the reliable backstop that ensures parts availability doesn’t depend on one person’s memory or diligence.

Next Steps: Set up proactive inventory management in Antero →

The post Reorder Parts Flagging in Antero: Auto-Identify Stockouts Before They Happen appeared first on AllMax Software.

Why print and email from Antero?

Manual PO communication means copying part numbers, quantities, and costs from Antero into a separate document template, then converting to PDF and attaching to an email. Each manual step risks typos, omissions, or version mismatches. Print and email purchase orders automates this: Antero formats the PO professionally, includes all required details, and sends it directly. Faster, cleaner, error-free.

Print purchase orders

Highlight the purchase order in the Ordering grid and click the Print icon. Select Print Purchase Order. Antero generates a PDF with all PO details: supplier name and address, PO number, date, itemized parts list (part name, description, item number, units, quantity, unit cost, total cost), estimated shipping and tax, and grand total. The PDF uses a professional template matching industry standards. Print it and mail it, or save the PDF to attach to emails or file in records.

Email purchase orders

Highlight the purchase order and click the Email icon. Antero generates the same PDF and opens your computer’s default email application (Outlook, Thunderbird, etc.) with the PDF pre-attached. The email recipient field auto-populates with the supplier’s email address (if stored in the supplier record). Add a subject line like “Purchase Order #1234” and any message text, then send. The supplier receives a professional PDF PO ready for processing without you touching Word or Acrobat.

Professional formatting included

Antero’s print and email purchase orders feature uses built-in templates that include standard PO formatting: company logo (if configured), supplier contact info, itemized line items with subtotals, shipping/billing addresses, tax calculations, and grand totals. Suppliers recognize this format immediately—it looks like every other PO they receive, making processing smooth on their end. No custom Word template building required.

Update supplier email addresses

For email purchase orders to work seamlessly, store supplier email addresses in the Suppliers section. Go to the supplier record, add their primary contact’s email under Contact Information, and save. Now when you email a PO, Antero auto-fills that address. If a supplier has multiple contacts (sales, support, accounting), add them all and choose the appropriate recipient when emailing. Some plants always email POs to suppliers’ accounting departments for invoice matching.

Review before sending

Both print and email functions generate a preview. Before printing or emailing, review the PDF to ensure accuracy: correct parts, quantities, pricing, and supplier details. If you spot an error, close the preview, edit the PO in Antero, and regenerate. This pre-send review catches mistakes before they reach suppliers, preventing rework and reorders due to incorrect POs.

Batch print multiple POs

If you created five purchase orders on Monday morning, you can batch print them. Highlight all five POs in the ordering grid (hold Ctrl and click each), then click Print. Antero generates PDFs for all five and sends them to the printer in one job or combines them into one multi-page PDF for digital filing. This saves time compared to printing each PO individually.

Email reduces paper and postage

Many suppliers prefer email POs for faster processing and easier record-keeping. Email purchase orders eliminates printing costs, envelope costs, and postage costs. It’s also faster: email reaches the supplier in minutes versus days for postal mail. For urgent orders, emailing is the only viable option. Some suppliers even automate email PO processing, extracting data directly from PDFs to generate invoices and shipment notifications.

Track sent POs

After emailing a PO, note the date and recipient in the PO notes field. Some plants add comments like “Emailed to [contact] on [date]” for tracking. If the supplier doesn’t respond within a day or two, you have a record of when you sent it and can follow up. This accountability is harder with manual email processes where POs get lost in sent folders.

Integrate with supplier portals

Some large suppliers use online portals where you upload POs or enter orders manually. In these cases, print and email purchase orders from Antero still serves as internal documentation. Generate the PDF, then copy part numbers and quantities from the PDF into the supplier’s portal. While not fully automated, it’s still faster than manually entering from Antero’s database into the portal line by line.

Why automation matters for purchasing

Creating 20 POs manually per month with manual formatting and emailing takes 3-4 hours. Print and email purchase orders reduces that to 30 minutes: create POs in Antero, batch email them, done. Over a year, that’s 30+ hours saved—time better spent negotiating prices, vetting new suppliers, or managing inventory strategically.

Next Steps: Streamline Antero purchasing workflows →

The post Print and Email Purchase Orders from Antero: Streamline Supplier Communication appeared first on AllMax Software.