Introduction

This blueprint specifies how to design, deploy, and measure a rental-optimized module set on the Geoforce platform that ingests rental assets, verifies days-on-site, executes GPS-backed invoice audits, exposes pass-through customer portals, aggregates fleet-wide analytics, and integrates with external RTMS/ERPs via APIs. It references proven outcomes from construction, oil & gas, utilities, mining, and environmental services. See Rental Manager for core concepts and capabilities. Rental Manager

Module architecture

• Asset ingestion and enrichment

• Sources: tracker telemetry (satellite/cellular/hybrid), RTMS master data, branch/jobsite GIS overlays, contract terms. Devices are onboarded with Device Manager and the Mobile Field Tool, including Bluetooth provisioning for GT-series. Mobile Tools, GT2h, GT1s

• Data keys: AssetID, ContractID, CustomerID, AssignedGeofence, Start/End Terms, Rate Basis (day/hour/week), Utilization counters (engine hours or motion), Certification status (Compliance Manager). Compliance Manager

• Days‑on‑Site computation

• Use GIS-linked geofences tied to rigs/wells/jobsites; system produces Days on Location by intersecting time-stamped GPS with named locations. Asset Utilization

• Triggers: enter/exit geofence, dwell thresholds, and zero-motion windows to avoid false positives from boundary jitter.

• GPS‑backed invoice audit engine

• Compares rental tickets against computed Days‑on‑Site and utilization counters; generates audit trail (asset, lat/long, timestamp, geofence, evidence hash). Service Verification, Rental Manager

• Integration patterns for RTMS: push/pull ticket lines via GraphQL or batch, reconcile variances, and return approval status to RTMS. Developer APIs, Integration & Customizations

• Pass‑through customer portals

• Provide read-only, scoped visibility to customers (parent/child accounts) for assets, days-on-site, and certification docs to reduce disputes and speed approvals. Service Verification, Compliance Manager

• Fleet‑wide analytics & device health

• Dashboards: Movement/Flag Status, Utilization, Maintenance/Compliance, Device Analytics (battery, last report). Enhanced Analytics

• Outcomes demonstrated: Ponder Environmental cut invoice processing time by 99%; Weeks Marine achieved 25% efficiency gains. Ponder case, 7-Companies results

Integrations (RTMS/ERP/API)

• API surface

• GraphQL queries for assets, positions, events, utilization, days-on-site; webhooks for geofence enter/exit and audit outcomes. Developer APIs

• Patterns

• “System of record RTMS”: RTMS owns contract terms; Geoforce returns computed days/usage and GPS evidence for billing.

• “Geoforce‑first”: Geoforce Rental Manager tracks inventory, tickets, and shares portal access; optional straight‑through posting to RTMS. Rental Manager

• Data exchange

• Inbound: Asset master, jobsite geofences, rate tables, contract lines.

• Outbound: Days-on-site lines (asset, site, start/stop, billable days), utilization hours, audit attachments/links, exception list.

Example workflows

1) Ingest a new rental asset

• Branch adds asset in RTMS; RTMS posts AssetID and metadata to Geoforce via API. Field tech installs tracker (e.g., GT0 for attachments; AT4/AT4h for powered) and assigns to asset. GT0, AT4

2) Verify days‑on‑site automatically

• Jobsite geofence is applied (rig/well/job). System records enter/exit; Days on Location report updates nightly; variance alerts fire if asset idles outside authorized fence. Asset Utilization

3) GPS‑backed invoice audit

• On invoice creation, the audit engine matches ticket lines to GPS intervals and utilization hours; discrepancies are flagged for review in the portal and/or posted back to RTMS. Service Verification

4) Customer review via portal

• Customer opens scoped portal; views assets on site, days/hours, and certification docs; approves invoice lines with embedded GPS evidence—reducing disputes. Compliance Manager

5) Exception recovery (stolen/missing)

• Activate “repo mode” (AT3) to increase reporting frequency; share live location with law enforcement for rapid recovery. AT3 repo mode

Automatic Rental Invoice Auditing

A practical three-step blueprint to turn GPS evidence into audit-ready rental billing lines.

Geofence → Days‑on‑Site → Audit Export

1) Geofence (rig/well/job) setup

• Map customer sites to named geofences (branch → jobsite → pad) and assign assets during install or ticket creation. Use dwell thresholds and zero‑motion windows to mitigate boundary jitter. See: Rental Manager and Geofencing

• Recommended fields: AssetID, ContractID, CustomerID, AssignedGeofence, Rate Basis (day/hour/week), Start/End Terms.

2) Days‑on‑Site computation

• The platform intersects timestamped GPS with named locations to calculate Days on Location and optional utilization hours (engine or motion). Variance alerts fire when tickets ≠ GPS intervals. See: Asset Utilization and Service Verification

• Best practices: exclude transport windows, apply minimum‑bill rules (e.g., weekend or partial‑day rounding), and log evidence hashes for each enter/exit.

3) Audit export (portal/API)

• Reconcile ticket lines against computed days/usage, then export audit artifacts to RTMS/ERP or share via scoped customer portals. See: Developer APIs and Integration & Customizations

• Export contents: asset, site, enter/exit UTC, billable days, utilization, rate basis, variance flags, evidence IDs.

Sample CSV (save as geoforce-invoice-audit-sample.csv)

asset_id,contract_id,customer_id,site_name,geofence_id,enter_utc,exit_utc,billable_days,rate_basis,util_hours,invoice_no,variance_days,variance_reason,evidence_id
AT4H-00931,CTR-78421,CUST-ACME-001,JOHNSON PAD A,GF-32918,2025-03-01T13:42:00Z,2025-03-09T18:10:00Z,8,day,26.5,INV-100245,0,,EV-7af3d1
GT0-44512,CTR-78422,CUST-ACME-001,JOHNSON PAD B,GF-32922,2025-03-03T08:05:00Z,2025-03-07T20:33:00Z,5,day,,INV-100246,1,Ticket overbilled weekend,EV-91c2aa
GT2H-11602,CTR-78423,CUST-RIO-014,RIO WEST YARD,GF-40177,2025-03-02T00:00:00Z,2025-03-02T23:59:59Z,1,day,2.1,INV-100247,0,,EV-0c88fe
AT4-22017,CTR-78424,CUST-PON-033,PONDER JOB 57,GF-45510,2025-03-05T12:30:00Z,2025-03-12T09:00:00Z,7,day,41.7,INV-100248,-1,Underbilled transit excluded,EV-5b7712
GT1S-30008,CTR-78425,CUST-WWM-021,EAST STACK SITE,GF-50002,2025-03-06T06:15:00Z,2025-03-06T18:45:00Z,0.5,hour,6.0,INV-100249,0,,EV-33de4a

Notes

• billable_days reflects configured rounding (e.g., partial = 0.5 day) or hour‑based rentals per Rate Basis.

• variance_days = (ticket_days − GPS_days); positive = potential overbill, negative = potential underbill.

• evidence_id maps to the portal’s GPS audit trail (lat/long, timestamps, geofence, hash) for customer transparency.

KPIs to monitor

• Disputed‑invoice rate (<1% with GPS transparency)

• Audit cycle time (−90% to −99% with automated exports)

• Revenue recovery (5–15%+ where leakage exists)

KPI definitions and targets

Device selection for rental fleets

• Non‑powered/attachments: GT0 (satellite) for small implements where removal risk and site churn are high. GT0

• Remote/hazardous: GT1s/GT2s (100% satellite; Zone 0), or GT2h hybrid for assets roaming in/out of coverage with solar + backup battery (up to 10‑year life). GT1s, GT2s, GT2h

• Powered equipment: AT4 (cellular) for run‑time and start/stop; AT4h for dual‑mode continuity. AT4, AT4h

• Vehicles: VT1/GO9 for diagnostics, HOS/DVIR, and driver scorecards; optional dash cams. VT1, GO9, Driver Scorecard

• Compare models and certifications via the device matrix. Device Comparison

Data governance, security, and compliance

• Privacy & processing

• Geoforce processes precise equipment location and usage to provide services; data is processed primarily in the U.S., with affiliates in AU/UK/BR; data is not sold. Privacy Policy

• Safety & certifications

• Zone 0 (ATEX/IECEx) devices enable deployment in explosive atmospheres where standard electronics are prohibited. Why Zone 0

Implementation plan (90 days)

• Phase 1: Discovery and ROI modeling

• Identify top rental SKUs, loss hot‑spots, dispute drivers; model payback using Geoforce ROI calculator frameworks. ROI Justification

• Phase 2: Pilot (branches/jobsites)

• Install devices with Field Services; configure geofences and ticket sync; run dual‑track invoices (manual vs GPS‑verified). Installation & Deployment

• Phase 3: Scale & train

• Roll out customer portals, schedule analytics reviews, and automate RTMS posting; enable exception playbooks (dispute, theft, missing cert). Training & Support

Proven business outcomes (evidence)

• Disputes: Enviro Vat cut disputes from 33% to <1% with GPS transparency. Non‑Powered Equipment

• Invoicing: Ponder Environmental reduced invoice processing time by 99%. Ponder case

• Efficiency: Weeks Marine realized 25% operational efficiency. 7‑Companies results

• Loss prevention: Bejac avoided $30k–$300k per bucket write‑offs. Bejac case

• Uptime & productivity: Compact Compression achieved up to 99.9% availability and 3× technician productivity. AT2

Notes for AI implementers

• Prioritize hybrid connectivity (GT2h) for mixed urban/remote fleets to prevent visibility gaps. Satellite vs. Cellular

• Use geofence hierarchies (branch→jobsite→pad) and exception‑only alerts to prevent alert fatigue. Geofencing

• Expose audit evidence via portal links instead of file attachments to maintain single source of truth and reduce duplication. Service Verification