ARCHAI®Electronics Inc./ PRODUCTS / AETHERONE™ / AetherDispatch™← ALL PRODUCT SYSTEMSDISCUSS A PROJECT ↗
AetherONE™AetherDispatch™Work-order dispatch
Utility field work: work orders, crews, contractors, field evidence and completion.
PRODUCT OVERVIEW
Carry a meter job through its field evidence.
AetherDispatch is AetherONE’s utility field-work and contractor component for meter installation and replacement. It owns the Work Order, planning, assignment, field package, evidence, exceptions, QA, reopening and revisit workflow.
This is utility field work, not grid, SCADA or OMS dispatch. The current browser evaluation offers dispatcher, field-app and contractor views on deterministic synthetic data.
Who it is for
- Field-operations managers and dispatchers
- Crew leads, technicians and contractor supervisors
- Field QA reviewers and integration architects
Responsibilities and evaluation scope
- Intake
- Approved design scopeValidate work and its CIS request reference before a Work Order; manual work-order creation is in the design.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- Meter work orders
- Approved design scopeWork type, priority, territory, due time, crew, skills and service-request/metering-point/site references; list, board, 360 and wizard.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- Planning and assignment
- Approved design scopeMatch crews/contractors to skills, territory and calendar; review appointments, constraints and a schematic map.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- Crews and qualifications
- Approved design scopeTechnicians, vehicles, contractor eligibility/capacity, skills and certification requirements.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- Materials and tools
- Approved design scopeRead-only projection of job reservations.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- Field work package
- Approved design scopeAccept/reject/clarify, route, checklist, serial matching, site confirmation, photos/readings/seals, exceptions and completion.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- Offline and sync
- Approved design scopeDistinguish locally queued work, conflict and server acknowledgement; the shown rows are synthetic.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- QA and revisit
- Approved design scopeEvidence review, correction, reopening, revisit and escalation with searchable evidence.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- Contractor portal
- Approved design scopeAssignments, capacity, QA corrections and read-only Revenue settlement references.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
- Analytics and configuration
- Approved design scopeService-level, first-time-fix and contractor views; work/checklist templates, territory, policy and optimizer settings.
- Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
How the work connects
The original diagrams and interface excerpts below are in English. The surrounding description explains their scope in the page language.
Clear responsibility across products
- AetherCIS / AetherMDMS
- CIS owns the originating Service Request. Dispatch owns the Work Order. MDMS alone commits the validated, effective-dated installation and measurement continuity. Service Point and Metering Point remain distinct.
- AetherGIS / AetherRevenue
- GIS owns addresses, coordinates and topology; Dispatch consumes site/route projections. Revenue owns contractor settlement, shown read-only in the portal.
- Work-order contracts
- dispatch.work-order.created.v1 and dispatch.work-order.status-changed.v1 are schema 1.0.0 design contracts, not a deployed transition engine. This edition neither produces nor receives the events.
Utility scenarios
A new connection by an in-house crew
Review service-request, metering-point and site references, then match skills, territory and due time before the planned field visit.
A contractor meter replacement
Review capacity and assignment, return QA photo corrections to the contractor and retain read-only settlement context from Revenue.
An exception at the door
No access, unsafe conditions or missing parts return a reason to the dispatcher. A failed QA review may reopen the job and require a revisit.
Evaluation views · synthetic data
The original diagrams and interface excerpts below are in English. The surrounding description explains their scope in the page language.
Edition and evaluation conditions
Three evaluation surfaces use deterministic demonstration data and open without live records. Action controls explain the required integration and do not execute jobs.
Optimizer runs, scanning/camera/NFC, positioning, signatures, persistent offline storage, resumable upload and contractor payment are not established. Map positions, acknowledgements and percentages are synthetic.
An operational deployment needs a Dispatch backend, authentication/authorization, private persistent store, field-device software and approved CIS/MDMS/GIS/Revenue contracts. No device support, certification, capacity, service level or customer outcome is claimed.
Document edition 2026.10 identifies the supplied documents, not a commercial release or a deployed version.
Product documents
Choose a language to download the matching document edition.
- AetherDispatch Datasheet · English (PDF)English · PDFDocument edition 2026.10
- AetherDispatch Catalogue · English (PDF)English · PDFDocument edition 2026.10