One Operating Record for Dealership Operations
F2 Core connects environmental workflows, energy signals, facility execution, connected hardware, and spend control into a single dealership operating record — so action and evidence are never separated.
Dealer-led motion
Software-first, partner-aware
Audit-ready evidence
Role-based shared record
Four operating lanes. One operating record.
Facility Ops, Environmental, Energy & Connected Hardware, and SpendGuard are the lanes a dealership actually runs on. F2 Core connects them into one shared operating record so signals from one lane create action in another — and the evidence stays with the work.
Connected hardware is the signal layer — not a peer lane. AFMS, EO3, compressor and dryer controllers, Lift Connect Pro, and device health all feed Energy & Connected Hardware, Environmental, and Facility Ops.
Start with the lane that hurts most. Expand from there without rebuilding the record.
Facility Ops — tickets, RFQs, approvals, vendor follow-through
Environmental — SPCC, AFMS used-oil control, waste pickups, evidence
Energy & Connected Hardware — HVAC, compressed air, current sensing, runtime, device health
SpendGuard — invoice intelligence, credits, scorecards
Connected site signals feed every lane

Four lanes that share one record
Each lane is built for the way dealership teams actually run that part of the operation. They share the same operating record, so signals, actions, and evidence stay connected. Connected hardware is the signal layer, not a separate lane.
Facility Operations
Tickets, work orders, RFQs, approvals, invoices, and vendors — without the follow-up chaos.
Multi-vendor RFQ
Approvals with full context
Invoices tied to work
Environmental Operations
SPCC, AFMS used-oil control, waste pickups, labels, and audit evidence — software-first, partner-aware.
SPCC tank inventory
Used-oil control (AFMS)
Audit-ready evidence
Energy & Connected Hardware
HVAC, compressed air, dryer logic, current sensing, runtime analytics, and device health — the signal layer that turns hardware into workflow action.
Pelican HVAC
Compressor & Dryer Logic
EO3 + Device Health
SpendGuard
Match invoices to contracts, RFQs, work orders, pickups, credits, and evidence — stop spend leakage before it becomes routine. Human-reviewed exceptions; no autonomous payment.
Invoice intelligence
Used-oil credit recovery
Vendor scorecards
Signal → Action → Evidence.
Every lane shares the same operating model. A signal — a tank threshold, an HVAC exception, an invoice mismatch — is captured. The right action is routed: a ticket, a work order, a vendor request, an approval, with policy and ownership applied. The evidence — photos, signatures, documents, manifests, source-cited data — stays on the record so audit support and reporting are a side effect of normal work.
Routing carries context — site, asset, vendor, approver
Approvals stop the right work, not all the work
Vendor coordination keeps requests, schedules, and proof in one record
Audit-ready evidence is captured in the workflow, not after the fact

Role-based views. One shared record.
Corporate leadership, regional managers, service teams, finance/AP, compliance/EHS, and partners each see what they need to act — but everyone is acting on the same record. Shared accountability replaces email forwarding and spreadsheet handoff.
Corporate sees portfolio status and exception queues
Service teams see today's work and what is blocking it
Finance/AP sees invoice exceptions tied to actual work
Compliance/EHS sees readiness, evidence, and inspections
Partners and vendors see only the requests they own

Pick the entry point that matches your role.
Buyers come in from different angles. Each entry point lands you on the part of the platform that maps to your day.
Corporate / Multi-rooftop leadership
Portfolio visibility, exception queues, and approvals across all sites.
See Portfolio DashboardService / Fixed Ops Manager
Daily operations: tickets, vendor follow-through, and audit-ready closeout.
See Facility OpsCompliance / EHS
SPCC readiness, waste vendor proof, and evidence captured during workflow.
See EnvironmentalReady to see the dealership operating record in motion?
Walk through F2 Core with an example dealership scenario.
