AEON Communications
A command-and-control room at night, three operators at their consoles.

WHAT WE DO

AEON is engaged where the operation of a system must be decided — before it is developed, while it is developed, while it runs, and when it must be explained.

The four capabilities below are modes of engagement, not a service catalogue. Each is described by the condition that calls it, the judgment it carries, and what it leaves behind.

DISCLOSURE

AEON names the programmes it has worked on. What it does not publish is the work product itself — documents, reports, schedules, and meeting records stay with the client who commissioned them. Disclosure policy →

SYSTEM LIFECYCLE — WHERE AEON IS CALLED
BEFORE DEVELOPMENT 01 FUTURE CONCEPT
& ADVANCE UX Operation that does not yet exist IN DEVELOPMENT 02 SERVICE &
PRODUCT DESIGN Structure being fixed IN OPERATION 03 COMPLEX
SYSTEM UX Judgment under real load IN COMMUNICATION 04 TECHNOLOGY
COMMUNICATION What is fixed, made understandable
ACROSS ALL FOUR

Technical interpretation runs through every engagement. AEON reads the system's own documentation, argues the case with its engineers, and works in their terminology. It is a condition of the work rather than a service — and for that reason it is not indexed below.

CAPABILITY RECORDS
01

FUTURE CONCEPT & ADVANCE UX

BEFORE DEVELOPMENT
WHEN CALLED
An operation is proposed before the system that would carry it exists. No precedent settles how a person would work inside it, and the decision to commit to it has to be made anyway.
WHAT WE DECIDE
What remains the operator's role once part of the work is delegated to a non-human element. Where supervision is required and where it is not. Which of the proposed operations a person could actually sustain.
WHAT REMAINS
Operating concept · role allocation between human and autonomous elements · scenario set · evaluation criteria · working prototype
PROBLEM TYPES
REQUESTABLE AS
  • — Operating concept for a capability that has no precedent
  • — Role allocation between an operator and an autonomous element
  • — Working prototype for a concept still under funding review
  • — Feasibility review of a proposed operation, from the operator's side
01 — SELECTED WORK Future Battlefield UX/CX Consulting (Integrated Unmanned Systems) LIG D&A · 2025 · UX/CX Consulting Drones changed what a battlefield is before anyone had settled what to build for it. VIEW CASE →
02

SERVICE & PRODUCT DESIGN

IN DEVELOPMENT
WHEN CALLED
A system is being built, and the structure a person will work through has to be fixed before it hardens into code — across variants, regions and successive releases that must stay consistent with one another.
WHAT WE DECIDE
What the units of the interface are and what each one is called. Which rules hold across every variant and which are allowed to differ. What a later team must not change.
WHAT REMAINS
Service architecture · component and state definitions · design rules and guidelines · terminology system · continuity rules across releases
PROBLEM TYPES
REQUESTABLE AS
  • — Interface guideline system for a product line with multiple variants
  • — Component and state definition for a platform under development
  • — Terminology and labelling system across an entire product family
  • — Continuity rules for a system another team will extend
02 — SELECTED WORK GR-LIG Multi-Robot Control LIG D&A · 2026 · Service Design & UX Three different people in three different places, and one fleet of robots between them. VIEW CASE →
03

COMPLEX SYSTEM UX

IN OPERATION
WHEN CALLED
A system already in service produces more state than an operator can resolve in the time available, and the cost of a missed item is not symmetric with the cost of a false one.
WHAT WE DECIDE
What is shown and what is withheld. What escalates, and on whose authority. Where control passes between operator and automation, and what the operator must already know at the moment it passes.
WHAT REMAINS
Information architecture · state-transition rules · authority allocation · alert and escalation grammar · operator scenario set · procedure for the exception case
PROBLEM TYPES
REQUESTABLE AS
  • — Operator interface restructuring for an in-service system
  • — Alert and escalation grammar definition
  • — Authority allocation review for a partially automated function
  • — Console layout for an operator holding several tasks at once
  • — Recovery and exception procedure design
03 — SELECTED WORK M-SAM Block-III — Operations & Engagement Control Centre LIG D&A · 2026 · UX Design & Prototype This control centre has to work alongside another system's control centre. Designing one now means designing the seam. VIEW CASE →
04

TECHNOLOGY COMMUNICATION

IN COMMUNICATION
WHEN CALLED
A system is understood by the people who built it and by almost no one else, while the decision to fund, adopt or approve it sits with those others.
WHAT WE DECIDE
What has to be understood first and what can be left out. Which claims the audience will test, and what evidence must be visible at the moment they test it. What may not be simplified.
WHAT REMAINS
Technical narrative structure · figure and diagram conventions · briefing and exhibition systems · moving-image sequences · terminology consistent with the system's own documentation
PROBLEM TYPES
REQUESTABLE AS
  • — Technical narrative for an audience outside the development organization
  • — Exhibition or conference presentation system for a system under development
  • — Moving-image sequence explaining an operating concept
  • — Figure and diagram conventions for a document set
04 — SELECTED WORK Global Multi-Layered Air Defence System — Promotional Film LIG D&A · 2026 · Promotional Film Six layers, each with its own answer, and none of them meaning much alone. VIEW CASE →
COVERAGE — CAPABILITY × PROBLEM TYPE 2008—2026 · 19 YEARS RECORDED

AEON has worked this way since before the term for it existed. The index begins where the contract record begins, in 2008.

Capability × problem type. A cell value is the number of years active in that combination — not a count of projects.
 DETCLSPRIHNDMODSUPLODTRURECCOO
01 FUTURE CONCEPT & ADVANCE UX
02 SERVICE & PRODUCT DESIGN
03 COMPLEX SYSTEM UX
04 TECHNOLOGY COMMUNICATION
SUSTAINED  16—19 RECURRING  9—15 ENCOUNTERED  1—8 NOT ENGAGED
CONTINUITY — ACTIVE YEARS PER HALF
CAPABILITY 2008—2016 (9) 2017—2026 (10)  
01 FUTURE CONCEPT & ADVANCE UX810continuous
02 SERVICE & PRODUCT DESIGN99continuous
03 COMPLEX SYSTEM UX910continuous
04 TECHNOLOGY COMMUNICATION26formed recently
HOW OUR WORK CAN BE VERIFIED
01 / INDEXED

COVERAGE
INDEX

Nineteen years of engagements, resolved into the problem types they addressed. The programmes are named in Cases; this is their distribution.

↓ COVERAGE · 31 PROGRAMS · 2008—2026
02 / OPEN

METHOD
DEMONSTRATION

Work that may be disclosed, presented as method rather than outcome: condition → constraint → alternatives → structural decision → verification.

IN PREPARATION
03 / RULES

OPERATING
RULES

The rules by which AEON abstracts, publishes and withholds. A firm that manages restriction by written rule is the evidence.

→ ABOUT · DISCLOSURE POLICY

Most of AEON's work is restricted from public disclosure under client security policy. AEON observes those restrictions. We consider it a condition of working in this field.

WHAT CAN BE REQUESTED
  • — Operator interface restructuring for an in-service system
  • — Alert and escalation grammar definition
  • — Operating concept for a capability that has no precedent
  • — Role allocation between an operator and an autonomous element
  • — Interface guideline system for a product line with multiple variants
  • — Technical narrative for an audience outside the development organization