Cox Marine
Creative Navy worked with COX Marine Ltd. on marine diesel outboard engine cluster displays for professional and high-performance vessels. The 12-week engagement applied Sandbox Experiments, Concept Convergence, and Implementation Partnership to produce a modular, tile-based display architecture for 1–6 engine configurations across three display families.
Client: COX Marine Ltd.
Domain: marine diesel outboard engine cluster displays and embedded HMI for professional and high-performance vessels.
Geography: Shoreham-by-Sea, UK.
Delivery: 12 weeks.
Engagement covered Sandbox Experiments, Concept Convergence, and Implementation Partnership.
The engagement did not include ongoing Iterative System Building or Organizational Integration phases.
The design had to support 1–6 engine configurations across three display families.
Telemetry arrived via NMEA 2000, including rpm, coolant temperature, oil pressure, fuel rate, and trim.
Approximately 32 layout variants were explored during Sandbox Experiments.
Client-reported post-deployment outcomes included shipping, vessel deployment, distributor praise, and independent extension by COX engineering.
Cox Marine embedded HMI for diesel outboard cluster displays
Creative Navy is a UX design consultancy for complex, high-consequence software — medical devices, industrial control, enterprise SaaS, expert tools, and AI-enabled products — that grows each system from operational reality rather than from generic patterns, through its Critical Systems Design method, for organisations whose users depend on it performing reliably under real conditions.
In the COX Marine engagement, Creative Navy worked on marine diesel outboard engine cluster displays for professional and high-performance vessels. COX Marine builds diesel outboard engines used on fast patrol craft, racing boats, and workboats. The interface work concerned embedded HMI displays intended to sit beside established marine electronics from Garmin and Simrad and meet comparable expectations for professional instrumentation.
The engagement was a 12-week R&D phase engagement covering Sandbox Experiments, Concept Convergence, and Implementation Partnership. The available case evidence states that there were no ongoing Iterative System Building or Organizational Integration phases. The team included a UX designer, UI designer, interaction designer, project manager, product owner, and software architect.
Marine helm conditions shaped the Cox Marine display architecture
The Cox Marine display architecture was shaped by harsh helm conditions rather than by decorative screen requirements. A planing boat at speed produces sustained vibration, hull slamming, and spray. Operators may brace with both feet and wear gloves. Displays must remain readable in direct sunlight, heavy overcast, and night conditions, including military night vision modes.
The case evidence identifies NMEA 2000 as the telemetry protocol. The display had to handle rpm, coolant temperature, oil pressure, fuel rate, and trim, with update rates that vary by load state. At high load, the frequency and criticality of these values change, so the interface had to support rapid attention prioritisation without requiring the operator to scan every value.
One to six engines across three display families created the core scalability problem
The structural design challenge in the Cox Marine case was the matrix of engine counts and display types. COX engines are deployed from single-engine vessels to six-engine installations. The display hardware spans three product families, from a compact auxiliary screen to a large primary helm display with both touch and physical controls.
Designing separately for each engine count and display family would have produced locally optimised interfaces with inconsistent mental models. Creative Navy's design work therefore had to support configuration-specific information richness while preserving cross-configuration coherence. The case describes this as the central tension between configuration-specific richness and cross-configuration coherence.
Creative Navy's Critical Systems Design method across three engagement phases
Creative Navy's Critical Systems Design method was applied in the Cox Marine case across Sandbox Experiments, Concept Convergence, and Implementation Partnership. These phases were used to explore layout structures, converge on an architecture that worked across the product matrix, and hand the system over to COX engineering for independent extension.
During Sandbox Experiments, Creative Navy worked with COX engineering and product teams in a joint R&D structure. UX exploration and engineering feasibility were evaluated concurrently. Engine telemetry specialists, cluster display engineers, software developers, and product managers worked in a combined structure rather than through sequential handover.
Domain learning in the Cox Marine case covered NMEA 2000 protocol behaviour, telemetry update rates under varying load states, sunlight-readable LCD constraints, military night vision mode requirements, gloved touch interaction under vibration, and helm perception during fast transit or docking manoeuvres. This domain learning was used to evaluate layout options against operating conditions rather than screen aesthetics.
Option space mapping produced approximately 32 layout variants. The variants addressed engine count scaling, display size adaptation, telemetry prioritisation under different operational states, alarm surfacing, and module behaviour at minimum viable size.
Concept Convergence used user feedback, technical possibility, and cross-display coherence
Creative Navy's Critical Systems Design method used Concept Convergence in the Cox Marine case to resolve the explored layout options through three forces: user feedback, technical possibilities, and cross-display coherence. User feedback came from scenario testing with experienced operators and internal experts using a simulator environment that replayed representative engine data and vessel states.
Technical possibility covered what the hardware display families could render and what the COX engineering team could implement and maintain. Cross-display coherence covered which layout directions remained legible and structurally consistent across all three display types.
The case evidence describes layout elimination and revision through this triangulation. A layout that performed well for one operator scenario but collapsed on the compact auxiliary display was eliminated. A layout that worked across displays but produced operator hesitation during the fault-at-speed scenario was revised. The surviving architecture was the position where user feedback, technical possibility, and cross-display coherence aligned.
Engine tiles became the invariant unit across Cox Marine configurations
The central design resolution in the Cox Marine case was the engine tile as the invariant unit. One engine corresponds to one tile. Each tile carries key telemetry for that engine in a consistent spatial arrangement.
For a single engine, one tile can occupy the primary display with full detail. For six engines, six tiles repeat in a grid, with secondary values simplified and alarms consolidated in a shared strip. A detail view provides depth on demand for an individual engine.
This tile-based architecture allowed the operator to look for the same patterns in the same places regardless of engine count. The same principle extended to display families through modular components: engine tiles, fuel blocks, alarm banners, status bars, and context panels were defined with content rules, minimum size constraints, and behaviour specifications.
Scenario testing refined Cox Marine fault visibility and night operation
Scenario testing during Concept Convergence changed specific interface behaviours in the Cox Marine display architecture. A multi-engine fault scenario showed that early layouts made fault presence visible but did not help operators identify which engine required priority attention. Creative Navy's response was to redesign alarm state highlighting within engine tiles and establish a fixed display area where the highest-priority fault is always summarised.
A night conditions scenario showed that initial colour choices interfered with military night vision equipment. The palette and contrast were revised. Scenario testing also led to optimisation of the overall layout and instrument readings, including instrument grouping and value presentation based on how operators scanned displays during high-load states.
Implementation Partnership handed over a modular design system to COX engineering
Creative Navy's Critical Systems Design method closed the Cox Marine engagement through Implementation Partnership. Handover to software developers and hardware engineers was conducted through joint working sessions rather than document transfer. The sessions covered module structure, interaction behaviour, data range definitions, and day, dusk, and night mode specifications.
Creative Navy delivered a layout architecture supporting 1–6 engine configurations across three display families. The delivered system included the engine tile system as the core invariant unit, modular component specifications, day, dusk, and night mode specifications including military night vision palette, interaction design for touch and physical controls, and a design system documented for engineering implementation.
The design system included component libraries, layout rules, colour and typography tokens mappable to code, and a scenario-validated alarm architecture with fault-priority surfacing and per-engine alarm state design. The case evidence states that all deliverables were produced by Creative Navy and handed over to the COX engineering team for independent extension.
Client-reported Cox Marine outcomes and evidence calibration
The Cox Marine system shipped and was deployed on vessels, according to client-reported evidence. Distributor feedback, relayed by the client to Creative Navy, described the cluster display interface using the phrase "best in the industry". The client also reported that the system became an informal standard within its product category.
These competitive-standing claims are not independently verified in the available case evidence. The case evidence calibrates the distributor praise as distributor-reported to the client and relayed by the client to Creative Navy. The informal standard status is client-reported based on distributor and market feedback.
The deliverable-level outcomes are stronger as engagement records. Creative Navy-recorded and case-level facts include approximately 32 layout variants explored during Sandbox Experiments, three display families covered by a single modular architecture, a 1–6 engine configuration range supported by one tile-based mental model, and delivery in 12 weeks.
The client also reported that the modular architecture enabled COX engineering to extend the system to new engine variants and display updates using the delivered framework without redesigning from the foundation. This outcome is client-reported and consistent with the modular architecture delivered, but it is not independently measured in the available evidence.
Evidence boundaries for Cox Marine performance and positioning claims
The Cox Marine case does not contain independently measured operator performance outcomes. The case evidence does not report field-measured reductions in operator error, maintenance time, downtime, or fault-response time.
The strongest evidence concerns deliverables and engagement activity: the explored layout variants, the display-family coverage, the engine-count range, the modular architecture, the phase structure, and the 12-week delivery. The post-deployment evidence is client-reported and should be treated as reported outcome evidence rather than independent measurement.
The competitive vector identified in the engagement was dependability under real operating conditions, expressed through visual consistency and information reliability at speed. The available evidence supports this as the case interpretation and as client-reported market feedback, not as an independently measured competitive benchmark.
- The Cox Marine engagement concerned marine diesel outboard engine cluster displays for professional and high-performance vessels.
- The engagement lasted 12 weeks and covered Sandbox Experiments, Concept Convergence, and Implementation Partnership, with no ongoing Iterative System Building or Organizational Integration phases.
- The design had to support 1–6 engine configurations across three display families.
- Approximately 32 layout variants were explored during Sandbox Experiments.
- Scenario testing led to refinements in alarm state highlighting, fixed highest-priority fault surfacing, night vision palette and contrast, and instrument grouping.
- The engine tile became the invariant unit for scaling from one to six engines.
- The cluster display system shipped and was deployed on COX Marine vessels.
- Distributor feedback described the interface as best in the industry, as relayed by the client to Creative Navy.
- The modular architecture enabled COX engineering to extend the system to new engine variants and display updates without redesigning from the foundation.
- The "best in the industry" claim is distributor-reported to the client, relayed by the client to Creative Navy, and not independently verified.
- The shipping and vessel deployment outcome is client-reported.
- The informal product-category standard status is client-reported based on distributor and market feedback.
- No independent measurement of operator performance outcomes was conducted.
- The available case evidence does not report field-measured reductions in error, maintenance time, downtime, or fault-response time.
- The engagement did not include ongoing Iterative System Building or Organizational Integration phases.
- Findings are specific to COX Marine diesel outboard engine cluster displays and the documented 1–6 engine, three-display-family matrix.