Fieldforce

AI on the record

Agents will change the work. The record remains.

Athena and the Fieldforce MCP connector put models and agents to work on the record, under the same identity, permissions and audit trail as every person who uses it.

01 · The principle

Three things make AI safe to use on infrastructure.

01

A complete record

So there is something true to act on. Sites, assets, leases, work orders and crews, with their history.

02

Inherited permissions

An agent can do no more than the person who invoked it. Identity passes through from single sign-on.

03

An audit trail

Every proposal, approval and action is attributable, with its source and its time.

Fieldforce provides all three, and the agents are built on top.

03 · Athena

Intelligence that inherits your controls.

Athena Insight

Live

Plain-language questions on the record, answered with tables, indicators and charts.

Which sites have work orders at risk this month?→ 14 sites · table · 3 over forecast by more than 10 daysIllustrative

Athena Hub

Live

Answers from your own documents: leases, permits, specifications and procedures, in the language of the user.

What is the escalation clause on PK-1182?→ 4% annually from 1 March · source: lease 2024-117, clause 6.2Illustrative

Athena Vision

Live

Reads field photographs: installed assets and serial numbers captured into the record; safety equipment checked on site.

Close-out set TX-0412 · 42 photographs→ 6 radios serialised · 1 unreadable · helmet and vest presentIllustrative

04 · The Fieldforce MCP connector

Let any assistant into the workflow. Keep the record in charge.

A hosted gateway that exposes governed Fieldforce workflows to enterprise AI assistants through the Model Context Protocol. Search, status, updates and approved write actions in natural language. Identity passes through from your single sign-on; every tool call runs the same validations as the web application and is logged.

In production with a customer since 2026 · Crusoe

fieldforce.mcpIllustrative
  1. user · via assistantStatus of Polar P1 shipments, and move the rack delivery to 4 November.
  2. fieldforce.mcp · identity: m.chen@customer · role: procurement leadPolar P1: 3 shipments in transit, 2 received, 0 delayed.
    Shipment SH-2231 (racks): proposed new date 4 November 2026. A justification is required before saving.
  3. userVendor confirmed slip; logistics hold at port.
  4. fieldforce.mcpSaved. SH-2231 date changed 28 Oct → 4 Nov · justification recorded · actor m.chen · 09:45:31 · audit entry 88213.

05 · Agent catalogue

Named by the job, labelled by what is true today.

AgentJobApproval pointStatus
InsightAnswers questions on the record with tables and chartsNone required; read-onlyLive
Close-out reviewChecks close-out photographs for installed assets, serials and safety equipment; returns a deficiency listProject manager accepts the listLive
Lease and permitAbstracts leases and permits, flags escalations and expiries, drafts renewalsSite or lease manager approvesLive
Procurement trackerFollows requisition, purchase order, shipment and receipt to asset readiness; raises exceptionsProcurement lead approves date changesLive
Schedule-risk watcherFlags tasks and work orders likely to miss forecast; projects finish datesAdvisoryPlanned
Inventory reconciliationReconciles warehouse, truck and site inventory to the fixed asset registerFinance approves adjustmentsPlanned
Tenant revenue assuranceMatches equipment recorded on site to tenant charges; flags unbilled equipmentCommercial team approvesPlanned
DispatchProposes crew assignment by skill, location and scheduleSupervisor confirmsPlanned

Live agents are available to customers today. Planned agents are on the roadmap and are not sold.

06 · Trust

  • Answers cite the record they came from.
  • Agents inherit the permissions of the user who invoked them.
  • Nothing is written without sign-off. Autonomy is set per workflow.
  • Customer data does not train third-party models.