Enterprise Smart Glasses for Field Service, Remote Expert and Industrial Workflows
Plan field-service smart glasses around work orders, capture or remote-expert interfaces, customer software, site constraints and acceptance evidence for the selected configuration.
Historical face-recognition and vehicle-traffic-recognition project experience; new regional review required
For established brands, channel partners and enterprise teams with a credible deployment or route-to-market plan. Begin with your contact details, company, platform and purpose: standard SDK access, a paid sample evaluation, standard-platform branding or custom development. A business owner can lead standard procurement; custom development also needs a technical owner and development budget. Evaluation, engineering, tooling and optional source licensing are quoted separately where applicable.
Industrial smart glasses start with a measurable workflow.
Define the job, the working environment and the evidence that would justify deployment. Camera access, readable guidance, connectivity and support must work together on the selected configuration.
Inspection
Associate required images, observations and timestamps with the correct asset and work order. Evaluate usable evidence, missing steps, upload confirmation and supervisor review. The customer defines inspection criteria and acceptance authority.
Remote assistance
Verify the actual live audio/video interfaces, service compatibility and network path before the pilot. Measure whether the expert can understand the task, how sessions reconnect and how workers escalate when the link fails.
Work instructions
Test readable prompts, step confirmation and record synchronization in the intended environment. Define task completion, operator errors, interruption recovery and how approved instructions are versioned.
Agree measurable targets and a comparison method with the site team; no deployment return, full-shift runtime or PPE approval is implied by these workflows.
Follow one work order from assignment to closure
Assign the taskThe customer system identifies the worker, site and work order. Confirm the App, login and any device-management requirements.
Guide and captureSpecify prompts, photos, audio or video evidence. Review trigger, capture, transfer and display interfaces separately for the chosen build.
Escalate when neededIf remote expert support is required, define the live-video/audio path, conferencing service and reconnection behavior as a separate integration.
Close with evidenceThe customer system associates records with the work order. Define upload confirmation, access, retention and supervisor acceptance.
Select a configuration that matches the actual task
K900: capture-led evaluation
K900 is a mass-production camera-glasses platform. Confirm the selected SDK's capture and transfer scope. A local video file, preview and continuous stream are different interfaces; specified partner streaming configurations do not make a remote-expert integration standard.
C100: Android and display prototype
C100 is at EVT3 with CNC functional prototypes. Evaluate an Android workflow, camera and display with direct Wi-Fi or the BLE phone-app path described below. Model inference runs off-device. Workload, heat, runtime, site networking and future production readiness need validation.
Industrial or historical requirements
Hands-free use does not establish PPE compatibility, hazardous-location approval, industrial protection or suitability for a safety-critical task. Falcon 007 Pro is a historical reference without evaluation samples; similar functions require a separately scoped ODM project.
Name the enterprise integration owner
The customer or system integrator owns work-order integration, user accounts, enterprise network access, remote-expert service, record retention and worker support. SmartXY identifies the platform interfaces and any commissioned firmware/App work. Confirm SDK versions, permissions, data formats, capture timestamps, transfer acknowledgments and available device-management controls.
For streaming, agree transport, audio, session length, network conditions and third-party compatibility; no protocol or API is implied by this page. Review privacy controls and site deployment requirements with the responsible customer team. Manufacturing traceability records and any ERP/MES integration must also be specified and confirmed per project.
Accept the pilot on evidence from the target site
Fill task-completion criteria, required image/audio quality, upload success, remote-expert delay if applicable, reconnect behavior and work-order record integrity. Test the expected wearing duration, charging plan, network dead zones, gloves/PPE fit and escalation procedure on the named build. Targets and results remain project-specific and unfilled.
Task and environment: task-success criteria, wearing duration, PPE compatibility and continuous camera/display/network workload.
Integration and data: enterprise-system owner, data access and retention, upload acknowledgment and disconnect/recovery behaviour.
Operations: worker training, charging, failure escalation, repair or replacement process and the named acceptance owner.
The customer site owner approves task safety and deployment conditions; the software owner verifies its integrations; SmartXY provides evidence for contracted platform deliverables. Record open defects and authorized acceptance before agreeing rollout. Include site conditions, platform, software stack, required interfaces, pilot volume and acceptance owners in the RFQ; review the blank gate checklist and cost responsibilities.
For a connected live AI agent with Android apps running on the glasses, evaluate C100, an EVT3 standalone Android edge-client project with camera and dual-eye display, available as CNC functional prototypes. Customized exterior design and further validation define the path toward production. Android apps run on the glasses. C100 supports direct Wi-Fi and BLE phone-app modes. In direct Wi-Fi mode, its own dual-band Wi-Fi reaches cloud or private AI services through home or office Wi-Fi, a phone hotspot, or a compatible public Wi-Fi network. A phone is not required as the runtime gateway when using a compatible router; using a phone hotspot still depends on that phone, and public Wi-Fi login compatibility requires validation. In BLE phone-app mode, image/audio from the glasses travels over BLE to the phone app and onward to VLM/LLM/cloud services; results return through the phone app and BLE to the glasses for audio playback and display. BLE phone-app mode requires the phone and its network connection. LLM/VLM inference runs off-device. Contact SmartXY to request the C100 SDK software development kit. C100 Android SDK/Demo availability and paid development policy.
RFQ checklist
Map your workflow, software stack, privacy constraints and pilot volume. Falcon 007 Pro is a historical project reference, not an overseas-ready product, and no test samples are available. Similar applications require a new ODM project with NRE, development time and project budget, agreed by scope. Discuss a new field-operation ODM project.
For faster feasibility review, include target market, ID direction, optical or audio route, certification region, app/SDK needs, estimated volume and launch timing.
Related reference architecture · ODM scoping
Embodied AI Data Capture Glasses
XY-DC Reference Architecture is a proposed display-free reference architecture for robotics and embodied-AI data collection. It is scoped as an ODM evaluation, not an additional product SKU.
Falcon 007 Pro context: A historical field-operation project reference, not an overseas-ready product or a source of evaluation samples. Similar first-person capture and external-power requirements need a new ODM project with NRE, development time and project budget; transfer to a new capture architecture requires review.
Stereo capture, synchronization, calibration and capture-point provenance require separate feasibility and project validation. These requirements must not be inferred from existing platform specifications.