AMVUE Energy Systems, Inc.AMVUE is pronounced “AM-view”
Start a conversation
← Back to home

AMVUE FIELD COPILOT • CONTROLLED PROOF

Intelligence at thepoint of work.

Field Copilot is AMVUE’s planned field-intelligence system: a phone-first software foundation with an AI smart-glasses interface, source-grounded knowledge, project evidence and one-touch access to qualified human support.

Discuss a pilotExplore the full capability ↓
CURRENT STATUS90-day proof inquiries open • Device and workflow availability subject to review
FIELD COPILOT / CONCEPTAMVUE / 02
TWO INTERACTION MODESWorker questions + bounded proactive prompts
02SHARED INTELLIGENT CORETask state, safety, knowledge and visual context
03AUTHORITY BOUNDARYQualified people retain decisions and STOP/HOLD control
Concept visualization — product design may change
01TWO INTERACTION MODESWorker questions + bounded proactive prompts
02SHARED INTELLIGENT CORETask state, safety, knowledge and visual context
03AUTHORITY BOUNDARYQualified people retain decisions and STOP/HOLD control
01

MORE THAN A PAIR OF GLASSES

The wearable is one interface to a controlled field system.

The planned glasses make information accessible without forcing a worker to leave the task. The phone provides edge processing and connectivity. The backend organizes project context, approved knowledge and evidence. A remote Journeyman or Master-level workstation supports human escalation.

The product is not intended to watch unrestricted video continuously or give autonomous approval. It is designed to capture the right context, retrieve the right approved source, apply authorization gates and escalate uncertainty.

PLANNED PRODUCT CAPABILITIES

What Field Copilot is being designed to do

Capabilities will be released only after technical, safety and field validation.

01

Nameplate & equipment capture

Bring equipment identity, labels and relevant field context into the project record for review.

  • Key-frame capture
  • Candidate extraction
  • Human confirmation
02

Drawing and document check

Compare observed conditions with project-approved drawings, OEM material and available instructions.

  • Project-source priority
  • Applicability metadata
  • Mismatch escalation
03

Step guidance with gates

Present concise, role-aware guidance tied to the current task step and authorization state.

  • Task-state awareness
  • Permission checks
  • STOP/HOLD gates
04

Evidence log

Preserve photos, voice notes, decisions, model versions and changes as a traceable project record.

  • Timestamped context
  • Source and version
  • Follow-up queue
05

Remote expert connection

Transfer the worker’s question, current step, visual context and evidence to a qualified human reviewer.

  • One-touch escalation
  • Complete context package
  • Human takeover
06

Source-grounded field knowledge

Prioritize project-approved documents, AHJ and utility requirements, regulations, OEM material and approved procedures.

  • Traceable answer
  • Applicability check
  • Confidence and authority label

TWO MODES, ONE SAFETY CORE

Passive questions and bounded proactive guidance

Both modes use the same task state, authorization rules, traceable sources and escalation controls.

01

Worker-initiated question

Wake word, button or voice question with selected visual and project context.

02

Context and source assembly

Worker role, project, task step, authorization state and approved evidence are combined.

03

Bounded proactive event

A repeated, high-confidence scene signal can create a record, reminder, confirmation or HOLD request.

04

Answer or human escalation

Return concise guidance with source and boundary—or transfer the full context to a qualified person.

SYSTEM ARCHITECTURE

Four connected product layers

01

AI glasses

Hands-accessible voice, display and selected field capture interface.

02

Phone edge hub

Local task state, cached knowledge, connectivity and common bounded checks.

03

AMVUE knowledge core

Project context, approved retrieval, authorization logic and evidence records.

04

Expert workstation

Qualified human review, collaboration, decisions and knowledge improvement.

OPERATING BOUNDARY

Field Copilot supports work; it does not authorize work.

The system cannot independently confirm absence of voltage, authorize LOTO, energized work, energization, final PPE or code conclusions. STOP/HOLD rules, qualified-person review and project-specific authority remain controlling. The architecture described here is a product direction, not proof of released functionality.

NEXT STEP

Interested in a controlled Field Copilot pilot?

Contractors may introduce a use case, workforce profile and proposed low-risk validation environment.

Discuss a pilot← Back to home